How to indicate to Puppy where you want your savefolder to be located.

[Clarity]

Since only using psave=, I have NOT tried to do a pristine boot without it, save a session, and then review if the SAVESPEC is placed such that it is found on subsequent boot. I will try the current 'ScPup64-21.04+2-T.iso' and report back here.

Edit: This report verifies your indicators.

The following shows a simple occurance: I merely downloaded and booted the ISO in a single step, broken down as follows (in case someone wants to make a video for PUP/DOG booting):

1. Downloaded 'ScPup64-21.04+2-T.iso' to /BOOTISOS on SG2D USB stick

2. Booted USB

3. Selected "ScPup64-21.04+2-T"

4. Pristine boot (Enter key only at ScPUP's Menu)

5. Filled-in FirstRUN with locale changes

6. Updated Package manager

7. Setup SAMBA

8. Tested SAMBA

9. Minor desktop changes

10. Shutdown processing

    1. chose EXT4 for folder session save (this is NOT on boot USB)

    2. change the pre-selected folder name to /Sessions folder

       

       ScPup64-1st_shutdown3.gif (137 KiB) Viewed 756 times

    3. Shutdown

11. Rebooted USB and selected same ISO

12. At ScPup64 Menu screen, merely hit the Enter screen (same as before)

13. ScPup64 booted, found its save-session showing [SAVESPEC]

14. Everything, as before my prior shutdown, is present...ready to go!

Thanks @gyrog for this eye-opener. This is an even better game changer for PUP/DOG use!!!

I, now, no longer need to ever use "psave=" with this built-in ability. Puppy Linux booting has just gotten so much easier to boot and manage. This replaces all need for use of Frugal with this knowledge.

GREAT feature thanks to you and the PUP+DOG developers who made these changes for our benefit.

[Clarity]

This really means that any PUP/DOG distro builder has an additional option available in releasing their ISO...namely it 'could' be embedded in an SG2D IMG file.

This then allows any user to have all that needed to make the bootable USB with the PUP enclosed to run on any PC; namely BIOS/UEFI with NO PREPARATION. And if the user so chooses, they could merely add PUP/DOG ISOs to the USB's /BOOTISOS folder as the need arises.

Just an implementation idea OR one for an application...not a request.

[gyrog]

@Clarity,
thanks for testing.

[gyrog]

Yes, they apply to all woof-ce Puppy Linux installs that use the normal 'init' script in 'initrd.gz'.

The code in 'init' for handling these facilities does not discriminate between the various boot possibilities,
but somtimes it is quite difficult to make use of a particular facility.

If we take SAVESPEC as an example:

The standard code always processes a file called SAVESPEC in the install directory, i.e. the directory that contains the puppy...sfs, if it finds one there.
For frugal installs that's easy to setup.

But for booting from a CD/DVD, it still works, the difficulty is getting it there, i.e. as a SAVESPEC file on the CD/DVD.
Of course you can get it there by "editing" the .iso, with "ISOMaster",
or if you are using an "open" DVD (suitable for multisession, pupmode=77), it can be written directly to the device by 'mk-savespec'
viewtopic.php?p=20976#p20976, once.

Similarly for an isoboot, the standard location for the SAVESPEC file is inside the .iso file, beside the puppy...sfs file,
it will work if you get it there, but the effort in getting it there kind of defeats the whole point of diretly booting the .iso file.
That's why the extra code added to support 'isoboot', will use a SAVESPEC file found in the directory containing the .iso files.

[Clarity]

Although not requested, this is what it looks like for the SG2D USB boot on my PC

ScPup64-1st_shutdown4.gif (54.7 KiB) Viewed 736 times

All occurs automatically ... NO USER INTERVENTION on either boot or reboots! This has made ISO booting all too simple for both new and OLD (like me) users of modern PUPs & DOGs.