Boot dir of Save File

[Jake]

Xenial, & now Bionic, Pup has changed where they will ID Save Files. They must be C:\. Previously I always made a dir for each Puppy -- C:\Macpup, C:\Slacko57, C;\Tahr64, & so on to keep things neat. Some Puppies, I'm remembering Lucid, would just drill down until it found a save file. Slacko & Tahr will still do C:\dir but not further if I remember. This inabilty to find Save Files below C:\ matters not if Puppies X & B are booted from a multi boot usb, single boot usb [designated usb or cd], or from a cd. More, X & B always copy sfs files from the boot-source & do not use the sfs in the Save File Dir.

Explanation: multi boot sticks are made with most distros created as an Unlisted distro. This makes a boot function that places the ISOs in an ISO dir on the stick. For instance, this boot stick has Bionic, Slacko64-6.3, Tahr64, & Xenial64-7.5 with all the ISOs sbd1/multiboot/ISOS/listed Puppies. Slacko & Tahr boot, find the C:\Slacko\Tahr dirs load the sfs files from the dir and start the Save File[s]. Bionic & Xenial boot, load the sfs files from the sbd1/multiboot/ISOS/listed Puppies ISO, find the C:\Save File & start it. Of course with USB3 time to complete boot is short. If the computer has a WinOS, I like to place Save Files in the partitions hidden from the Win file manger, System or Recovery, & that cannot now be done.

A Puppy, or any Linux distro --Manjaro/4MLinux/AV Linux, on this stick-- created as a Linux distro, runs from the stick. The questions: why does Xenial & Bionic behave so, and how/can that be fixed[?]? C:\ is getting a little messy with Save Files & various sfs files.

[s243a]

There might be a boot parmater that says how deep that puppy will search for a save file but if you want the search to start at a given directory you can use the "psubdir" paramater. Here is an example:

Code: Select all

title dpupStrech (sdb1)
  uuid 6b364213-21c1-4c84-b2e9-75697db956e2
  kernel /dpupStrech/vmlinuz  pmedia=usbflash psubdir=/dpupStrech
  initrd /dpupStrech/initrd.gz

You can also specify the exact location of a save file. Example:

Code: Select all

psave=f27da80d-445e-47dc-b043-9199bfe4891e:/TazPup/64/a1-j/tazpupsave/

**Note that I'm using a save folder here but you can change this to a save file by specifying the path to the savefile.

to get the uuid you can use the blkid comand but you should already have this info in your menu.list file.

In my save folder example here is my complete entry in my menu.list flie:

Code: Select all

title Start tazpup64 b23 - sdb1 -- a1-j
  uuid f27da80d-445e-47dc-b043-9199bfe4891e
  kernel /TazPup/64/a1-j/vmlinuz pmedia=atahd pfix=fsck pdrv=f27da80d-445e-47dc-b043-9199bfe4891e psubdir=/TazPup/64/a1-j/ psave=f27da80d-445e-47dc-b043-9199bfe4891e:/TazPup/64/a1-j/tazpupsave/ 
  initrd /TazPup/64/a1-j/initrd.xz  

For more info see:
http://wikka.puppylinux.com/BootParametersPuppy
http://wikka.puppylinux.com/BootParameters
http://wikka.puppylinux.com/BootParametersGeneral
http://wikka.puppylinux.com/BootIndex
http://distro.ibiblio.org/fatdog/web/fa ... tions.html
House Training: puppy boot options.
http://wikka.puppylinux.com/BootLoaders

p.s. the name of the boot paramter (e.g. psubdir) must be either entirely in uppercase or entirely in lowercase.

[bigpup]

The boot options for Fatdog only work in Fatdog or something based on Fatdog.