(old)Puppy Linux Discussion Forum

Posted: **Sat 05 Oct 2013, 22:14**

Looks like the devx is in the 571 directory?
Try moving it outside (/mnt/home/) and see if that helps.

Posted: **Sat 05 Oct 2013, 23:34**

That worked! So what's the trick to being able to have all the files for the install self-contained in a subdirectory?

Posted: **Fri 08 Nov 2013, 05:08**

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

Posted: **Wed 22 Jan 2014, 05:46**

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

Posted: **Wed 22 Jan 2014, 09:45**

So this is where you are all hiding...
mike

Posted: **Wed 22 Jan 2014, 11:44**

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

Thank you very much!!!

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

inserted at line 61 and second is:

Code: Select all

if [ "$NEWPSUBDIR" != "" ]; then
	PSUBDIR="$NEWPSUBDIR"
fi

inserted at line 2229.

All testings are going well. I'm going to install this version now permanently (doing a new remaster).

Again: Thank you very much!!!

RSH

Posted: **Wed 29 Jan 2014, 16:02**

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

Posted: **Wed 29 Jan 2014, 16:28**

infamous .wh out bug that never seems to get solved rediscovered by RSH.

Posted: **Wed 29 Jan 2014, 17:58**

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.

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?

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

Posted: **Sat 01 Feb 2014, 13:13**

fixed it yet?

Posted: **Mon 03 Mar 2014, 21:28**

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

Posted: **Mon 03 Mar 2014, 23:05**

Hmm RSH that does mimic slax behaviour to avoid loading while in the unionfs.

In my approach I only copied to tmpfs and load the copy leaving the original alone... and if there was not enough ram to do so the load fails. I was not keen on disappearing sfs either.

mike

Posted: **Tue 04 Mar 2014, 02:47**

Hmm RSH that does mimic slax behaviour to avoid loading while in the unionfs.

Ok, I see.

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.

Posted: **Tue 04 Mar 2014, 09:29**

So, mimic slax behaviour should make me happy?

In my approach I only copied to tmpfs and load the copy leaving the original alone... and if there was not enough ram to do so the load fails. I was not keen on disappearing sfs either.

mike

Posted: **Wed 14 May 2014, 15:01**

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.

I encountered the same behaviour and managed to determine the exact circumstances.
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 /

I'm not AUFS expert and don't really know how to fix it. I tried to do 'reval': busybox mount -t aufs -o remount,udba=reval unionfs / before and/or after the offending line, but it didn't change anything, unfortunately...
___________

Another issue - there is:

#v1.9.4, v1.9.6-2: 'losetup -d' is disabled for kernel-3.x

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).
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!

Posted: **Thu 05 Jun 2014, 04:19**

Since sfs_load uses #!/bin/ash sub scripts in /tmp :

Busybox find does not recognize the -mount option,

which is already deprecated according to man find .

-xdev is the other name for the -mount option .

# sfs_load
/usr/sbin/sfs_load: line 794: 4660 Terminated $GTKDIALOG -p DIALOG -c > /dev/null
find: unrecognized: -mount
BusyBox v1.23.0.git (2014-06-03 23:37:26 GMT-8) multi-call binary.

Usage: find [-HL] [PATH]... [OPTIONS] [ACTIONS]

Search for files and perform actions on them.
First failed action stops processing of current file.
Defaults: PATH is current directory, action is '-print'

-L,-follow Follow symlinks
-H ...on command line only
-xdev Don't descend directories on other filesystems

Posted: **Thu 12 Jun 2014, 12:49**

Please test sfs_load-2.0.8.pet
http://shino.pos.to/linux/puppy/

#09 Jun 2014 v2.0.8: ydrv, save-to-directory(gyro), DISSOSIATE option to be set by hardcode (thanks to R-S-H), remove find -mount option(Karl Godt)

Note: DISSOSIATE option is not automatically determined by the kernel version. You can edit the script to choose this option.

Posted: **Mon 16 Jun 2014, 16:54**

Hey Shinobar, thanks for the new version.

I think I found a workaround for disappearance of .wh files from pup_rw, when PUPMODE=3/13 & RAMSAVEINTERVAL=0.

The idea is to find and tar all .wh files from pup_rw:

Code: Select all

find "/initrd/pup_rw" -name ".wh.*" -not -name ".wh..wh.*" -exec tar -Ppuf /tmp/wh_temp.tar {} \;

and then, when aufs gets remounted, recover them:

Code: Select all

tar -Ppxf /tmp/wh_temp.tar

Initial tests are fine, so far, but I didn't examine sfs_load's code thoroughly enough, so perhaps there are some caveats of such an approach I'm not aware of; what do you think?

Here's the diff against 2.0.8:

Code: Select all

--- old/sfs_load	2014-06-09 16:37:50.000000000 +0200
+++ new/sfs_load	2014-06-16 18:38:56.823284373 +0200
@@ -1176,6 +1176,10 @@
         # merge whiteout first
         $MYTMPDIR/petget $PREM
         return
+      else	# SFR: save all .wh files
+        TMP_WH="${MYTMPDIR}/wh_temp.tar"
+        rm -f "$TMP_WH"
+        find "/initrd/pup_rw" -name ".wh.*" -not -name ".wh..wh.*" -exec tar -Ppuf "$TMP_WH" {} \;
       fi
       ;;
   esac
@@ -1386,6 +1390,11 @@
   if [ "$AUFS" != "" ];then
     busybox mount -t aufs -o remount,append:$MNTPNT=ro unionfs /
     STATUS=$?
+	# SFR: recover .wh files
+	if [ -f "$TMP_WH" ] && [ $PUPMODE -eq 13 -o $PUPMODE -eq 3 ] && [ $RAMSAVEINTERVAL -eq 0 ]; then
+	  tar -Ppxf "$TMP_WH"
+	  rm -f "$TMP_WH"
+    fi
   else
     # 28 Oct 2011: unionfs support
     mount -t unionfs -o remount,add=:$MNTPNT=ro unionfs /
@@ -1604,6 +1613,11 @@
           debug "busybox mount -t aufs -o remount,del:$MNTPNT unionfs /"
           busybox mount -t aufs -o remount,del:$MNTPNT unionfs /
           STATUS=$?
+		  # SFR: recover .wh files
+		  if [ -f "$TMP_WH" ] && [ $PUPMODE -eq 13 -o $PUPMODE -eq 3 ] && [ $RAMSAVEINTERVAL -eq 0 ]; then
+		    tar -Ppxf "$TMP_WH"
+		    rm -f "$TMP_WH"
+		  fi
         else
           debug "mount -t unionfs -o remount,del=$MNTPNT unionfs /"
           mount -t unionfs -o remount,del=$MNTPNT unionfs /

(code could be better, but it's only a prototype, for testing purposes)

Btw, why PUPMODE=7 isn't also included? Only:

Code: Select all

3|13)	# ata/usbflash

Greetings!

Posted: **Mon 16 Jun 2014, 17:30**

why would a sfs loader be touching pup_ro1... or is this more a snap merge issue. I get none of this happening with my sfs script but then again I dumped PUPMODE=13 years ago ..perhaps related but not sure how.

mike

Posted: **Tue 17 Jun 2014, 13:32**

SFR wrote:Btw, why PUPMODE=7 isn't also included? !

PUPMODE=7 is buggy. I have no energy to check it out on many versions of Puppy. It's a nightmare.

(old)Puppy Linux Discussion Forum

sfs_load-2.4 on-the-fly

sfs_load-2.0

Re: sfs_load-2.0

sfs_load-2.0.8

PUPMODE=7