I like to run my LazY Puppy without the use of a save file but wanted to run as many programs as possible. So i wrote the LazY Puppy SFS P.L.U.S. to be able to have scripts inside the remastered system that will be executed from a menu entry (or desktop button) and do execute programs from sfs files (mounting and loading the sfs is done in background). No more need to run sfs_load from the menu before running a program (but it needs to be installed ---> 1.9x!).

The LazY Puppy Lazarus SFS needs to have the devx loaded to be able to compile pascal source codes. The converted Lazarus SFS "knows" that it needs the devx, so it does load the devx automatically!

While converting to LazY Puppy SFS P.L.U.S. Format the user gets option to "tell" the sfs what else sfs is needed to run and also what else sfs does conflict with the converted sfs ---> it then will not load, if the conflicting sfs is already loaded. It then gives option to unload the conflicting sfs and loads the new sfs after that.

There are some more options that will explain itself while using.

The attached .pet contains:

- a tool to convert a sfs file to LazY Puppy sfs format (the sfs file needs to be renamed ---> just add prefix "LP2_" in front of the filename)
- a tool to create RunScripts from converted sfs file (must not be in use or mounted before that)
- a tool to add dependencies to a converted sfs (If the user adds NOGO-dependencies a new RunScript has to be created!)
- a tool to combine a converted sfs with all its dependencies (makes single sfs from all of them ---> would be: combining the Lazarus and the devx)

All these tools can be executed by a right-click on a SFS file and also from the menu Utility.

Recommendations:

I do recommend to install the attached .pet into a clean and fresh system (load to ram, no save file) and then to make a remaster after installing the SFS_PLUS.pet and building all needed and/or wanted RunScripts from your favorite (then converted) sfs files.

For the fastest result of loading the sfs and running the program from the RunScript it's recommended to place the sfs files inside the boot directory of your puppy.

SFS P.L.U.S. in Precise 5.3.3.3

By the way: I do run currently Programs from 273 SFS Files using a remasterd Version of the LazY Puppy 2.0.2 Final (Web) Version. Not all at the same time and not every day.

But I can use different versions of programs like gimp in 2.6.10, 2.6.11, 2.6.12 and 2.7.3. I can use Openshot 1.3.1 and KdenLive 0.7.8 which willl never work if I would install them into my LazY Puppy. All from the menu and all without the need to use a save file!

My private LazY Puppy OS is by now 110 MB the iso and 106 MB the sfs file ---> and it contains the whole LazY Puppy Menu Suite, LazY Remaster Suite and lots of stuff that is not installed in the original lucid 528-4 like xdotool, Design Switcher, Sound Switcher, LazImUl, Backup Settings and more...

It is nearly the smallest possible OS with the most immediately usable software without to have to install it and to use a save file. This attached .pet will (hopefully) bring your puppy a big step forward using software without the need to have problems on installing any software.

I hope you'll like this.

RSH

Updates/Changes:

2.0.5

- it checks now, if gtkdialog4 is installed (now uses gtkdialog3, if gtkdialog4 is not installed)

Hello,
Agree with the concept completely..
Will D/L and play with..
Let ya know how it goes, and on what..
_________________Close the Windows, and open your eyes, to a whole new world
I am the Admin of the
Puppy Linux Users Group on Facebook
Join us!
Puppy since 2.15CE...

I like to run my LazY Puppy without the use of a save file but wanted to run as many programs as possible.

The quote caught my attention. It perfectly states one of my goals. As I understand it, Lazy Puppy 2.0.2 Final and Lazy Puppy Plus 2.0.0 are a bit different, but each work somewhat in the way that I am wanting to accomplish with Fatdog64-601.

That’s it. Is this possible?

As I understand it currently, Fatdog64 requires to install the apps sfs and then reboot with saving... see quote above!

I hope a bit more detail won’t be off-topic. I have tried Lazy Puppy 2.0.2 Final and although it would acquaint me with how it works, not being 64 bit means it is not a resourceful solution for a new machine with 16GB RAM.

It boots OK, but it appears to me that my hardware is too new for this version and my particular Realtek chipset is not recognized. So, I cannot download the customized sfs files to try out and learn if this is what I want.

Just 4 weeks ago I bought my first 64 bit machine. In other interests, I have been watching Ubuntu for Android, so I was aware of Ubuntu64. I left the Win7 drive in long enough for it to register at “headquarters” (I guess it did, but I don’t care really) then pulled it out and began the adventure with Ubuntu64 (No HD). First, from a Live CD boot and then moved to booting from the USB port. Still in search of the place I wanted to go, I found Fatdog64 and USB booted that. Fatdog64 recognizes all resources I use on this machine. If it doesn’t work for something on this machine, I don’t know and don’t care.

Still, I want to boot a generic base “live” distro configuration and elect to load additional apps (or not) as I want. Doing this at boot time or later (from my reading, I understand Lazy Puppy Plus 2.0.0 does this while running) isn’t a deal breaker either way. However, as I understand the way Lazy Puppy Plus 2.0.0 to work I would not be booting a base configuration.

The “base configuration” consideration is important to me since I am away on long trips a lot and might want to put my USB into a different machine and be able to boot a base distro configuration if needed.

I hope my reasoning is correct. Moreover, I hope my reasoning is clear and there will be some helpful comments! All guidance will be appreciated.

1. Yes, SFS P.L.U.S. 2.0.0 (now 2.0.1) is different to the SFS P.L.U.S. version which is used in LazY Puppy - so, do not install this here into LazY Puppy. It's made especially for any other puppy than LazY Puppy.

2. You should boot a fresh and clean Puppy (RAM, no save file) and install SFS P.L.U.S. 2.0.1. Then do a remaster immediately.

3. If SFS P.L.U.S. 2.0.1 is installed, you should be able to create RunScripts from each and every SFS file you want and can be opened (to grab the needed information) by SFS P.L.U.S. 2.0.1.

Note: I have found some sfs files from time to time that could not be opened by LazY Puppy (I think it was because of different compression of the sfs)

4. If SFS P.L.U.S. 2.0.1 was able to open the sfs file, you should see the SFS P.L.U.S. 2.0.1 GUI which shows the .desktop files included in the sfs file. Select every .desktop file you want to create a RunScript of.

There will be a message when the job is done. After this you should find the RunScript/s in /root/.my-sfs-scripts (symlink /root/SFS-RunScrips)

Note: to create a RunScript from the .desktop file inside a sfs file, the sfs file must be converted to LazY Puppy format - please, read information at first post on that.

This package offers 4 applications: RunScript builder, SFS to LazY Puppy converter, Add dependencies (dependent sfs files), Combine with dependencies (builds a single sfs from the main sfs and its dependent sfs files. All are right-click applications, but can also run by the menu, using a GUI to select a file.

If a RunScript could be created and the sfs could be converted to the LazY Puppy format, then everything should work fine. Now you can create all RunScripts from every sfs you want.

All RunScripts shown at the Image above are "installed" in my LazY Puppy - so, you should do a remaster after creating all RunScripts and select option to put .desktop files and icons into your running puppy. Menu entry will call the RunScript (instead of the program) and the RunScript will execute the program. If the sfs is not loaded, it will load the sfs and run the application after this. If the sfs is not inside the boot directory of your puppy, it will download the sfs from the web, if you did give a download link at creating the RunScript and have already uploaded it (works not, if stored at mediafire or other file hosters; needs possibility of direct acces to the file; this uses the wget of puppy). It downloads to the bootdirectory, loads the sfs after this and runs the application.

Give it a try and install it as described. Tell me the results. If something's going wrong, I will try to give help, to get this to work. But it should work out of the box, because I have successfully installed this in Lucid 525 & 528, Slacko 5.3, Studio 13.37 and in Precise 5.3.3.3 (and done remasters of these puppies, for a later use (maybe)).

RSH

BTW. the execution of a RunScript checks md5sum automatically at download of a sfs and gives information, if md5sum doesn't fit.

Hi RSH !
I find find the idea using sfs files quite cool although i can not really estimate advantage-disadventage over pet files .
From my intuition i prefer sfs files .
I am substituting more and more of my programms with sfs type files .

I do prefer to use sfs files because I can use them without to use a save file. Also it makes me able to use different versions of programs and/or different programs, which would conflict if they were installed because of different versions of qt (f.e) used by these programs.

So, the way I do use this in LazY Puppy, I can use KDenLive and Openshot and I can change which one to use without to reboot. If i would install them, they would conflict, so, one or the other would not work/run.

Also I do prefer to use my LazY Puppy without any save file and it is easy to load and/or unload a sfs. If you would try to uninstall a installed package, it can remove needed libs, overwritten at installing process, but needed by other installed applications. SFS doesn't remove anything except its own files.

I can currently use Applications from 285 different SFS Files just by clicking the menu entry of the application (using te SFS P.L.U.S.). That's pretty cool and so I did choose to make a version of SFS P.L.U.S. for other puppies - but the currently used version in my LazY Puppy is a bit forward to this here version

But, not to forget: it would be nothing at all, without the amazing sfs_load by shinobar. He's a very friendly guy and did include my suggestion of a special command to use for the LazY Puppy SFS handling which is now called --skip-fixmenus (in version 1.9.x and above).

Ooops me a month late or something
but on the other hand I am too noob
to even be sure I get what you write.

1.
I love Spotify and have now two versions
one on Slacko and one on Upup Precise
and I wonder if you have included Spotify
as sfs?

2.
That you don't need save file after the first
remasterning is great. Does that mean you
have protection in same way as those who
only use CD/DVD? You can have frugal
install an when you shut down the malware
is gone? Or maybe it has downloaded itself
to the HD in the background?

3.
is it possible to make a sfs version that works
for your OS of this linux program?

A few weeks ago you did ask me for the Make Human Application to run in my OS. I gave it a try but there are too many libs missing. I do not have the time to search for all those libs. Just forgot to pm you. Sorry.

To 1.: I don't know Spotify. So, if you can post me a link to a .pet etc. I could try to build a sfs for LazY Puppy from this. I would also try to compile, if I would get a link to the sources... ...why not. But a .pet would be better solution for me.

To2.: Yes, I'm save, because after reboot everything saved inside LazY Puppy will be gone. No, I'm not save on "downloading itself", because I do use the LP2_Firefox7.sfs, so, the boot partition is mounted.

However: I do use my LazY Puppy at my home workstation 100% without any save file and I can use more than 350 Applications from 285/286 sfs files just by clicking the programs menu entry, which is included at creating a RunScript process and then remastered. I have scripts from 93 sfs files inside the LazY Puppy main sfs file. The rest is inside the LazY Puppy extension sfs file, which can be loaded by a separate menu entry, to get access to all programs.

I do run this from USB Stick on my three different computers and also on seven different computers at my favorite internet cafe. I'm totally happy with LazY Puppy, especially because of its sfs handling.

I personally do use a cut down version, sized 110 mb. You remember? Some time ago, I told/asked you as a reply of one of your posts somewhere on the forum to make LazY Puppy smaller ---> done. _________________LazY PuppyRSH's DNASARA B.

Okay about the Make Human. I will have to use Ms Win for that one then

Spotify for Puppy is here
Tempesteous version for Slacko with .pet files and then Pemasu's version
for Upup Precise having both pet and sfs. both in same thread.
Both work for me on my small Acer D255 Netbook

"Take me down to the Paradise Puppy
where the Sources are open and the users are happy,

oh won't you please take me home."

Freely taken from... (you surely know whom)...

---

I know you've had downloaded LazY Puppy 1 (528-4) which was already then mainly a sfs puppy - including some installed applications. LazY Puppy 2.0.2 Final is a huge step forward from that point. Mainly for its SFS P.L.U.S. but also for lots of new created tools and modifications of installed scripts.

Let me give to you -and also to other users- a short overview how comfortable it is, to use LazY Puppy and especially its SFS P.L.U.S. - if one can boot and use it on the personal computer.

I have set the default action for .mid/.MID files to the RunScript created from the LP2_TiMidity2130.sfs. The RunScript is included inside the LazY Puppy main sfs. I have set three different symbolic links inside /root/.config/rox.sourceforge.net/OpenWith/.audio_midi (Customize Menu). Now, if I do click a .mid/.MID file, the RunScript loads the LP2_TiMidity2130.sfs file, executes timidity and plays the MIDI file. Doing a right-click on a MIDI file i can play the file in background (the sfs is also loaded then). Third option is to kill timidity background playing.

If the sfs file is not available at bootdirectory the RunScript downloads the LP2_TiMidity2130.sfs from the LazY Puppy Repository at smokey01.com (thanks again to smokey01. ), loads the sfs after successfully downloaded, executes timidity and plays the file.

The exactly same way it is configured for images with gimp at right-click action All of this stuff is done automatically from each and every created RunScript - including to load dependent sfs files.

Unfortunately I have done this for .mid/.MID files after uploading the latest iso files. But for gimp it works as described wit the downloadable iso files.

OK, there is one more main feature (not the last one): the LazY Puppy LazY Remaster Suite.

I have nearly "rewritten" the original puppy remaster script and created a front end, a GUI to use the new remaster script from a GUI call. I can set the 4 different main remaster modes inside the GUI (do not configure /root and /etc, give option to configure /root and /etc, configure /etc like it is done in the original remaster script and full remaster for the use with only the current used computer.

I can set lots of options which are usually kept for the new remaster if one would edit /root and /etc manually at remaster process. So, I can remaster the de iso to en iso just by clicking checkboxes inside the GUI.

I can rename the LazY Puppy and if I would remaster it and rename it to let's say, Hurray Puppy, it replaces all "LazY Puppy"-named menu entries to "Hurray Puppy". Also inside the GUI, because I do use mainly $DISTRO_NAME from /etc/DISTRO_SPECS.

I can enter the new name of the iso to build and its label inside the GUI. I can give symbolic links to .pet files and some other file types, which will be installed automatically into the running system before remastering begins.

Just clickong some boxes, entering some text and "move" some files as symbolic links into specified directories which can be opened from inside the GUI.

Now, you understand?

"Take me down to the Paradise Puppy
where the Sources are open and the users are happy,

oh won't you please take me home."

So, to get a new LazY Puppy to include some new RunScripts, I do boot LazY Puppy to RAM without save file (as usually), create the RunScripts, call the LazY Puppy Remaster Suite, enter a new name for the iso and its label and click on remaster button. Done.

Relevant files and directories in /root will be kept for the new iso, if options are set inside the GUI.

The whole thing doesn't take too much time compared to save a save file on usb stick. So, others do save including the risk to lost the whole save file while using the puppy. I do save permanently and even as comfortable like saving to a save file.

I am convinced, lots of my created stuff inside the new remaster script should be default in each and every remaster script of all puppies. Also the GUI.

Happy Happy Happy

That's just all, I can say! _________________LazY PuppyRSH's DNASARA B.Last edited by RSH on Sat 01 Dec 2012, 06:11; edited 1 time in total

I have successfully build a Spotify sfs for LazY Puppy, created a RunScript including desktop icon, and could run Spotify by clicking the desktop icon ---> seems to work, but I could not test completely. I'm not registered, I don't want to register and so, I can not log in.

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