(old)Puppy Linux Discussion Forum

Posted: **Tue 17 Jun 2014, 14:00**

It's a nightmare

That could be the understatement of the year... ... a bit like juggling eggs

mike

Posted: **Thu 19 Jun 2014, 20:22**

shinobar wrote: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.

Hi.

Thanks for the new version.

I have downloaded the new version, made my modifications and then somw testings. The

Ted Dog wrote:infamous .wh out bug that never seems to get solved rediscovered by RSH.

still seems to exist. Files removed from the file system do re-appear in the file system when loading/unloading a SFS.

shinobar wrote:DISSOSIATE option to be set by hardcode (thanks to R-S-H)
...
...
Note: DISSOSIATE option is not automatically determined by the kernel version. You can edit the script to choose this option.

Can you explain this a little more?

Currently, I don't understand this.

Would this solve the infamous .wh out bug?

Thanks

RSH

Posted: **Thu 19 Jun 2014, 22:42**

shinobar wrote:#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.

Sorry, it was SFR who suggested on the DISSOSIATE option.
The issue R-S-H proposed is still on my TO-DO list.

Posted: **Sun 29 Jun 2014, 08:21**

Pet Loaded. I thought that 'on the fly' was only a link to something external. Often, it's not true, files in the distro are erased when using SFS.
Abiword 3.0.0, is concerned but Suite goffice Japan too. (libspreadsheet erased).
Puppy runs 'on the fly' in my computer and keep Windows 7 sleeping.
RSH on the fly let traces when taking off (plane) ????

To understand on the fly I use "croquis"

Posted: **Wed 02 Jul 2014, 19:28**

Download: http://shino.pos.to/linux/puppy/
Testing: sfs_load-2.0.11.pet (2014-07-03)

#26 Jun 2014 v2.0.9: init script in initramfs may not handle extra sfs
#27 Jun 2014 v2.0.10: afterwork at boot
#3 Jul 2014 v2.0.11: fix save-to-directry(gyro), fix was ydrv on loadable list

Posted: **Sat 05 Jul 2014, 14:38**

@shinobar,
Just in case it gets missed in all the chatter in the slacko6 discussion, I hope this comment helps. http://murga-linux.com/puppy/viewtopic. ... &start=371
gyro[/code]

Posted: **Tue 08 Jul 2014, 11:39**

Download: http://shino.pos.to/linux/puppy/
Testing: sfs_load-2.0.12.pet
#8 Jul 2014 v2.0.12: no extra sfs but layers can be changed, rewrite cleanwhite, WIPEWHITEONINIT, PUPMODE7SUPPORT
FIX by SFR: http://www.murga-linux.com/puppy/viewto ... &start=419
/usr/sbin/sfs_load line 1195:

Code: Select all

$MYTMPDIR/cleanup /initrd/$SLAYER $PARAM

is to be

Code: Select all

$MYTMPDIR/cleanup /initrd$SLAYER $PARAM

Made for Slacko 6.0 beta(Slacko-5.9.3.6), but may work with any puppy.

NOTE on whiteout:
The whiteout need different treatment depends on the PUPMODE, typically next 3:
1) PUPMODE=5 or PUPMODE=12
2) PUPMODE=13 and RAMSAVEINTERVAL>0
3) PUPMODE=13 and RAMSAVEINTERVAL=0
Report with what PUPMODE you have tested.
As for the RAMSAVEINTERVAL=0 is a special case. We may have to clarify its specification...

Posted: **Tue 08 Jul 2014, 13:30**

shinobar wrote:cleanwhite, WIPEWHITEONINIT, PUPMODE7SUPPORT

PUPMODE=6 is supported with this sfs_load, almost same as PUPMODE=12.
PUPMODE=7 is not supported as the defaulet. The default action for PUPMODE=7 is install like a pet, same as PUPMODE=2.

Set the PUPMODE7SUPPORT 'true', editing /usr/sbin/sfs_load, if you want to test PUPMODE=7 support same as PUPMODE=13.

Posted: **Sat 12 Jul 2014, 13:03**

http://shino.pos.to/linux/puppy/
Testing: sfs_load-2.0.13.pet
#12 Jul 2014 v2.0.13: cleanwhite fix(SFR)

Posted: **Wed 16 Jul 2014, 04:31**

Download: http://shino.pos.to/linux/puppy/
Stable: sfs_load-2.1.pet (2014-07-16)

Posted: **Sun 27 Jul 2014, 03:11**

Download: http://shino.pos.to/linux/puppy/
Testing: sfs_load-2.1.8.pet (2014-07-27)
#v2.1.8: all extra sfs by sfs_load not by initramfs

I also suggest to update pman to make fixmenu fast:
pman-2.3.pet from the same place.

sfs_load-2.1.8 modifies /etc/rc.d/rc.sysinit by the pinstall.sh.

Code: Select all

--- rc.sysinit.org   2014-07-09 06:41:42.000000000 +0900
+++ rc.sysinit   2014-07-26 17:51:18.266657221 +0900
@@ -583,6 +583,8 @@
 
 status_func 0
 
+[ -d /initrd ] && [ -x /etc/init.d/sfs_load ] && /etc/init.d/sfs_load start
+
 ##############USER SELECTED MODULES##################
 echo "USER SELECTED MODULES"
 #the user can select extra modules to load in the BootManager..

Posted: **Sun 03 Aug 2014, 02:02**

Download: http://shino.pos.to/linux/puppy/
Testing: sfs_load-2.1.9.pet (2014-08-03)
#v2.1.9: fix loop device conflict with irregular initramfs

Posted: **Sun 10 Aug 2014, 06:43**

UPDATE:
Download: http://shino.pos.to/linux/puppy/
Most recebt: sfs_load-2.2.pet (2014-08-10)

#v2.1.8: all extra sfs by sfs_load not by initramfs
#v2.1.9: fix loop device conflict with irregular initramfs
#2014-08-10 v2.2: fix was removed all sfs after abnormal shutdown

Posted: **Sat 06 Sep 2014, 15:51**

Download: http://shino.pos.to/linux/puppy/
Most recent: sfs_load-2.3.pet (2014-09-06)
#2014-09-06 v2.3: fix again save-to-directry, avoid always mounted puppy sfs partition under PUPMODE=5

Posted: **Sun 07 Sep 2014, 11:54**

shinobar wrote:sfs_load-2.3.pet (2014-09-06)
#2014-09-06 v2.3: fix again save-to-directry, avoid always mounted puppy sfs partition under PUPMODE=5

Thank you shinobar !

Posted: **Sun 21 Dec 2014, 15:23**

hi shinobar,

tahrpup 6.0.1 ext4 partition
when trying to grab an url with sfs_load i'm getting this 'not enough space error'

Posted: **Sun 21 Dec 2014, 21:23**

666philb wrote:hi shinobar,

tahrpup 6.0.1 ext4 partition
when trying to grab an url with sfs_load i'm getting this 'not enough space error'

The problem is there are two instances of "Length:"

Code: Select all

Content-Length: 9678848 Length: 9678848 (9.2M) [application/vnd.spotfire.sfs]

Both are combined 9678848967884892

Edit line 988 in sfs_load and add -m 1 so only the first instance is read.

Code: Select all

 SIZEB_ONLINE=$(grep -m 1 'Length: ' "$myLOG"| cut -d':' -f2| tr -dc '0-9')

Better still maybe just read the "Content-Length:"

Code: Select all

 SIZEB_ONLINE=$(grep 'Content-Length: ' "$myLOG"| cut -d':' -f2| tr -dc '0-9')

Posted: **Mon 12 Jan 2015, 16:22**

only just noticed this

thanks Geoffrey!

Posted: **Wed 14 Jan 2015, 19:59**

My apologies that this is a bit off-topic, but thought this was the best thread to ask this question.....

Just trying to understand how sfs load behaves when the sfs contains an executable that already exists on the system.

Attached is a test sfs (with false .gz) that contains a single file - /usr/sbin/partview

The sfs loads without problem and afterwards there are 2 instances of partview - the original in /initrd/pup_ro2 and the one from the sfs in /initrd/pup_ro4

However, the one that is executed remains the original one in pup_ro2 whereas in my naive understanding I would expect the new version from the sfs to be seen/replace the original and be executed.

Is there a description of sfs loading anywhere that I can read so that I can understand what is going on better?

Thanks for any assistance.
Cheers
peebee

p.s. test environment is a pristine, manual, frugal install of Slacko5.7 with no savefile

p.p.s if more appropriate please send me a pm rather than hijack any further this thread.....

Posted: **Wed 14 Jan 2015, 20:19**

peebee...the puppy way is to add sfs under the main sfs ... and thats the result.

Mike

(old)Puppy Linux Discussion Forum

sfs_load-2.4 on-the-fly

Re: sfs_load-2.0.8

DISSOSIATE

On the fly means 'I don't touch' anything.

sfs_load-2.0.11

whiteout file problem

sfs_load-2.0.12

PUPMODE=6 and 7

sfs_load-2.0.13

sfs_load-2.1

sfs_load-2.1.8

sfs_load-2.1.9

sfs_load-2.2 released

sfs_load-2.3

Re: sfs_load-2.3

OT - understanding how sfs load works