Puppy Linux Discussion Forum

[shinobar]

Test release: sfs_load-1.9.3.pet (2012-05-01)
NLS (seperated from 1.9.3): sfs_load_NLS-1.9.3.pet
[url]Download: http://shino.pos.to/linux/puppy/[/url]
Small improvement from 1.9.2:
#1 Mar 2012 v1.9.3: fix was clean up whiteout do not see pup_z, incleased RESERVHDD/RAM, version info, jwm -reload without flicker
Messages are refined by jemimah, in the English NLS in the main PET.

[shinobar]

Test release: sfs_load-1.9.4.pet (2012-05-07)
Download: http://shino.pos.to/linux/puppy/

#6 Mar 2012 v1.9.4: fix excess(>6) load was messing up with some version of busybox(lupu), fix was menu disappeared for excess sfs, fix was error but already mounted, avoid 'losetup -d' for some kernel
#6 Mar 2012 v1.9.4: fix 'restart X' warning, never use external download_file, 'Back to sfs_load' button, gtkdialog4

Note that this is a test release, but has many important fixes. All users and pupplet makers using version 1.9.x series are recommended to upgrade.

[puppypeter]

Typing "sfs_load --help" generates:-

usage: sfs_load [--unload] [--cli] [+/-][EXTRA_SFS_FILE]
Load or unload extra sfs files on-the-fly.

Two questions:-

1. What's the "--cli" option for?

2. Do "sfs_load --unload xxx.sfs" and "sfs_load -xxx.sfs" do the same thing? If not, what's the difference?

Many thanks.

[shinobar]

[shinobar]

Test release: sfs_load-1.9.5.pet (2012-05-21)
#19 May 2012 v1.9.5: fix was no move but always copy
#18 May 2012 for lupu-528JP: SUPPORTSIG=yellow

Download: http://shino.pos.to/linux/puppy/
NLS (seperated as for 1.9.3 and later): sfs_load_NLS-1.9.3.pet

[shinobar]

Download: http://shino.pos.to/linux/puppy/
Test release: sfs_load-1.9.6.pet (2012-05-31)
NLS (seperated as for 1.9.3 and later): sfs_load_NLS-1.9.3.pet

#31 May 2012 v1.9.6: fix was everytime rc.update run when the number of additional sfs > 3, also when >6

[majorfoo]

[shinobar]

[`f00]

A bit less technical (mmhm, manual is good practice/exercise)

The words are mostly in a screenie @387k, not so much bigger than the jpg I did along with. Until I get racy (and my old personal sfs') squared away, any large stuff on disc will have to wait (a few mm sliver on the rim is all that's left and I'm really set on keeping it on cdrw disc if I can).

As more than a few have found, a running devx helps with damage control (the wm in the cap reverts to less than a joy if the devx isn't loaded). Maybe I'll check out what's after 1.4 stable (small I can do on the near horizon).

Good work, all

[peebee]

Hello all the SFS experts....

The way I like to manage sfs's on my system, given that I frugally install and test quite a few Puppy versions, is to put each Puppy version into it's own subdirectory but put all the sfs's into a common directory.

I then create a symlink in the Puppy subdirectory to the sfs I want to use in the common directory and then load it with sfs-load-on-the-fly.

This seems to work 100% for some sfs's but for some when I reboot I get the "Configuring filesystem - next boot will be quicker" message as though the boot system always thinks that the sfs has been newly loaded.

So I'm wondering why do different sfs's behave differently in this respect?? and is there anything I can do to make them all be permanent on reboot in this way of working?

Many thanks for any insights or help anybody can provide. It's not a showstopper as obviously I can copy the "misbehaving" sfs into the Puppy subdirectory rather than making a symlink.

Cheers
peebee

[Jasper]

Hi peebee,

It seems you are linking individual sfs files. Whilst every sfs may not work in every Pup - I wonder what would happen if you were to link the sfs directory instead of individual files?

SFS-Exec from seaside may be an alternative to load-on-the-fly since either can be used at any time.

My regards

Addendum: now deleted, as my thoughts were useless..

[RSH]

Hi shinobar.

You remember the command --skip-fixmenus? Thanks for introducing this.

LazY Puppy has installed sfs_load 1.9.4 but version of 1.3.9 (the one with my modifications inside) also. For a special use of LazY Puppy from CD/DVD i did made some new modifications on 1.3.9, that makes me able, to run the complete system from CD/DVD and to load the sfs by the RunScripts from CD/DVD without the need to click/confirm the "copy-GUI". So, maybe I'll have something new to be introduced in a new sfs_load version?

I did insert the following code at the very beginning of the 1.3.9 script:

[Pelo]

DPUP485 inside Precise Puppy for instance.
I load the DPUP485 SFS and it runs. That's all.
Same for LHP 503
Same for Fluppy 013.
These three distros were unable to connect Internet on my new Laptop but mounted on the fly on A recent Puppy 5XXXX, they go back to life !
With all their programs (...quite all)

[vicmz]

Spanish locale updated

[01micko]

I have fixed and uploaded sfs_load for crashing the system if you are using kernels greater than 3.2. NOTE: not tested on k3.8, reports please.

Many thanks to SFR

Package:
http://mirror.aarnet.edu.au/pub/puppylinux/pet_packages-slacko14/sfs_load-1.9.6-2.pet