How to make .sfs file (compress programs and settings)
Hi,
i am having hard time with squash files. I hope someone of you will help, here is where i am: i have created a SFS file and i would like it to be mounted at boot time by the CD.
1. i have put an application into /usr/local/SFS_FILENAME
2. i have make the SFS with the command
mksquashfs /usrlocal/SFS_FILENAME myaddon_214.sfs
3. i have deleted /usr/local/SFS_FILENAME
4. i have remastered the cd with Dougals tool
5. i have a brand new CD with all the file AND myaddon_214.sfs
ok, it boots fine, but the squash file is not mounted and the softwares in myaddon_214.sfs are not found in /usr/local
I cannont figure what i did wrong nor i don't know how to mount it by hand so to test may squash file. I read on another thread MU created a squash extension manager but it is not for v2.14 (or am i wrong ?) here is the thread
http://www.murga-linux.com/puppy/viewtopic.php?t=7457
Is there something special to specify somewhere to have a squash file mounted at boot
time ? i thought it was automagic...
Also, is there a size limit at a squash file ? mine is around 100Mo ; how much Mo can i add for a computer with 512 Mo ?
best regards,
Laurent.
i am having hard time with squash files. I hope someone of you will help, here is where i am: i have created a SFS file and i would like it to be mounted at boot time by the CD.
1. i have put an application into /usr/local/SFS_FILENAME
2. i have make the SFS with the command
mksquashfs /usrlocal/SFS_FILENAME myaddon_214.sfs
3. i have deleted /usr/local/SFS_FILENAME
4. i have remastered the cd with Dougals tool
5. i have a brand new CD with all the file AND myaddon_214.sfs
ok, it boots fine, but the squash file is not mounted and the softwares in myaddon_214.sfs are not found in /usr/local
I cannont figure what i did wrong nor i don't know how to mount it by hand so to test may squash file. I read on another thread MU created a squash extension manager but it is not for v2.14 (or am i wrong ?) here is the thread
http://www.murga-linux.com/puppy/viewtopic.php?t=7457
Is there something special to specify somewhere to have a squash file mounted at boot
time ? i thought it was automagic...
Also, is there a size limit at a squash file ? mine is around 100Mo ; how much Mo can i add for a computer with 512 Mo ?
best regards,
Laurent.
Create a folder (it also could be somewhere else):
/root/sfs/
Copy there your files.
In this example, I use some example files EXAMPLE to make it clearer.
You need such a folderstructure:
/root/sfs/usr/local/bin/EXAMPLE.sh
/root/sfs/usr/lib/EXAMPLE.so
/root/sfs/usr/share/applications/EXAMPLE.desktop
/root/sfs/usr/share/icons/EXAMPLE.png
Now create the squashfs:
cd /mnt/home
mksquashfs /root/sfs EXAMPLE_215.sfs
That's all!
Now reboot, and you should have these files:
/usr/local/bin/EXAMPLE.sh
/usr/lib/EXAMPLE.so
/usr/share/applications/EXAMPLE.desktop
/usr/share/icons/EXAMPLE.png
Note that sfs are only mounted automatically, if you run Puppy from CD or a frugal installation. But not from a full harddisk installation.
/mnt/home is a symbolic link to the folder, where Puppy stores all settings in the file pup_save.2fs.
You don't need a manager to mount them, such managers are only made for extended possibilties.
The filesize is unlimited.
It is not loaded to Ram, but mounted like a CD or harddisk if it runs from a fast media like a harddisk.
Mark
/root/sfs/
Copy there your files.
In this example, I use some example files EXAMPLE to make it clearer.
You need such a folderstructure:
/root/sfs/usr/local/bin/EXAMPLE.sh
/root/sfs/usr/lib/EXAMPLE.so
/root/sfs/usr/share/applications/EXAMPLE.desktop
/root/sfs/usr/share/icons/EXAMPLE.png
Now create the squashfs:
cd /mnt/home
mksquashfs /root/sfs EXAMPLE_215.sfs
That's all!
Now reboot, and you should have these files:
/usr/local/bin/EXAMPLE.sh
/usr/lib/EXAMPLE.so
/usr/share/applications/EXAMPLE.desktop
/usr/share/icons/EXAMPLE.png
Note that sfs are only mounted automatically, if you run Puppy from CD or a frugal installation. But not from a full harddisk installation.
/mnt/home is a symbolic link to the folder, where Puppy stores all settings in the file pup_save.2fs.
You don't need a manager to mount them, such managers are only made for extended possibilties.
The filesize is unlimited.
It is not loaded to Ram, but mounted like a CD or harddisk if it runs from a fast media like a harddisk.
Mark
Thanks Mark, I run from a live CD v2.14 and my goal is to have an addon_214.sfs file mounted automatically at boot.
it does not work, i do not have a /mnt/home direcotry ; is it a special directory and is there a special command to create it ?
and when i reboot do i save or not ? usually i do not save. My goal is to remaster so my friend can have the same cd.
Best regards,
Laurent.
it does not work, i do not have a /mnt/home direcotry ; is it a special directory and is there a special command to create it ?
and when i reboot do i save or not ? usually i do not save. My goal is to remaster so my friend can have the same cd.
Best regards,
Laurent.
/mnt/home is created, when you save the first time.
So when pup_save.2fs is created.
So yes, you must save once to be able to use a sfs.
This will change in Puppy 2.16, which will allow to mount a sfs directly from CD.
The advantage of sfs is, that you can share it with users of different versions of Puppy.
But if you just want to give your friends a whole customized CD, you do not need sfs.
In this case you would install programs in the running system, and then create a new CD with such a remaster program like that from Dougal.
But I cannot help you with that, as I don't use it.
I rebuild Isos like Muppy with some console-commands from an external folder, where I copy everything I need.
This method is for advanced users only, usually such a remaster wizard is easier to use.
Mark
So when pup_save.2fs is created.
So yes, you must save once to be able to use a sfs.
This will change in Puppy 2.16, which will allow to mount a sfs directly from CD.
The advantage of sfs is, that you can share it with users of different versions of Puppy.
But if you just want to give your friends a whole customized CD, you do not need sfs.
In this case you would install programs in the running system, and then create a new CD with such a remaster program like that from Dougal.
But I cannot help you with that, as I don't use it.
I rebuild Isos like Muppy with some console-commands from an external folder, where I copy everything I need.
This method is for advanced users only, usually such a remaster wizard is easier to use.
Mark
216 which is in the experimental stage at the moment has a great feature for handling sfs files on load - I use sfs files a lot to hold my customizations and programs like wine which are tailored to my individual needs and I have found that the bootmanager included in 216exp2 is sinmple to use and appears very stable
It sounds like it will br ideal for what you are looking for
George
It sounds like it will br ideal for what you are looking for
George
george
Laurent; What MU says is the correct way to do it (of course).
What vern72023 said is correct also, Barry has rewritten my "post boot SFS GUI".
It'll allow setting up SFS files for booting, I haven't seen his handy work yet though.
Laurent... I think that the reason your SFS file doesn't load is Puppy ONLY loads
SFS files named pup_more.sfs or pup_devx.sfs, so rename your SFS to "pup_more.sfs".
You could rename it & try it just for the heck of it, but if it loads but doesn't
work you should probably do the SFS file again with MU's instructions.
...Terry
What vern72023 said is correct also, Barry has rewritten my "post boot SFS GUI".
It'll allow setting up SFS files for booting, I haven't seen his handy work yet though.
Laurent... I think that the reason your SFS file doesn't load is Puppy ONLY loads
SFS files named pup_more.sfs or pup_devx.sfs, so rename your SFS to "pup_more.sfs".
You could rename it & try it just for the heck of it, but if it loads but doesn't
work you should probably do the SFS file again with MU's instructions.
...Terry
There is ABSOLUTELY no doubt about it, i am the newbie, he is the guru ;sunburnt wrote:Laurent; What MU says is the correct way to do it (of course).
That's why i was asking for help and i am very gad Mark helped me because now...
IT WORKS ! ...it's incredible ! it is very powerful !! I can load thousands of megas and it does not weight, amazing, really.
...and i can now understand what Barry said at the beginning of the thread:
mine files have come right into / even if i managed to put them in /root/sfs/usr/local/EXAMPLE like Mark teached.For Puppy2, the sfs files will mount on "/"
but anyway, i will do it again until i can put them down into /usr/local
I think another error i made was i did not respect 8+3 filename naming convention for msdos files and perhaps my SFS was not seen...
well mine is named dofs_214.sfs and was loaded fine automagically at boot time, but ok i take notice of itsunburnt wrote:Laurent... I think that the reason your SFS file doesn't load is Puppy ONLY loads SFS files named pup_more.sfs or pup_devx.sfs, so rename your SFS to "pup_more.sfs".
You could rename it & try it just for the heck of it, but if it loads but doesn't
work you should probably do the SFS file again with MU's instructions.
...Terry
THANKS YOU ALL ! You are great programmers, really !
...so now i can create squash files i will begin to do a few and you will see SFS popping up... heu, when i will have managed not to put everything into / sorry
Best regards,
Laurent.
I don't know why your files went to "/".
I said:
I usually do it on an external partition:
Lets say I have:
/mnt/sda6/sfs/usr/local/bin/example.sh
Then I type:
cd /mnt/sda6
mksquashfs sfs EXAMPLE_215.sfs
This creates the sfs in /mnt/sda6 , not in /mnt/home, so I finally must move it manually there.
But I dont think this will be the problem you have, I just have no other idea at moment.
Mark
I said:
I think this should work, but maybe I oversaw something?cd /mnt/home
mksquashfs /root/sfs EXAMPLE_215.sfs
I usually do it on an external partition:
Lets say I have:
/mnt/sda6/sfs/usr/local/bin/example.sh
Then I type:
cd /mnt/sda6
mksquashfs sfs EXAMPLE_215.sfs
This creates the sfs in /mnt/sda6 , not in /mnt/home, so I finally must move it manually there.
But I dont think this will be the problem you have, I just have no other idea at moment.
Mark
Post deleted,
wrong thread, sorry.
wrong thread, sorry.
Last edited by vtpup on Sat 21 Feb 2009, 02:04, edited 1 time in total.
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.MU wrote:http://www.murga-linux.com/puppy/viewtopic.php?t=29194
Mark
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.
Puppy Linux's [url=http://www.murga-linux.com/puppy/viewtopic.php?p=296352#296352]Mission[/url]
Sorry, my server is down atm!
Sorry, my server is down atm!
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
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