rufwoof wrote:In multi-session save mode, you set Fatdog to load all of the prior saves automatically at next reboot, there's no need to manually set/load them by-hand, you just add the appropriate 'savefile' kernel boot parameter.
You can't be selective, as they're sequential save sfs's, so missing one out in the middle would mess things up. You can however opt to not load the last N saves. For readability I've shortened down my actual uuid in the following, but that's the kernel boot paramater I use for multi-session. The last two ":" don't have to be included, but I leave them as that way its a reminder of where the 'skip' N saves value is
savefile=direct:multi:uuid:5d::
i.e. if I change that to
savefile=direct:multi:uuid:5d::2
then it wont load the last two saves.
Or you could just manually delete the last (most recent) save sfs
When you have say 10+ saves and want to consolidate them, I boot (so all the saves are loaded into ram), manually delete all of the multisession save files (sfs's) - backing them up first just in case, and then click the desktop 'save' icon ... and its back down to just two save sfs's.
My full menu.lst entry looks like
title FatDog
root (hd0,0)
kernel /fatdog-vmlinuz pkeys=uk waitdev=5 basesfs=ram:uuid:5df8f89e-33d5-4720-b3f2-9c9030a718bd:/fd64.sfs savefile=direct:multi:uuid:5df8f89e-33d5-4720-b3f2-9c9030a718bd::
initrd /fatdog-initrd.xz
Note that in my case I originally clicked on the initrd to open it, dragged out the fd64.sfs from that, and then closed the initrd again (by clicking the repack-initrd file) so as to have the main sfs (fd64.sfs) outside of initrd. Note also that I've renamed the vmlinuz and initrd (and I've also opted to xz compress the initrd) ... i.e. not they're not the default/standard names
The appeal of multisession for me is that I install it all to and boot/run from usb stick (bootloader etc.), and all saves are written back to that usb. But where I have Event Manager's Save Session Interval set to zero so it only ever saves on demand, and the usb can be removed between times (i.e. is physically isolated after having booted up the system). Mostly I'm very frugal with savesi.e. tend to just boot, use, shutdown without saving, and I'm careful as to what saves are added (boot clean, make changes, save ... without doing anything else so that the system remains 'clean'). I keep my bookmarks in a text file, and have tilda drop down terminal installed, where one of its tabs has that bookmarks text file open (and where hovering-over and clicking a link opens up that url in chrome). Chrome is about the only reason I run 'save' i.e. boot, use the control panel to update to the latest version of chrome, save.
Another appeal is that Fatdog only improves with age, each later release builds upon the last release. With Puppy it often seemed one step forward two steps back i.e. some past improvements were suddenly lost.
Yet another appeal of Fatdog for me is that its alsa equaliser works. i.e. running alsamixer presents the usual alsa mixer, but running alsamixer -D equal ... presents a working equaliser. And, at least for me, its alsa supports multiple sound sources being played simultaneously.
Thanks, Rufwoof, that clears it up for me. Had totally forgot about I needed to make menu.lst changes if I want Fatdog to look for something I created on a previous pristine boot and I had not created a 'savefile' at the end of that pristine boot (so Fatdog could remember things for next next boot).
Soon as I saw your menu.lst example, I had to shake my head at myself
Thanks again.
1234:wlan0:dhcp pkeys=uk lateshell basesfs=ram:uuid:4d054dbd-ff:/FATDOG-TIP/fd64.sfs savefile=direct:multi:uuid:4d054dbd-ff:/FATDOG-TIP/:
