Sylvander wrote:
3. Something that gives me cause for concern:
a. I always thought it good that when booting Puppy from an optical disk...
It could be finalized so it couldn't be written to, hence practically incorruptible.
And a pupsave file, if infected/corrupted...
A 2nd Puppy could be used to delete the pupsave and replace it with a good backup copy.
Hence a "live" install was pretty safe.
b. With the new arrangement used in Quirky Unicorn, a snapshot would be saved within the Puppy filesystem.
Hence Quirky would need to be functional to be able to restore a snapshot.
Yet it's not guaranteed incorruptible.
I saw BK say somewhere that he intends to do something about this.
I wonder what?
4. I normally set up my Puppies so I have the choice "to save or not to save" session changes.
Both during the session, and at shutdown/reboot.
Is there a way to do this in Quirky Unicorn?
3.
A snapshot can be restored at bootup. Quirky creates a ramdisk, with a small Linux environment, and runs from there. As long as Quirky can get the files needed to create the ramdisk, even a broken system can be rolled back.
The files needed to create the ramdisk are mostly static, that I created especially for the purpose, though in theory if any of those have been damaged or deleted then the ramdisk won't work.
Yes, the extra step that I was considering, to ensure rollback of a totally messed up installation, is to have a ramdisk image file. As long as that file still exists, the ramdisk can be created.
Oh yes, busybox will have to still be there, and working, but it is also a static executable.
4.
You are thinking in Puppy terms, but as for number 3 above, you have to know that Quirky is a conventional full installation of Linux.
There is no "pupsave" file. You are running a full install of Linux, so no option to shutdown without saving session.