I dont know what significant time would have been required to use a basic puppy function. This is not a slight against TazOC at all. So please no one take it as that. But the functionality of a save file sitting in top of everything is is a needed function for a frugal system with persistance to even work. So it doesn't take special skill to manage that. He has hacked the initrd script quite a bit to enable the addons that we see in LHP, but thats all lower work dealing mostly with SFS package management. (its been a while since I ripped the inird apart and looked at it, so I may be operating on older information)gcmartin wrote:Question
In LH64, isn't the save-session files (I run live media) loaded before the SFSs. Thus this puts it highest in the order and SFS loading would not compromise save session stuff.
I ask, because I seem to remember TaZoC doing a significant amount of structuring to arrive at the boot-time management that we see.
This is, I believe, how it works in, say, Mariner.
Is that a correct view?
TazOC can correct me If I'm wrong, (and I hope he does if I am wrong) but the only thing I remember that needed special attention was the order the SFS layers loaded into memory. Thats why the zWine layer loads first, and if you run KDE or other SFS like that they have a number appended to the beginning so they are loaded before others. He worked through that in LHP v4 series I think. That did require trial and error on his part to work out the proper order for certain SFS packages. Is that what you are refering to?
The Save session sits on the top level of layered file system. This is the same as every other puppy that Im aware of. Thats how the user save file can overwrite any changes in the Base SFS thats on the ISO or any add-on SFS packages the user installs.
In my previous post I said "save file sits on top of SFS files". In the layered file system the layers on top have priority over the layers below... so what I said means the same thing as what you said... this puts it highest in the order and SFS loading would not compromise save session stuff.
Hence the conversation Meeki and myself had.
EDIT:meeki wrote:Agree.... this is why I am switching all my Drivers to SFS for now on. Even if i uninstall my old 304 nvida pet and install my new 310 SFS it fails.SFS release is a problem for video drivers. Due to the layering of the system when it boots... save file sits on top of SFS files... so if they have an older driver in their save file... the newer one in the SFS wont be used.
Ive now installed and uninstalled the nvida SFS and it stays happy.
Found it: