SFS file issues / concerns (Not-Quite Solved...yet)

Using applications, configuring, problems
Message
Author
slavvo67
Posts: 1610
Joined: Sat 13 Oct 2012, 02:07
Location: The other Mr. 305

#16 Post by slavvo67 »

Ahhhhh, so I'm not crazy!! I just haven't been able to recreate the issue, yet. I'm going to remove the "solved" and see if we can't get more insight here.

User avatar
mikeb
Posts: 11297
Joined: Thu 23 Nov 2006, 13:56

#17 Post by mikeb »

Other thoughts are sfs loader has some hacks to overcome puppies reverse layering .... that could be another possibility if it does something in reverse when removing.

In a normal world adding and removing should not change anything.

mike

slavvo67
Posts: 1610
Joined: Sat 13 Oct 2012, 02:07
Location: The other Mr. 305

#18 Post by slavvo67 »

Mikeb:

What sort of scripts are you using? You wouldn't happen to have one that searches for all mounted SFS files and does an "auto-unmount" would you? If not, I might just have to slap one together and have it execute for me at shutdown or something.

Slavvo67

User avatar
mikeb
Posts: 11297
Joined: Thu 23 Nov 2006, 13:56

#19 Post by mikeb »

Code: Select all

echo "Remove added modules"
ls -1 /initrd | grep -E '.sfs|.lzm' | while read I ; do 
	busybox mount -t aufs -o remount,del:/initrd/$I unionfs / 
	busybox umount /initrd/$I
done
this is what I have in my rc.shutdown to unload added modules... but in your case the detection would be something like grep pup_ and hide the failure to unmount the core layers.

Not sure if this would help your problem as I do this to ensure a clean shutdown if running in ram but sfs are mounted from the hard drive due to limited space (in ram)

mike

User avatar
solo
Posts: 389
Joined: Thu 14 Nov 2013, 20:33

#20 Post by solo »

I do recognize the unexplainable fluctuations in free space when installing or uninstalling. Sometimes, uninstalling a small package with the Puppy Package manager suddenly yields a lot more free space than I would expect to receive.

But I do not recall spectacular unexplainable differences where it concerns SFS files.

I do have to say, I do not use SFS-Load (on the fly) at all. I strictly load or unload SFS files through the Bootmanager SFS loader. This does mean I have to reboot every time I load or unload an SFS, but I am not bothered by that.

My pup save file is 504 MB, of which 251 mb is free. But I have Firefox, Inkscape, LibreOffice, Gimp, NVidea drivers and a nice game all loaded as SFS files. By exchanging SFS files in the Bootmanager, I can choose to load devx, java, Blender, Avidemux, Wine, or other games.

Oh I like SFS files a lot! :)

User avatar
mikeb
Posts: 11297
Joined: Thu 23 Nov 2006, 13:56

#21 Post by mikeb »

Sfs files are likable.... having no limits is nice...each machine has its own set of apps to load at boot (but by filename...no boot manager) and a stock of others to load on demand. Typically there are 10-20 loaded. Also means the core pup contains core libraries and yer basic tools and a browser....handy for quick boot/fix stuff.

I also find it the cleanest way to test a new application or compile since the system is left as was after wards (or should be...hence the topic here.)

Ok people...here is my sfs loader
usage is activate /path/to/file.sfs
or add the script to rox's right click menu.
it toggles load or unload...same script.

Try it and see if you still get this strange behaviour.

mike
Attachments
activate.tar.gz
(1.18 KiB) Downloaded 135 times

slavvo67
Posts: 1610
Joined: Sat 13 Oct 2012, 02:07
Location: The other Mr. 305

#22 Post by slavvo67 »

Sorry, I'm bringing this up again! This time, same issue with Virtualbox. I think that I'll convert SFS files to pets from now on... at least the old, somewhat obsolete PPM can still recognize when a pet has been installed and remove it.

User avatar
mikeb
Posts: 11297
Joined: Thu 23 Nov 2006, 13:56

#23 Post by mikeb »

well if you want proper sfs module handling use slax or porteus or rewrite half the scripts :)

mike

slavvo67
Posts: 1610
Joined: Sat 13 Oct 2012, 02:07
Location: The other Mr. 305

#24 Post by slavvo67 »

Porteus and Slax were my favorites before I went full-time puppy. Maybe I should play in their sandboxes some more...

User avatar
Karl Godt
Posts: 4199
Joined: Sun 20 Jun 2010, 13:52
Location: Kiel,Germany

#25 Post by Karl Godt »

mikeb wrote:
Ok people...here is my sfs loader

mike
Mike, your code has this line :

Code: Select all

RAMSIZE=`free | grep "Total:"| tr -s " " | cut -f 2 -d " "`
But my free has this output :

Code: Select all

bash-3.00# free
             total         used         free       shared      buffers
Mem:       3972280       915184      3057096            0       181408
-/+ buffers:             733776      3238504
Swap:     23366352            0     23366352
Around here ( rc.shutdown ) :
#110405 fix 'free' applet output format different in later versions of busybox.
Barry's code in pup_event_frontend_d does it like this :

Code: Select all

free_initrd_func() { #UniPup, runs entirely in initramfs.
 #110405 fix for later versions busybox...
 memFREEK=`free | grep -o 'Mem: .*' | tr -s ' ' | cut -f 4 -d ' '`
 swapFREEK=`free | grep -o 'Swap: .*' | tr -s ' ' | cut -f 4 -d ' '`
 SIZEFREEK=`expr $memFREEK + $swapFREEK`
 SIZEFREEM=`expr $SIZEFREEK \/ 1024`

User avatar
mikeb
Posts: 11297
Joined: Thu 23 Nov 2006, 13:56

#26 Post by mikeb »

Yes free in busybox has changed... more dumb linux stuff.

It also breaks the sfs loaded in lighthouse pup.

@slavvo67 nothing to stop you adding useful parts of puppy to slax... eg the wifi handling.

mike

Post Reply