the latest sfs_load 1.9.7 seems to have a bug which appears only on big sfs files.

In LazY Puppy I have installed two different versions of sfs_load. There is a modified version of 1.3.9 and also (original) 1.9.4. Using the modified version 1.3.9 it does load the LP2_LazarusFPCSuite.sfs without any problems - it's usable and works well after loaded.

When installing sfs_load 1.9.7 (1.9.6 seems to have this bug as well) and using sfs_load 1.9.7 to load the LP2_LazarusFPCSuite.sfs the files don't appear in the OS and also the sfs is not listed in $EXTRASFSLIST - even though, filemnt tells me it is in use by LazY Puppy when doing a single left-click onto the LP2_LazarusFPCSuite.sfs. So, it seems to appear in a pup_ro directory.

It is a huge file (308 MB) and it is loaded by its SFS P.L.U.S. RunScript which uses options: --skip-fixmenus --cli --quiet

I did try to go back to the 1.3.9 / 1.9.4 combination from LazY Puppy 202-005 for the use in my private LazY Puppy 3 version. The modified version of 1.3.9 works well on the Lazarus SFS, but the 1.9.4 has this bug already existing.

Both, the 1.9.4 as well as the 1.9.7 do load a 283 MB Wine SFS (Gecko and Corel Suite installed) fine, but do not load the Lazarus SFS (308 MB). Neither by the RunScript nor manually by right-click action!

When installing sfs_load 1.9.7 (1.9.6 seems to have this bug as well) and using sfs_load 1.9.7 to load the LP2_LazarusFPCSuite.sfs the files don't appear in the OS and also the sfs is not listed in $EXTRASFSLIST - even though, filemnt tells me it is in use by LazY Puppy when doing a single left-click onto the LP2_LazarusFPCSuite.sfs. So, it seems to appear in a pup_ro directory.

I would love some help making this a CLI sfs loader that works when X is NOT running.

I've been running a modified version of sfs_load-1.3 for over a year which I use to load SFS's at startup. Since I don't use a pupsave file I needed something besides Boot Manager to do the job. I stripped (commented) out all the code that required user input (do you want to copy? etc.) so that SFS's are loaded automatically.

I just exited to prompt and loaded an SFS with it successfully from the command line.

Code:

sfs_load-min /z.sfs

You can find my mods by searching for "jrb" in the script. You might have to compare with an unmodified version in some places. Looks like I deleted some sections rather than commented out.

I've been running a modified version of sfs_load-1.3 for over a year which I use to load SFS's at startup. Since I don't use a pupsave file I needed something besides Boot Manager to do the job. I stripped (commented) out all the code that required user input (do you want to copy? etc.) so that SFS's are loaded automatically.

The idea of jrb seems interesting.
This reminds me of another idea ...

For several weeks, I am looking for a utility that allows users to install sfs integrated into an iso image.

My idea: offer a Puppy light, while allowing the user to simply add some popular applications (webbrowser, image editor, etc..)This, without having to download the applications (sfs files will be included in the iso, but separated from the main Puppy sfs).

sfsload will be used to mount/unmount the sfs (with optionl cli). It remains for me to design a GUI, If someone wants help, this is possible.

I do run in my LazY Puppy a modified version of sfs_load generally (I started to do this with the 1.3.9).

Currently I'm running a modified version of 1.9.9 and I did similar things as jrb mentioned.

For the SFS P.L.U.S. RunScripts in LazY Puppy I can use the modified version of sfs_load to load sfs files from a specific location. So, I do have several LazY Puppys and do load all the sfs files from one directory 'Modules'.

I can 'patch' my RunScripts after its creation to switch the sfs files location easily and immediately without to create new RunScripts.

I would like to add the SFS P.L.U.S. together with shinobar's sfs_load as an official SFS Package - but I'm helpless... ..and lost...

The new sfs_load seems to have some issues. I'm not sure if it is because of the modifications I've made. Yes, the modified 1.3.9 works perfect and it has the same modifications inside.

The issue:

I've tried to remove an icon from /usr/local/lib/X11/mini-icons and also a .desktop file from /usr/share/applications - everything worked well, so far.

Then I've tried to edit another .desktop file and since I've removed Geany from my LazY Puppy, I did load the LP2_Geany-0.20.sfs to edit the .desktop file.

After editing the file and unloading the LP2_Geany-0.20.sfs the previous removed icon and .desktop file returned into the os !!!

Back to 1.3.9 and everything works well!

RSH

Btw: I don't use any save file!

ASRI éducation wrote:

My idea: offer a Puppy light, while allowing the user to simply add some popular applications (webbrowser, image editor, etc..)This, without having to download the applications (sfs files will be included in the iso, but separated from the main Puppy sfs).

My idea: offer a Puppy light, while allowing the user to simply add some popular applications (webbrowser, image editor, etc..)This, without having to download the applications (sfs files will be included in the iso, but separated from the main Puppy sfs).

LazY Puppy already can do this!

Hello RSH
I know your Lazy can do that, but the problem is that your solution is avaible only for your puplet.
I hope that this possibility becomes available for all Puppy ...

Off topic:
I've tested your Lazy, and I can say that it offers many interesting possibilities for users.
I'm like many geeks, I want to control my OS and its utilities, I like to test new versions while maintaining my favorites applications/utilities. With Lazy, I'm dependent on a version of its main developer, I lack of freedom (of course, my opinion is personal and subjective, it is only a reflection of my needs).
So, I encourage users to test/adopt lazy, but I also would like to propose adaptable good tools to other versions of Puppy.

Hello RSH
I know your Lazy can do that, but the problem is that your solution is avaible only for your puplet.
I hope that this possibility becomes available for all Puppy ...

To make this available and usable in any other Puppy (maybe except FatDog) we first need a command line option in sfs_load, to skip the copy function - so, the SFS can be loaded from its original location.

But, if using this from CD, it will lock the CD drive after loading the first SFS from CD !!!

If we would have the command line option to skip the copy function, I could offer my new SFS P.L.U.S. (currently v3.3.5), which now can create RunScripts from ALL SFS files - no need to convert the SFS first to SFS P.L.U.S. format (but is still usable). Also: SFS dependencies can be added into the SFS P.L.U.S. RunScript (SFS P.L.U.S. SFS files do have their dependencies declared inside the SFS). Each RunScript can have its own location to load from !!!

The user will be able then to load the SFS and run the Program from CD (and everywhere else) just by its menu entry (as it would be installed).

The new SFS P.L.U.S. 3.3.5 (LazY Puppy will be replaced by the Name of your Puppy because of DISTRO_NAME is used for this)

My only question is about the bootconfig.save function. It apparently has something to do with remastering, but I don't understand its purpose. I remaster occasionally, and ended up with an extra sfs loading automatically on boot in the remaster, though I had unloaded it with sfs_load before doing the remaster. Confusing.

I noticed BK also mentioned an issue with this function on his blog (in the comments):

Quote:

I did find what seemed like a problem. After using sfs_load, I then ran BootManager and unloaded the .sfs -- which does of course only take affect at next bootup, and after rebooting I saw that /etc/rc.d/BOOTCONFIG.save still had the .sfs in it's EXTRASFSLIST variable.

I think I was able to remove the function, by commenting out these lines in /usr/sbin/sfs_load (line 1380), like this:

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum