sfs_load-2.4 on-the-fly
Yapp almost works, haven't got xterm so == small problemRSH wrote: Hope this will work.
Thanks for pointing me in the right direction though, used info to create bash function
Code: Select all
function list_sfs() {
grep EXTRASFSLIST /etc/rc.d/BOOTCONFIG | awk -F "=" '{
gsub("\047","",$2)
gsub("\042","",$2)
print $2
}'
}
Can't see any hijacker.Darn Hijackers !
Move your forks to your own threads !
PLEASE !
Also no one has posted and/or published a fork of sfs_load in this thread here.
So, what's the problem?
A few images, that shows possibilities of an application, that's set 'on top' of sfs_load to use sfs_load in a much smarter way, than it is possible by sfs_load's own gui?
Yeah, I have examined sfs_load a lot and made some modifications for the use of 1.3.9 in LazY Puppy.sunburnt wrote:Hi RHS; Any thought to making sfs_load use ext2-3-4 and brtfs image files?
Just a thought to making it complete in it`s capability...
But, sorry, sunburnt.
Did you ever have a look into sfs_load?
I can do some modifications, but I'm not able to create really a fork of sfs_load or to extend it with new functions.
So, dear Karl, looks like still no fork is going on here...
[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]
Trouble with sfs_load of devx file in Precise 5.7.1.
I have the following error occur when I try to load the devx_precise_5.7.1.sfs file in a fresh frugal install of puppy_precise_5.7.1. The same error occurs on two different machines, and I re-downloaded the devx file both manually and via the desktop "install" icon. Both machines are i686 boxes. Other sfs files load OK (e,g, virtualbox-4.2.12-x86.sfs4.sfs)
Thanks
AEE
I can't find any other references to this error in the forums. Any ideas how to troubleshoot?fs_load: debug: Using /usr/bin/gtkdialog4.
sfs_load: Using /usr/bin/gtkdialog4.
sfs_load: debug: 'losetup -d' is disabled. for kernel-3.x
sfs_load: 'losetup -d' is disabled. for kernel-3.x
sfs_load: debug: SUPPORTSIG=green, SFSMODE=y, DESTPART=sda1, DESTDIR=/mnt/home;
sfs_load: SUPPORTSIG=green, SFSMODE=y, DESTPART=sda1, DESTDIR=/mnt/home;
sfs_load: debug: TFREE=842732
sfs_load: TFREE=842732
sfs_load: debug: RFREE=3174156
sfs_load: RFREE=3174156
sfs_load: debug: FILEISAT=home;
sfs_load: FILEISAT=home;
sfs_load: debug: Do you want to load 'devx_precise_5.7.1.sfs(filesize: 79MB)'?
sfs_load: Do you want to load 'devx_precise_5.7.1.sfs(filesize: 79MB)'?\n
sfs_load: debug: EXIT=OK
sfs_load: EXIT=OK
sfs_load: debug: Do not assosiate /mnt/home/puppy571/devx_precise_5.7.1.sfs to /dev/loop5 but /dev/loop2.
sfs_load: Do not assosiate /mnt/home/puppy571/devx_precise_5.7.1.sfs to /dev/loop5 but /dev/loop2.
mount: wrong fs type, bad option, bad superblock on /dev/loop2,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
sfs_load: debug: '/mnt/home/puppy571/devx_precise_5.7.1.sfs'() is mounted on '/initrd/pup_ro5'.
sfs_load: '/mnt/home/puppy571/devx_precise_5.7.1.sfs'() is mounted on '/initrd/pup_ro5'.
mount: mounting unionfs on / failed: Invalid argument
umount: can't umount /initrd/pup_ro5: Invalid argument
sfs_load: ERROR: fatal:Failed to append '/initrd/pup_ro5' to unionfs.
sfs_load: fatal:Failed to append '/initrd/pup_ro5' to unionfs.
sfs_load: debug: fatal:Failed to append '/initrd/pup_ro5' to unionfs.
sfs_load: fatal:Failed to append '/initrd/pup_ro5' to unionfs.\n
/usr/sbin/sfs_load: line 276: 19941 Terminated $GTKDIALOG -p DIALOG -c > /dev/null
sfs_load: debug: EXIT=OK
sfs_load: EXIT=OK
Thanks
AEE
Hi.
Just want to make a new request for an option to disable copy function of sfs_load and instead to let sfs_load load SFS Modules from the SFS Modules location.
RSH
Just want to make a new request for an option to disable copy function of sfs_load and instead to let sfs_load load SFS Modules from the SFS Modules location.
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]
sfs_load-2.0
Download: http://shino.pos.to/linux/puppy/
Most recent: sfs_load-2.0-2.pet (2014-01-22)
#18 Dec 2013 v2.0: '--info' shows installed sfs list, fix was always copy in cli(thanks to R-S-H), fix launcher was missing some desktop application name, fix menu icons for excess sfs
#v2.0: BOOTCONFIG.save for treating excess sfs, no wide search by default, refresh default applications, fix zdrv was double mounted
sfs_load-2.0 is built in the Precise-471JP, Japanese edition
http://www.murga-linux.com/puppy/viewtopic.php?t=91463
Most recent: sfs_load-2.0-2.pet (2014-01-22)
#18 Dec 2013 v2.0: '--info' shows installed sfs list, fix was always copy in cli(thanks to R-S-H), fix launcher was missing some desktop application name, fix menu icons for excess sfs
#v2.0: BOOTCONFIG.save for treating excess sfs, no wide search by default, refresh default applications, fix zdrv was double mounted
sfs_load-2.0 is built in the Precise-471JP, Japanese edition
http://www.murga-linux.com/puppy/viewtopic.php?t=91463
Last edited by shinobar on Wed 22 Jan 2014, 15:06, edited 1 time in total.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
Re: sfs_load-2.0
Thank you very much!!!shinobar wrote:Download: http://shino.pos.to/linux/puppy/
Most recent: sfs_load-2.0-2.pet (2014-01-22)
#18 Dec 2013 v2.0: '--info' shows installed sfs list, fix was always copy in cli(thanks to R-S-H), fix launcher was missing some desktop application name, fix menu icons for excess sfs
#v2.0: BOOTCONFIG.save for treating excess sfs, no wide search by default, refresh default applications, fix zdrv was double mounted
sfs_load-2.0 is built in the Precise-471JP, Japanese edition
http://www.murga-linux.com/puppy/viewtopic.php?t=91463
Downloaded and done some testings. I found I would still need to do some modifications for the way I'm using it.
But this reduces my effort to modify it a lot!!!
In fact I do need to insert just two parts to get it working for my purposes as it is wanted. First is:
Code: Select all
# Get redirected boot directory
if [ -f /tmp/redirected_lp2bdl ]; then
read TMPPSUBDIR < /tmp/redirected_lp2bdl
NEWPSUBDIR="`basename $TMPPSUBDIR`"
fi
Code: Select all
if [ "$NEWPSUBDIR" != "" ]; then
PSUBDIR="$NEWPSUBDIR"
fi
All testings are going well. I'm going to install this version now permanently (doing a new remaster).
Again: Thank you very much!!!
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]
Hi.
I have to post an issue in sfs_load 2.0.2 which I did experience already in version 1.9.9.
If having a SFS loaded and removing some files (I did try to remove some files from /usr/share/applications and also from /usr/local/bin), those removed files re-appear in the running OS when unloading the loaded SFS files.
I did try this in several Puppies with several files - same results.
Though, it seems not to happen with files that are only changed (changed its content e.g.).
RSH
I have to post an issue in sfs_load 2.0.2 which I did experience already in version 1.9.9.
If having a SFS loaded and removing some files (I did try to remove some files from /usr/share/applications and also from /usr/local/bin), those removed files re-appear in the running OS when unloading the loaded SFS files.
I did try this in several Puppies with several files - same results.
Though, it seems not to happen with files that are only changed (changed its content e.g.).
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]
Well thought I should double check and my crappy little sfs loader/unloader does not do this. Indeed there is a whiteout file left in the pup_rw layer which means the deleted items remain deleted even if the sfs is unloaded and then reloaded later on or after a reboot....sorry if this is what is supposed to happen. Oh yes the same applies to my sfs save as I did not do things the way snapmerge/multisession handles whiteouts either. In the case of my sfs loader there is NO whiteout handling as aufs does it so why would I need to?If having a SFS loaded and removing some files (I did try to remove some files from /usr/share/applications and also from /usr/local/bin), those removed files re-appear in the running OS when unloading the loaded SFS files.
Perhaps disinguishing between the way aufs works and the way puppy handles its layered filesystem might actually help to solve such issues.
mike
ps only having fun..ignore this post as usual
Hi.
I have found another annoying thing and am not sure if this is a bug or a feature?
When I'm creating/building SFS Modules they usually do appear in /root and also usually I do try to load it from /root for a first test - before copying it to my huge SFS repository.
In sfs_load 2.0.2 the SFS Module is removed from /root, after unloading it.
Any hints/clues?
Would you please have a look also here
Thanks,
RSH
I have found another annoying thing and am not sure if this is a bug or a feature?
When I'm creating/building SFS Modules they usually do appear in /root and also usually I do try to load it from /root for a first test - before copying it to my huge SFS repository.
In sfs_load 2.0.2 the SFS Module is removed from /root, after unloading it.
Any hints/clues?
Would you please have a look also here
Thanks,
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]
Ok, I see.Hmm RSH that does mimic slax behaviour to avoid loading while in the unionfs.
As I said earlier, I do not know Slax and this behavior of sfs_load was totally new to me. I just was afraid to have done something that I would never ever find again and therefore could not fix it.
So, mimic slax behaviour should make me happy?
Thanks for the Info.
[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 encountered the same behaviour and managed to determine the exact circumstances.RSH wrote:If having a SFS loaded and removing some files (I did try to remove some files from /usr/share/applications and also from /usr/local/bin), those removed files re-appear in the running OS when unloading the loaded SFS files.
Steps to reproduce:
0. Slacko-5.7.0, fresh savefile, PUPMODE=13, SAVEINTERVAL=0
1. Create a file, e.g.: /root/testfile
2. Save session
3. Delete the file
4. Load & Unload an SFS file
5. testfile reappears (corresponding whiteout from pup_rw gets deleted)
I see that if SAVEINTERVAL != 0 then sfs_load "manually" removes files from pup_ro1 pointed by whiteouts in pup_rw, hence they won't reappear in this case.
Files are reappearing when the following line gets executed:
Code: Select all
busybox mount -t aufs -o remount,del:$MNTPNT unionfs /
___________
Another issue - there is:
However, I re-enabled it some time ago. Don't remember exactly why; I think in some cases loop devices weren't properly disassociated without this (or something like that).#v1.9.4, v1.9.6-2: 'losetup -d' is disabled for kernel-3.x
Anyway, 'losetup -d' has never done any harm here in Slacko-5.7.0 (k3.10.32) and from what I remember, also in Slacko-5.6 (k3.4.something).
So, perhaps only 3.2.x series is affected and it's time to re-evaluate this precaution?
Greetings!
[color=red][size=75][O]bdurate [R]ules [D]estroy [E]nthusiastic [R]ebels => [C]reative [H]umans [A]lways [O]pen [S]ource[/size][/color]
[b][color=green]Omnia mea mecum porto.[/color][/b]
[b][color=green]Omnia mea mecum porto.[/color][/b]