SfsBuild v22 - sfs file builder

Under development: PCMCIA, wireless, etc.
Post Reply
Message
Author
gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

SfsBuild v22 - sfs file builder

#1 Post by gyro »

What is it?

SfsBuild uses a list of sfs files and/or directories, and merges these to build a new sfs file.
It provides a facility to define an ordered list of the elements that become part of the sfs file.
Each element in the list can be an sfs file or a directory.
And, of course, a facility to generate an sfs file from the list.

The default output filename is <sfs definition>.sfs in the current working directory,
but if it is recognised as a system sfs, e.g. 'adrv', 'ydrv', then the output filename will be the standard system sfs filename, in the Puppy install directory.
These defaults can be overidden by the 'Filename' facility, which allows the specifiation of the 'Filename' and the 'Folder'.
The specified filename can include "%D" which will be replaced by a date string when writing the output file;
if the filename includes "%T", it will be replaced by a time string when writing the output file.

So it could be used to maintain an "adrv...sfs", combining many sfs files.
Or it could be used to maintain the sfs file for a project that consists of many elements, each in their own directory.

It is an example of how to use a stack to merge multiple directories, (both aufs and overlayfs).


Try it?

I have attached 'sfsbuild_22.sfs':
This sfs is meant to be added as an Extra sfs.
If you are using "mio" or "StackExtra", it can be added to either the 'BELOW' list or the 'ABOVE' list.
This should add 'SfsBuild - sfs file builder' to the 'Setup' menu.


Why?

Like "StackExtra", this is partly in response to messages on the forum about adding bdrv, cdrv etc, that suggest that having only the adrv and the ydrv as sfs's loaded above the puppy...sfs, is too restrictive.
But, instead of providing for more sfs's above 'puppy...sfs', it can merge all the sfs's that might be wanted above 'puppy...sfs', into a single sfs, e.g. as 'adrv...sfs'.
Simply create an sfs definition called 'adrv', add your sfs files to this definition, and produce the output 'adrv...sfs'.
If the 'adrv...sfs' file on disk is busy, i.e. you are running with 'pfix=nocopy', the output file will be 'adrv...-NEW.sfs'.

gyro
Attachments
sfsbuild_22.sfs.gz
gunzip to produce sfs file
(11.88 KiB) Downloaded 103 times

Post Reply