This here is the translation of this post:
http://murga-linux.com/puppy/viewtopic. ... 339#668339
Nooby, DrDeaf, there is some new information at the post above.
---
Hello backi.
I reply in German language, because I don't have time to think and write this in English language at the moment.
I know the program you are talking about. The SFS-Exec by seaside. I have tested it and it seems to be useful. But it has some disadvantages compared to SFS P.L.U.S.
If running a program (right-click on sfs) via sfs-exec, then exiting the program and run later again via sfs-exec will mount/open the sfs again, if it wasn't manually unmounted before that.
One more disadvantage is the use with sfs files containing several applications. Using sfs-exec on the LazY Puppy LP2_AudioStudio.sfs doesn't work, nothing happens after the right-click.
Also it is needed to have the directory of the sfs files opened in rox (which means, several directories if the sfs files aren't stored at the same place).
I currently use a LazY Puppy version sized 110mb the iso and 106mb the sfs file. I have a extension sfs file sized 14mb, so the whole system is 120mb, which is smaller than the original lucid 528-4. But it has a lot of stuff installed, which is not installed in the lucid 528-4, like: xdotool, DesignSwitcher, SoundSwitcher, BackupSettings, LazImUL and many more.
Using the extension sfs my LazY puppy version currently has 442 RunScripts of 442 Programs from 286 sfs files. Each and every single program can be executet by its menu entry (or desktop icon, if created at building the RunScript) and all without the need to use a save file.
At home I don't use a save file to 100%, except doing some special testings where it would be needed. In my drumming room I do use a LazY Puppy derivative, named Osiris Studio, which has already installed all main audio applications. On this system I do use currently a save file sized 512mb.
I surely don't want to degrade seasides work on the sfs-exec, which would be surely helpful a lot at my work to create the SFS P.L.U.S., if I would have found it earlier. But I think SFS P.L.U.S. is currently the best what Puppy Linux has to offer in case of SFS use and handling.
The above named facts should demonstrate this clearly. I'm totally sure about this ---> but we should have some attention on sunburnt's AppPkg stuff.
Also I think it is similar to LazY Puppy. It is currently one of the best puppies we do have to offer. The problem that it could not be used on every computer isn't LazY Puppy specific, it's generally Puppy Linux or maybe Linux specific - so, never mind.
To the lucky ones who can run LazY Puppy on their computers and also want to use this puppy, it is surely a Paradise Puppy - even if it doesn't come with the all newest software.
I have found in Puppy Linux (because of the lucid 528-4 by playdayz and 01micko) a lot more than I could imagine after I had to quit my search for newer software for the muppy 08.3F which I've used in 2010. I've given everything I've found and some more back to the puppy community and LazY Puppy is now my Main OS on every computer i do use.
There's only one reason for me to use windows now. This is the recording of Drum-Solos, because my video software does only work with the hardware equipment and revert. Could not be installed and used in Wine. But I do plan to do all the after recording work for a drum video using Openshot and KDenLive in LazY Puppy on my next drum video recording session. If possible, all Live in RAM, without a save file . just to point out that it would be possible.
---
So, 442 programs from 286 sfs files is surely not bad. But that's not all. The version of SFS P.L.U.S., currently running in my private version of LazY Puppy doesn't only handle everything for the use of sfs files.
It can create RunScripts for applications to install in wine. It loads wine automatically, downloads it, if not available at the local computer, executes wine, installs the install.exe (or setup.exe) and executes the installed program after ti has been installed. All from the menu, in RAM, no save file.
It can do exactly the same thing for the use with portable applications for wine (PortableApps), so, there is no need for me to use the PortableApps Starter. All from the menu... ... ...
And not to forget:
It can do exactly the same for the use of linux portable applications, which sometimes needs some stuff like python etc. All from the menu... ... ...
That's not all but should be enough for now.
RSH
EDIT:
I think, each and every .pet can be used as sfs file. If application from sfs doesn't run, but runs if installed, does mean there are one or more files that where installed and are also placed inside the sfs. These files do conflict, because to load sfs doesn't overwrite these files (installing does).
I have removed from my private version of LazY Puppy qt, sqlite, gtkmm, glibmm, goffice, mplayer and some more back ends including their front ends and do load them separately as single applications sfs files. SFS P.L.U.S. doesn't only load the sfs to run the wanted application, it loads also dependent sfs files (if defined). Example: Openshot needs python, so the LP2_Openshot131.sfs knows, that it needs the python. The RunScript checks the dependencies list of Openshot sfs and loads every sfs files which is listed in the dependencies list. The Openshot runs. Conflicting sfs files could be defined also. If so, then the RunScript gives option to unload the conflicting sfs before loading the new one.
Now, that my LazY Puppy version hasn't installed the qt, I can run and use Openshot and KDenLive - which would conflict, if they would have been installed. Both sfs files do "know" this, so their RunScripts will unload each other, if selected by the user.