perhaps my wording was not clear enough..'and have a not save option' might be more clear.Multisession [Multi-session live-CD/DVD] can save to dated save folders. That's why it's called "multisession".
In other words it truly loads all to ram including saves (sfs part only if enough ram) ..... and there is no persistent save file on a hard drive/usb. It inherently, and as part of the system has a no save option. My point was usb DOES have a save file which is mounted in use...just has the extra tmpfs for session changes which then gets merged. Hence the inability to remove the usb flash stick. The impression was given that puppy loads to ram saves and all regardless of mode...which is not the case EXCEPT for multisession. PUPMODE=13 was designed reduce save file writes rather than be independent of one.
Another thing mentioned was decompressing of sfs.... not so...only the required data read is decompressed on the fly when needed but the sfs remains the same size sat in another tmpfs.
Thing is if talking about the system and optimising then it needs to be clear what the system is including my wording of it
Its important to know what goes where....
There is a nice set of diagrams of the various modes somewhere.... a picture definitely paints a thousand words.
As an aside the sfs save method I made is based on multisession's total ram approach but usable on flash and hard drives. In other words achieve what all these hacks with PUPMODE=13 are trying to do...ie be free of ANY drives once booted and discard all at the end if desired.
mike