sfs_load-2.4 on-the-fly
sfs_load-1.9.3
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.
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.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
sfs_load-1.9.4is out
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.
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.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
-
- Posts: 1
- Joined: Mon 21 May 2012, 00:46
sfs_load command line usage
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.
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.
Re: sfs_load command line usage
It depends on the version what option is accepted, but most recent sfs_load explains:puppypeter wrote:Typing "sfs_load --help" generates:-
usage: sfs_load [--unload] [--cli] [+/-][EXTRA_SFS_FILE]
Load or unload extra sfs files on-the-fly.
Code: Select all
# sfs_load --help
SFS-Load on-the-fly v.1.9.5
Load or unload extra sfs files on-the-fly.
usage: sfs_load [OPTION] [OPTION2 ...] [+|-][FILE_NAME] [+|-][FILE_NAME2] ...
+FILE_NAME: load, same as FILE_NAME without '+'.
-FILE_NAME: unload, same as --unload FILE_NAME.
Options (short, or long):
-u, --unload: unload the extra sfs files.
-c, --cli: commandline interface, without dialog.
-d, --debug: verbose output for debugging information.
-h, --help: print this help and exit.
-l, --list=FILE_LIST : read file names from the list file FILE_LIST.
-q, --quiet: skip the 1st confirmation dialog.
-v, --version: print version and exit.
- (without file name): read file names from standard input. Imply '--cli'.
Examples:
ls -1 DIR_NAME | sfs_load -
sfs_load - < FILE_LIST
sfs_load --list=FILE_LIST
Note that FILE_LIST contains each filename per a line.
Other options(sfs_load internal use):
-n, --no-afterwork: suspend fixmenus and etc. after (un)loading.
-a, --afterwork (without file name): only do suspended afterwork.
-s, --skip-fixmenus: skip fixmenus (but do startup scripts and etc.).
start: auto load at boot (called from /etc/initd.d/sfs_load)
stop: clean up at shutodpwn (called from /etc/initd.d/sfs_load)
Last edited by shinobar on Mon 21 May 2012, 02:45, edited 1 time in total.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
UPDATE: sfs_load-1.9.5
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
#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
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
sfs_load-1.9.6
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
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
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
Re: sfs_load-1.9.6
Tried this out today on libreoffice-3.60.sfs on full install ext4 partition using lucid-528-005shinobar wrote: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
Seemed to load ok - was able to bring up word processor, spreadsheet, etc.
Then I uninstalled. I have a question on the uninstall - Using Pfind I searched for libreoffice and found 401 files remaining after the uninstall.
They are files ending in .png, .svg, .desktop, etc - How do I get rid of these files?
uninstall
Have you ever installed the same or older version of libreoffice?majorfoo wrote:Tried this out today on libreoffice-3.60.sfs on full install ext4 partition using lucid-528-005
Seemed to load ok - was able to bring up word processor, spreadsheet, etc.
Then I uninstalled. I have a question on the uninstall - Using Pfind I searched for libreoffice and found 401 files remaining after the uninstall.
They are files ending in .png, .svg, .desktop, etc - How do I get rid of these files?
If so, you need to uninstall the previous install before loading new.
If you installed the older libreoffice manually, that is other than PET or SFS packages, you need to remove the files manually.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
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
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
Managing SFSs
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
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
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
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..
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..
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:
Then I did change the code at (above) line 1902 to:
As you can see (surely) this disables the "copy-GUI" and as a result it loads the sfs from CD/DVD without to copy it to any other location and no GUI is shown to be clicked away.
Any chance to introduce a command for that behavior of sfs_load (maybe --do-not-copy), so that it would change its behavior only if submitted this (or similar) command?
RSH
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:
Code: Select all
# 2012-11-20 RSH
#---------------
# Get Pupmode etc.
. /etc/rc.d/PUPSTATE
# Check if run from CD
DoNoCopy="false"
if [ "$PMEDIA" = "cd" ]; then
DoNoCopy="true"
elif [ "$PMEDIA" = "CD" ]; then
DoNoCopy="true"
elif [ "$PMEDIA" = "dvd" ]; then
DoNoCopy="true"
elif [ "$PMEDIA" = "DVD" ]; then
DoNoCopy="true"
fi
echo "PMEDIA="$PMEDIA
echo "DoNoCopy="$DoNoCopy
#---------------
Code: Select all
if [ "$DoNoCopy" = "true" ]; then
PART="NOCOPY"
else
choosepart $TOPART || finish
fi
Any chance to introduce a command for that behavior of sfs_load (maybe --do-not-copy), so that it would change its behavior only if submitted this (or similar) command?
RSH
[b][url=http://lazy-puppy.weebly.com]LazY Puppy[/url][/b]
[b][url=http://rshs-dna.weebly.com]RSH's DNA[/url][/b]
[url=http://murga-linux.com/puppy/viewtopic.php?t=91422][b]SARA B.[/b][/url]
[b][url=http://rshs-dna.weebly.com]RSH's DNA[/url][/b]
[url=http://murga-linux.com/puppy/viewtopic.php?t=91422][b]SARA B.[/b][/url]
I load complete distros
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)
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)
Spanish locale updated
- Attachments
-
- MoManager-es_AR-SFS_load.tar.gz
- (6.22 KiB) Downloaded 610 times
[url=http://murga-linux.com/puppy/viewtopic.php?t=76948]Puppy Linux en español[/url]
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/puppyli ... .9.6-2.pet
Many thanks to SFR
Package:
http://mirror.aarnet.edu.au/pub/puppyli ... .9.6-2.pet
Puppy Linux Blog - contact me for access
Tested on Quirky 5.4.91 (Kernel 3.8.) Eventually worked. After removing the old pet and installing the new pet reboot is required before testing or it will crash system.01micko wrote: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.
[b]Classic Opera 12.16 browser SFS package[/b] for Precise, Slacko, Racy, Wary, Lucid, etc available[url=http://terryphillips.org.uk/operasfs.htm]here[/url] :)
Is this a script that one can edit so it does not ask so many questions
it wants to move files and deal with save file and so on.
I need it to load the sfs and not make me go into dialogs all the time
I don't have a save file so all these questions are only annoying Sorry
Now I am using sfs-exec in Slacko despite it does not work properly
for slacko. Would be better to be able to use the built in sfs on fly
but a version that are less nosy all the time.
it wants to move files and deal with save file and so on.
I need it to load the sfs and not make me go into dialogs all the time
I don't have a save file so all these questions are only annoying Sorry
Now I am using sfs-exec in Slacko despite it does not work properly
for slacko. Would be better to be able to use the built in sfs on fly
but a version that are less nosy all the time.
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
nooby; Did you try sfs_load --help to get the CLI list for use without the GUI.?
shinobar; I just needed an SFS loader for the first time for AppPkg development.
It works great except for what seems to be a Puppy messup of both the dirs. /lib/i386-linux-gnu and /usr/lib/i386-linux-gnu
They are links to the parent dir. and sfs_load can`t union dirs. on them. I doubt any union can be done on this type of setup.
Is there a work around fix for what appears to be a Puppy hack.?
( I`m guessing apps. must be modified to work, meaning they`ll only work in Puppy. )
# Suggestion for sfs_load: Why limit it to SFS files,?
# Please also make it load ext2, ext3, and ext4 image files as well.!
And of course add "Load RO" and "Load RW". ( Separate buttons is good. )
Have the buttons disabled when a SFS file is selected to be loaded.
If the image file`s mounted RW and unioned RO, then the normal Save file is the union`s only RW.
Then changes to the image file can be made through it`s mount point.
This will allow new app. package development ( SFS and AppPkg ) to be done quite easily.
.
shinobar; I just needed an SFS loader for the first time for AppPkg development.
It works great except for what seems to be a Puppy messup of both the dirs. /lib/i386-linux-gnu and /usr/lib/i386-linux-gnu
They are links to the parent dir. and sfs_load can`t union dirs. on them. I doubt any union can be done on this type of setup.
Is there a work around fix for what appears to be a Puppy hack.?
( I`m guessing apps. must be modified to work, meaning they`ll only work in Puppy. )
# Suggestion for sfs_load: Why limit it to SFS files,?
# Please also make it load ext2, ext3, and ext4 image files as well.!
And of course add "Load RO" and "Load RW". ( Separate buttons is good. )
Have the buttons disabled when a SFS file is selected to be loaded.
If the image file`s mounted RW and unioned RO, then the normal Save file is the union`s only RW.
Then changes to the image file can be made through it`s mount point.
This will allow new app. package development ( SFS and AppPkg ) to be done quite easily.
.
Last edited by sunburnt on Tue 12 Mar 2013, 23:35, edited 4 times in total.
Hi.
To use sfs_load from command line use option --cli. I do use this inside the RunScripts from LazY Puppy's SFS P.L.U.S. to get the SFS loaded without the GUI.
Full command I do use:
or to unload
This works in sfs_load 1.9.0 and above!
--cli = command line interface
--skip-fixmenus = NO fixmenus is executed after loading the SFS (LazY Puppy did need this, because the menu entries are already inside the OS)
--quiet = NO Messages/Warnigs are given
RSH
To use sfs_load from command line use option --cli. I do use this inside the RunScripts from LazY Puppy's SFS P.L.U.S. to get the SFS loaded without the GUI.
Full command I do use:
Code: Select all
sfs_load --cli --skip-fixmenus --quiet "$LP2BDL/$nogo_file"
Code: Select all
sfs_load --unload --cli --skip-fixmenus --quiet "$LP2BDL/$nogo_file"
--cli = command line interface
--skip-fixmenus = NO fixmenus is executed after loading the SFS (LazY Puppy did need this, because the menu entries are already inside the OS)
--quiet = NO Messages/Warnigs are given
RSH
[b][url=http://lazy-puppy.weebly.com]LazY Puppy Home
The new LazY Puppy Information Centre[/url][/b]
The new LazY Puppy Information Centre[/url][/b]