Re: sfs_load-2.3.2 on pupmode=13
Posted: Fri 17 Apr 2015, 22:38
tnx mavrothal.
i am using sfs_load-2.3.2 on PUPMODE=13 and working with no problem so far.
i am using sfs_load-2.3.2 on PUPMODE=13 and working with no problem so far.
READ-ONLY Archive
https://oldforum.puppylinux.com/
I didArgolance wrote:Bonjour,
Please take a look around this thread...
sfs_load (2.3.2) seems to generate a (wrong) path starting with '/initrd/initrd/' (pupmode 5)
Cordialement.
Code: Select all
--- ./sfs_load_2.3 2014-09-06 10:44:34.000000000 +0200
+++ ./sfs_load_2.3.0 2015-07-07 16:06:31.000000000 +0200
@@ -51,9 +51,10 @@
#v2.1.9: fix loop device conflict with irregular initramfs
#2014-08-10 v2.2: fix was removed all sfs after abnormal shutdown
#2014-09-06 v2.3: fix again save-to-directry, avoid always mounted puppy sfs partition under PUPMODE=5
+#20150706 v2.3.0 by ASRI: Increase the size of main GUI # Add info "number of sfs mounted" # For the list of mounted sfs, use of a "table" (instead of "list") to sort the list alphabetically # Add button refresh
MYPATH=$0
MYNAME=$(basename "$0")
-VERSION=2.3
+VERSION=2.3.0
ORGOPT="$@"
#some options the puplet builder can choose
WIPEWHITEONINIT="true" # true/false
@@ -761,7 +762,18 @@
}
main_dialog() {
waitsplash $(gettext "Probing...")
- BOXHEIGHT=150
+ BOXHEIGHT1=300
+ BOXWIDTH=650
+ TEXTWIDTH=580
+ TEXTWIDTHCHARS=30
+ list="/tmp/sfs_load/loop_device_list"
+ cntsfsloaded=0
+ while read LINE
+ do
+ if [ "$LINE" != "" ]; then
+ cntsfsloaded=`expr $cntsfsloaded + 1`
+ fi
+ done < "$list"
LOADVISIBLE="enabled"
UNLOADVISIBLE="eabled"
if [ "$ACTION" = "unload" ]; then
@@ -793,8 +805,9 @@
UNLOADCOMBO=""
if [ "$ALREADY_SFS_LIST" != "" ]; then
UNLOADABLE="enabled"
- UNLOADCOMBO='<list tooltip-text="'$(gettext "Select the sfs file you want to unload.")'">
- <variable>UNLOADSFS</variable>'$(make_combo $ALREADY_SFS_LIST)'<visible>'$UNLOADVISIBLE'</visible></list>'
+ UNLOADCOMBO='<table tooltip-text="'$(gettext "Select the sfs file you want to unload.")'">
+ <label>'$(gettext 'Total of mounted SFS =')' '$cntsfsloaded'</label>
+ <variable>UNLOADSFS</variable>'$(make_combo $ALREADY_SFS_LIST)'<visible>'$UNLOADVISIBLE'</visible></table>'
[ "$QUEUELIST" ] && UNLOADCOMBO="$UNLOADCOMBO
"'<text><input>echo -en "'$(gettext "Some are not loaded but in the queue.")'"</input></text>'
else
@@ -804,10 +817,10 @@
DIALOG='<window title="'$LONG_TITLE'"><vbox>
<hbox>
<pixmap><input file>'$MYICON'</input></pixmap>
- <text width-chars="40"><input>echo -en "'$(gettext "You can load or unload extra SFS files on-the-fly.")'"</input></text>
+ <text width-chars="'$TEXTWIDTHCHARS'" width-request="'$TEXTWIDTH'"><input>echo -en "'$(gettext "You can load or unload extra SFS files on-the-fly.")'"</input></text>
</hbox>
- <hbox><frame '$(gettext "Load SFS")'>
- <vbox height-request="'$BOXHEIGHT'">
+ <hbox width-request="'$BOXWIDTH'"><frame '$(gettext "Load SFS")'>
+ <vbox height-request="'$BOXHEIGHT1'">
'"$LOADCOMBO
$WRONGTEXT"'
</vbox>
@@ -816,7 +829,7 @@
<action>EXIT:Load</action><visible>'$LOADVISIBLE'</visible></button>
</frame>
<frame '$(gettext "Unload SFS")'>
- <vbox height-request="'$BOXHEIGHT'">
+ <vbox height-request="'$BOXHEIGHT1'">
'$UNLOADCOMBO'
</vbox>
<button tooltip-text="'$(gettext "Which SFS do you want to unload?")' '$(gettext "Click here after you choose the extra sfs file.")'">
@@ -825,7 +838,8 @@
</frame></hbox>
<hbox>
- <button><label>'$(gettext 'Quit')'</label><input file stock="gtk-quit"></input><action>EXIT:Abort</action></button>
+ <button tooltip-text="'$(gettext "Refresh list of loaded sfs.")'"><input file stock="gtk-refresh"></input><action>sfs_load &</action><action>EXIT:Abort</action></button>
+ <button tooltip-text="'$(eval_gettext "Quit $TITLE v$VERSION.")'"><input file stock="gtk-quit"></input><action>EXIT:Abort</action></button>
</hbox>
</vbox></window>'
waitsplash --stop
I obviously do not intend to let user load two sfs files with the same name at the same time (for that strange purpose - probably useless - it is enough to name both differently), just replace the "old" one by the "new" one, which should be loaded at next startup. When SFS file is already present in /initrd/mnt/dev_save, SFS_load doesn't replace the old one with the new one, it just says that SFS file "was found" but keeps the old one that will be loaded at next startup anyway. If user chooses not to copy/move the SFS file to /initrd/mnt/dev_save, so there is no problem because the SFS file is directly loaded from the Downloads directory and the new one will be loaded at next startup. If it could be possible with moved/copied SFS files, using a dialog box prompting user if he wants or not do the overwriting, I think it would be convenient.musher0 wrote:cannot handle two files of the same name at the same time.
Code: Select all
more /initrd/tmp/EXTRASFSS
May be I am wrong, but you can delete a mounted SFS file and you will see that it will work properly during all the session because, as layer, it is not affected. The only difference is that it will not be mounted at next startup (with all the troubles this implies). Now, if you delete any file of the mounted SFS file with your file manager, Puppy will remember this and deleted files will not be present at next startup though the (new or old) SFS is duly mounted. Deletion affects the layer but not the SFS file itself (which is read-only anyway) and what could happen to the SFS file seems to be none of its business all long the session.This layer is active, so removing it while it is active would be like cutting the branch you are sitting on. The system will not let you do it.
Not sure: I really think replacing an SFS with another one is possible while it is currently mounted (it is what my little experiment tends to "prove": I did it manually with my devx file and even with my main ToOpPy sfs file during all my tests and at next startup, as far as I know, all works fine). So, I admit I would like to have (also) the opinion of another "leading light" of the forum and learn, if "feasible", how to modify the SFS_load script properly, using some added command lines inside and with all the required precautions!Autrement tu te retrouveras le bec à l'eau.
Je n'y suis pour rien: tout le mérite en revient à Puppy et son génial système de fichiers à couches!I find you courageous to change the devx file "in vivo". I know that I wouldn't risk it! Smile
If it works, bravo!
No answer: silly/untoward question?
Suggestion: the button "Install SFS" [of filemount] should be labeled "Un/Install SFS" because user can uninstall/unload any SFS file this way too,
This is done for several months.Argolance wrote:Suggestion: the button "Install SFS" [of filemount] should be labeled "Un/Install SFS" because user can uninstall/unload any SFS file this way too,
Yes, need to replace:Iguleder wrote:There's a bug in sfs_load - it should obtain the numeric kernel version using `uname -r | cut -f 1 -d \-`. Otherwise, it doesn't work at all with kernels that have an extra version string.
Hello, ASRI.ASRI éducation wrote:sfs_load-2.3.3
This version is based on:
- sfs_load-2.3 (by shinobar)
- sfs_load-2.3.0 (by ASRI)
- sfs_load-2.3.2 (by mavrothal)
- improve kernel detection KERNVER (by Iguleder)
Regards,