fossapup64: Pupsave on different drive won't boot?

[PuppyFromLosAndes]

Hello!

I would like to use a pupsave separate from the flash drive in which Puppy Linux was installed.

I have fossapup64 copied into an Easy2Boot drive. I was allowed on shutdown/reboot to choose what drive would the pupsave go to, so I told it to make a folder pupsave on a four hundred ninety something megabyte SD Card that I had at hand. However, by booting it again, it seems that Puppy Linux completely skips loading the pupsave.

I don't know how to directly tell it to take the pupsave into account at boot. Please help.

[esos]

You need boot parameter "psave="

[gychang]

Hello!

I would like to use a pupsave separate from the flash drive in which Puppy Linux was installed.

I have fossapup64 copied into an Easy2Boot drive. I was allowed on shutdown/reboot to choose what drive would the pupsave go to, so I told it to make a folder pupsave on a four hundred ninety something megabyte SD Card that I had at hand. However, by booting it again, it seems that Puppy Linux completely skips loading the pupsave.

I don't know how to directly tell it to take the pupsave into account at boot. Please help.

important to place a save folder in a fast drive (??sd card) and my save folder for FP64 is over 3G!

[PuppyFromLosAndes]

You need boot parameter "psave="

I tried doing psave=/dev/sda1, then psave=/dev/sda1/fossapup64save, then psave=hd0. None seem to work?

(i'm typing "sda" because my laptop doesn't have any HDD attached, so it detects the SD card slot as the first disk available)

[Clarity]

...
I would like to use a pupsave separate from the flash drive in which Puppy Linux was installed.
...

Hello @PuppyFromLosAndes. Thhis is a very good practice.

I have been doing this for a decade and its NOT just for FossaPUPs.

FossaPUP, although it still works and is a VERY good PUP distro, it has been superceded with various updates, such as F96CE PUP distro and Fossa upgraded and replaced with modern BookwormPUP which many forum members contribute to, currently.

To answer your question, for BOTH your current distro and future use, I offer this proven simple approach used. This info I offer is NOT new. It has been posted and discussed many time on the forum as follows:

1. Carve out a partition of your system drive where ALL of your forum's saves will be contained. I advise you name that partition "Persistence" because not only will this be used for PUPs without changing the Boot Menu, but will be used OOTB should you want to play around with KL distros from the forum.

2. On this partition, create a folder named "Sessions". Your PUP versions (and KLs too) will place and find your sessions without issue or need to touch the Boot Menu.

3. The MOST important part of this is the following: A SAVESPEC file that is a feature of ALL modern PUPs. It should have been created depending how you created your USB. With this file's presence. a booting PUP looks for this file to tell it where to find or create a save for the booting PUP...no matter if its a reboot or a new boot of any new modern PUP. For reference here is an example I have on my boot drive:

   Code: Select all

   # This file, if present, will be used by WoofCE PUPs at boot time.
   # The file sets the SESSIONs directional for the booting distro.
   
   # Indicate the label or UUID containing Sessions
   SS_ID='Persistence'
   # Indicate the folder containing Sessions
   SS_DIR='/Sessions'
   # Indicate the media type device containing Sessions
   SS_MEDIA='atahd'

   .
   The PUP developer who authored this PUP feature, SAVESPEC facility, offers a utility to create it IFF you want to create it correctly automatically, here

.Summary
1-2-3...1. create a partition 2. add Session folder 3. update the SAVESPEC file
Done! Its Simple.
.
Post back here if you need help.

[d-pupp]

I tried doing psave=/dev/sda1, then psave=/dev/sda1/fossapup64save, then psave=hd0. None seem to work?

psave is looking for a UUID of the drive
To get the UUID open a terminal window and type

Code: Select all

lsblk -f /dev/sda1

or

Code: Select all

blkid

I like lsblk better. It has a cleaner output.