Page 2 of 2
Posted: Sun 15 Apr 2007, 22:17
by sunburnt
Thanks Mark, I seem to recall some of this from when I looked at Puppy-2's boot code.
I'll keep this in mind as I work on a "Unleashed to SFS" builder GUI.
I have "mksfs" that seems to work well building SFS files by merging or joining
image files, directories, & SFS files into new SFS files.
Posted: Fri 20 Feb 2009, 19:04
by vtpup
Post deleted,
wrong thread, sorry.
Posted: Fri 20 Feb 2009, 23:08
by MU
Posted: Sat 21 Feb 2009, 02:02
by vtpup
Sorry Mark my post above is attached to the wrong thread! Transferring now to the one you quote here. That;ts where I have a problem.
Posted: Sat 19 Sep 2009, 20:08
by ecomoney
If you want your sfs to automagically create an icon on the desktop (which is something many new linux users need until they get to know under the hood),
here is a tip to do it.
Posted: Thu 24 Sep 2009, 13:14
by mary john
Hey all,
There are more than one way to create .sfs file, but i follow a single path like here,this is eaisy and quit way to create a .sfs file. If u want to go with my path then u must follow this
The sfs files will mount on "/",
Also, the file naming format for puppy2 is as follows:
*_200.sfs
where the "*" means any text string, the "200" is the 3 digit puppy version number. So when Puppy version 2.0.0 is released, it is compressed as 200.
Having versioning in all the .sfs files is probably a good thing.
ou can have up to 4 of them, and they will load in alphabetical order, for example:
devx_200.sfs
kde_200.sfs
Order is important, as a file named myfile.txt in devx_200.sfs will hide myfile.txt in kde_200.sfs.
So, in a running puppy2:
tmpfs (ramdisk)
persistent storage (hd, flash, dvd)
pup_200.sfs (puppy himself)
devx_200.sfs
kde_200.sfs