StackExtra v23 and SfsExtra v23
Posted: Tue 26 May 2020, 23:38
What is it?
StackExtra is a kind of replacement for 'SFS-Load on-the-fly'.
It can add and delete sfs files, and directories, from a Puppy frugal install.
They can be added above or below the Puppy system sfs files, with an ABOVE list and a BELOW list.
They can reside anywhere on the machine, even on a different partition.
Sfs files in the ABOVE list are copied to RAM, if possible. Directories, and entries in the BELOW list are used in-situ.
The order of each list can be easily modified with an "Up" button.
It stores a "last modified" date/time stamp for each entry, if a file is replaced by one with the same name it will most likely have a different date/time stamp, so it will be checked for any update processing requirement.
Try it?
latest version 23 at http://www.murga-linux.com/puppy/viewto ... 50#1060350.
I have attached 'stackextra_22.sfs':
This sfs is meant to be added as an Extra sfs using 'SFS-Load on-the-fly'.
This should add 'StackExtra SFS/Directory loader' to the 'Setup' menu, beside 'SFS-Load on-the-fly'. It may become confusing, having 2 usilities for managing Extra sfs files.
Another limitation with using this install file, is that if you click on an sfs file, this will still be handled by 'SFS-Load on-the-fly'.
Using this install file is not recommended for continual use.
I have attached 'stackextra_adrv_22.sfs':
This sfs is meant to replace the adrv...sfs.
This replaces 'SFS-Load on-the-fly' with 'StackExtra SFS/Directory loader'.
Now, if you click on an sfs file, it is handled by 'StackExtra SFS/Directory loader'.
The loading of Extra sfs files during boot is also more efficient.
Using this install file is the recommended way of using 'StackExtra'.
If you want to keep your current adrv...sfs, then rename it before installing 'StackExtra', and then add it to the bottom of the 'StackExtra' ABOVE list.
Why?
This is partly in response to messages on the forum about adding bdrv, cdrv etc, these suggest that having only the adrv and the ydrv as sfs's loaded above the puppy...sfs, is too restrictive.
StackExtra supports the definition of many sfs files in it's ABOVE list, all of which get loaded above the puppy...sfs.
It is also a kind of "porting" of 'MI Extra SFS List manager' to the aufs environment of "normal" Puppy.
StackExtra also extends the current boundries of Puppy stack support by including the ability to use a directory instead of an sfs file.
After all, aufs (or overlayfs) stacks are stacks of directories, not sfs files. It's just that in Puppy, we normally use the mount-points of sfs files as those directories.
This theoretically opens the possibility of being able to specify archive files as "read-only" layers in the stack, they would be extracted into "/tmp/some-dir" and this directory added to the stack.
(I have no idea if this would be useful.)
The BELOW list is simply there to provide the Extra SFS facilities we are used to.
Note on version number:
As with all utilities that emerge from my "mio" project, the version number has no particular meaning, it is just an integer that gets bigger, and it is shared by all.
22 is simply the current "mio" version.
gyro
StackExtra is a kind of replacement for 'SFS-Load on-the-fly'.
It can add and delete sfs files, and directories, from a Puppy frugal install.
They can be added above or below the Puppy system sfs files, with an ABOVE list and a BELOW list.
They can reside anywhere on the machine, even on a different partition.
Sfs files in the ABOVE list are copied to RAM, if possible. Directories, and entries in the BELOW list are used in-situ.
The order of each list can be easily modified with an "Up" button.
It stores a "last modified" date/time stamp for each entry, if a file is replaced by one with the same name it will most likely have a different date/time stamp, so it will be checked for any update processing requirement.
Try it?
latest version 23 at http://www.murga-linux.com/puppy/viewto ... 50#1060350.
I have attached 'stackextra_22.sfs':
This sfs is meant to be added as an Extra sfs using 'SFS-Load on-the-fly'.
This should add 'StackExtra SFS/Directory loader' to the 'Setup' menu, beside 'SFS-Load on-the-fly'. It may become confusing, having 2 usilities for managing Extra sfs files.
Another limitation with using this install file, is that if you click on an sfs file, this will still be handled by 'SFS-Load on-the-fly'.
Using this install file is not recommended for continual use.
I have attached 'stackextra_adrv_22.sfs':
This sfs is meant to replace the adrv...sfs.
This replaces 'SFS-Load on-the-fly' with 'StackExtra SFS/Directory loader'.
Now, if you click on an sfs file, it is handled by 'StackExtra SFS/Directory loader'.
The loading of Extra sfs files during boot is also more efficient.
Using this install file is the recommended way of using 'StackExtra'.
If you want to keep your current adrv...sfs, then rename it before installing 'StackExtra', and then add it to the bottom of the 'StackExtra' ABOVE list.
Why?
This is partly in response to messages on the forum about adding bdrv, cdrv etc, these suggest that having only the adrv and the ydrv as sfs's loaded above the puppy...sfs, is too restrictive.
StackExtra supports the definition of many sfs files in it's ABOVE list, all of which get loaded above the puppy...sfs.
It is also a kind of "porting" of 'MI Extra SFS List manager' to the aufs environment of "normal" Puppy.
StackExtra also extends the current boundries of Puppy stack support by including the ability to use a directory instead of an sfs file.
After all, aufs (or overlayfs) stacks are stacks of directories, not sfs files. It's just that in Puppy, we normally use the mount-points of sfs files as those directories.
This theoretically opens the possibility of being able to specify archive files as "read-only" layers in the stack, they would be extracted into "/tmp/some-dir" and this directory added to the stack.
(I have no idea if this would be useful.)
The BELOW list is simply there to provide the Extra SFS facilities we are used to.
Note on version number:
As with all utilities that emerge from my "mio" project, the version number has no particular meaning, it is just an integer that gets bigger, and it is shared by all.
22 is simply the current "mio" version.
gyro