I have never created an SFS and hence the questions.
From what I read on puppylinux.com website, SFS is the top layer and any file in this layer will override (not physically) the same file in any other layer.
Based on the above understanding, I created an SFS and many files worked as expected. But the below 3 files did not.
1 - /root/.xinitrc - My version in the SFS was not used. Instead the already existing version was used.
2 - /root/Choices/ROX-Filer/PuppyPin - The wallpaper in the SFS version was picked up correctly. The SFS version had no icons on the desktop. But when the SFS was loaded, all the default icons appeared.
3 - /etc/windowmanager - I had changed this to icewm in the SFS. But even after loading the SFS, it continued to go to jwm. And this file was unchanged.
Can anyone explain what is going on? Or please correct me if my understanding is not right.
SFS - How does it work?
files in the savefile (pup_save.2fs) always have a higher priority.
You can find them in /initrd/pup_rw/
There acctually is no way to workaround this, as this could break the users settings.
So to change those, you will have to write a script/dialog, that offers to overwrite them (creating backups maybe).
Concerning the Pinboard-icons:
this is done by Barrys approach, to add/remove icons to the desktop.
That script creates backups of puppypin, and restores them.
imho this approach is problematic, right because of the issues you have.
In Muppy I deactivated this I think, but don't remember, where.
I think it was /usr/sbin/fixpuppypin.
Another approach to add icons I posted here:
http://www.murga-linux.com/puppy/viewtopic.php?p=180206
This script could be run by a "sfs-observer" script.
That would check for a configfile in the SFS, and then add them to the pinboard using my script.
It would create a config-file, of what it added.
If the sfs would be removed, the icons from this configfile could be removed (if they were not used by another sfs/config either).
I'd like to write such a tool for Muppy, but had no time yet.
Mark
You can find them in /initrd/pup_rw/
There acctually is no way to workaround this, as this could break the users settings.
So to change those, you will have to write a script/dialog, that offers to overwrite them (creating backups maybe).
Concerning the Pinboard-icons:
this is done by Barrys approach, to add/remove icons to the desktop.
That script creates backups of puppypin, and restores them.
imho this approach is problematic, right because of the issues you have.
In Muppy I deactivated this I think, but don't remember, where.
I think it was /usr/sbin/fixpuppypin.
Another approach to add icons I posted here:
http://www.murga-linux.com/puppy/viewtopic.php?p=180206
This script could be run by a "sfs-observer" script.
That would check for a configfile in the SFS, and then add them to the pinboard using my script.
It would create a config-file, of what it added.
If the sfs would be removed, the icons from this configfile could be removed (if they were not used by another sfs/config either).
I'd like to write such a tool for Muppy, but had no time yet.
Mark
[url=http://murga-linux.com/puppy/viewtopic.php?p=173456#173456]my recommended links[/url]
@MU:
Thanks for the quick reply.
I guess, I will just have to add a script that can be run after the SFS is loaded that can change the required files, lines.
Also thank you for the easy dir2sfs script. This is what I used to create the SFS.
Thanks for the quick reply.
I guess, I will just have to add a script that can be run after the SFS is loaded that can change the required files, lines.
Also thank you for the easy dir2sfs script. This is what I used to create the SFS.
[url=http://macpup.org][b]Macpup - The beauty of linux[/b][/url] [b] | [/b] [url=http://pritlog.com/][b]Pritlog - Simple blog app[/b][/url]
Here is another question. But about pet files.
Suppose I have /root/.xinitrc in a pet file - this would overwrite the existing .xinitrc file - right?
Also, what will happen when this pet is un-installed? Is there anyway to get back the original .xinitrc file?
Suppose I have /root/.xinitrc in a pet file - this would overwrite the existing .xinitrc file - right?
Also, what will happen when this pet is un-installed? Is there anyway to get back the original .xinitrc file?
[url=http://macpup.org][b]Macpup - The beauty of linux[/b][/url] [b] | [/b] [url=http://pritlog.com/][b]Pritlog - Simple blog app[/b][/url]
>Suppose I have /root/.xinitrc in a pet file - this would overwrite the existing .xinitrc file - right?
yes.
>Also, what will happen when this pet is un-installed? Is there anyway to get back the original .xinitrc file?
No.
Also here,you had to add a script, that backups/restores.
I think pets can include a postinstall.sh file (or similar), that is executed after installation.
Here you could run such actions.
Mark
yes.
>Also, what will happen when this pet is un-installed? Is there anyway to get back the original .xinitrc file?
No.
Also here,you had to add a script, that backups/restores.
I think pets can include a postinstall.sh file (or similar), that is executed after installation.
Here you could run such actions.
Mark
[url=http://murga-linux.com/puppy/viewtopic.php?p=173456#173456]my recommended links[/url]
Thanks again Mark. I remember there is a Pinstall script that gets executed after the pet installation. But I dont know if there is a script that can be executed when the pet is being un-installed.
[url=http://macpup.org][b]Macpup - The beauty of linux[/b][/url] [b] | [/b] [url=http://pritlog.com/][b]Pritlog - Simple blog app[/b][/url]
http://puppylinux.com/development/createpet.htmThis is an optional script that you would have to create yourself. Very few PET packages need this. Ditto for the post-uninstall script.
Mark
[url=http://murga-linux.com/puppy/viewtopic.php?p=173456#173456]my recommended links[/url]