How to build your personal SFS Puppy

How to do things, solutions, recipes, tutorials
Post Reply
Message
Author
R-S-H
Posts: 487
Joined: Mon 18 Feb 2013, 12:47

How to build your personal SFS Puppy

#1 Post by R-S-H »

Hi.

Most of you surely already do know: I like to run my applications from sfs without using a save file (pupmode 5). To make this possible the easiest way for any other Puppy Linux user, I did decide to make this little guide here.

Two things are needed:

1. Shinobar's sfs_load version 1.9.x has to be installed
2. The attached script (remove the fake .gz and make it executable)

Ok, here's what to do if one wants to make this usable for a firefox.sfs and its executable would be named firefox.

1. Make a copy of my_sfs_runscript.sh and rename it to my_firefox_sfs_runscript.sh
2. Open it in geany or any other text editor
3. Change NameOfProg="alsaplayer" to NameOfProg="firefox"
4.
- a: Change NameOfSFS="LP2_ALSAPlayer-0.99.81.sfs" to NameOfSFS="firefox.sfs" or
- b: Add path to the sfs name and change NameOfSFS="LP2_ALSAPlayer-0.99.81.sfs" to NameOfSFS="/your/path/to/sfs/firefox.sfs"
5. Change NameOfDependentSFS"" to NameOfDependentSFS"TheRealNameHere" if maybe python or such things are needed (not yet surely)
6. If you don't want to have the sfs automatically unloaded after exiting the application, do make comments out of the following lines:
- CreateAutoUnloadScript
- /tmp/$BNameOfSFS.AutoUnload.sh
- rm /tmp/$BNameOfSFS.AutoUnload.sh
You could then also remove completely function CreateAutoUnloadScript - if you know what you are doing :lol:
7. Save the script

A single left click onto the script should now load the firefox.sfs and after this executing the firefox executable. But we all would not be in Puppy Linux, if it would be really that easy. Because it is not always that easy I did choose the firefox as an example.

Some applications like firefox and gimp do have already symbolic links placed in Puppy Linux. These symbolic has to be removed and this would result in a new issue. Files that are removed from the running OS usually are not seen if an equal file is loaded with an sfs. That's why a remaster of your puppy is needed in such cases. So, check your puppy first for symbolic links in /bin, /sbin, /usr/bin and /usr/sbin for each and every sfs you want to use. Remove these symbolic links and do a remaster.

Ok, let's assume that one has removed all those symbolic links and done successfully a remaster. The OS is then ready to use this feature completely.

Do the above noted steps on every sfs you want to use this way and create all the scripts needed. Now, after all scripts are created you have to make a decision: How do I want to use these runscripts?

- from a directory outside the OS (hd, usb) or
- from within the OS (maybe from a menu entry?)

Ok, let's assume one decides to use this from within the OS, from a menu entry or desktop icon (button).

Here's what to do:

1. Put all the scripts into /usr/local/bin
2. Create a directory in /root named menu_entries and open it in rox
3. Do this for each sfs file you did create a runscript for
- Open the sfs file with left-click onto it
- go to /usr/share/applications (inside the sfs's path)
- copy the needed .desktop file to /root/menu_entries
- search for the icon of the application (might be /usr/share/pixmaps or the application's directory)
- copy the icon to /usr/share/pixmaps (inside the OS)
- Close the sfs file again with left-click onto it
4. Do this for each .desktop file in /root/menu_entries
- open it in geany or any other text editor
- change its Exec= entry and replace it with the name of the runscript (my_firefox_sfs_runscript)
- remove any path from its Icon= entry (just use the name)
- save the .desktop file
5. After all .desktop files are edited move them to /usr/share/applications (inside the OS)
6. Open a terminal program and enter fixmenus
7. Check the menu for the new entries and icons
8. If everything seems to be fine, remove /root/menu_entries
9. Do a remaster

Done!

If anyone has problems using the remaster function, let me know. I will do the second post as a placeholder for this.

Have fun with your new SFS Puppy! :)

RSH
Attachments
my_sfs_runscript.sh.gz
(3.07 KiB) Downloaded 520 times
Last edited by R-S-H on Thu 14 Mar 2013, 04:31, edited 2 times in total.
[b][url=http://lazy-puppy.weebly.com]LazY Puppy Home
The new LazY Puppy Information Centre[/url][/b]

R-S-H
Posts: 487
Joined: Mon 18 Feb 2013, 12:47

#2 Post by R-S-H »

Placeholder
[b][url=http://lazy-puppy.weebly.com]LazY Puppy Home
The new LazY Puppy Information Centre[/url][/b]

nooby
Posts: 10369
Joined: Sun 29 Jun 2008, 19:05
Location: SwedenEurope

#3 Post by nooby »

Quote
Sub_title: An easy guide for the Puppy Linux users, but: dedicated to nooby!
/Quote

Ah thanks. I make a bookmark link to it and keep it in mind
for to use it when I am ready for to apply it. Much appreciated.

Hope many try it out and give you feedback on it.
I use Google Search on Puppy Forum
not an ideal solution though

pl3589
Posts: 12
Joined: Thu 07 Mar 2013, 03:46

Unable to extract script

#4 Post by pl3589 »

I haven't been able to extract your script.

This is my first time doing this, so it may be something wrong that I'm doing.

Clicking on the file I get the prompt "do I want to decompress the file?" When I click on "yes", the prompt goes away, but nothing else happens. The file does not extract.

I opened a terminal, and tried tar and gzip, but I always get a "not in gzip format" error.

I redid the download a couple of times, just to try to make sure I didn't have a corrupt download. But I get the same results every time.

User avatar
tallboy
Posts: 1760
Joined: Tue 21 Sep 2010, 21:56
Location: Drøbak, Norway

#5 Post by tallboy »

R-S-H wrote:2. The attached script (remove the fake .gz and make it executable)
tallboy
True freedom is a live Puppy on a multisession CD/DVD.

pl3589
Posts: 12
Joined: Thu 07 Mar 2013, 03:46

#6 Post by pl3589 »

tallboy wrote:
R-S-H wrote:2. The attached script (remove the fake .gz and make it executable)
Oops! Thanks for the assist!!

.

hamoudoudou

from a menu entry or desktop icon (button)

#7 Post by hamoudoudou »

"Ok, let's assume one decides to use this from within the OS, from a menu entry or desktop icon (button)."
bookmarked

Post Reply