Puppy Linux Discussion Forum

[seaside]

Nooby,

Thanks, that was very helpful and one more request post what is in the file "/etc/rc.d/PUPSTATE".

Regards,
s
(I have no idea what the "fuse' refers to - I don't have that on any of my mounts )

[nooby]

Don't get alarmed me have fluppy13s

The s stands for sfs and flp is Jemimah's way to say Fluppy
here it is

PUPMODE=12
PDEV1='sda3'
DEV1FS='ntfs'
PUPSFS='sda3,ntfs,/fluppy13s/flp-013.sfs'
PUPSAVE='sda3,ntfs,/fluppy13s/flpsave.3fs'
PMEDIA='scsihd'
#v3.97: kernel with libata pata has both sata and pata drives in ATADRIVES...
ATADRIVES='sda '
#these directories are unionfs layers in /initrd...
SAVE_LAYER='/pup_rw'
PUP_LAYER='/pup_ro2'
#The partition that has the flpsave file is mounted here...
PUP_HOME='/mnt/dev_save'
#(in /initrd) ...note, /mnt/home is a link to it.
#this file has extra kernel drivers and firmware...
ZDRV=''
#complete set of modules in the initrd (moved to main f.s.)...
ZDRVINIT='no'
PSWAPFILE=''
PSAVEMARK=''
FASTPARTS='sda1|ntfs sda2|ntfs sda3|ntfs '

[seaside]

Nooby,

Thanks. Your information confirms that some additional coding is required to test where the pupsave file is mounted.

Unfortunately it's not always the same and depends on what kind of installation.

So basically, in your case, the pupsave file was not changed to a "read-only" system which is what was intended.

Thanks for testing this and I'll have to ponder how to change this.

Regards,
s

[nooby]

Very naive question from Nooby. Can I not tell it to be ro through CLI then or even use a gui and set permissions and such

[seaside]

[nooby]

#this file called from rc.sysinit
#you can edit this file
#When firewall is installed, will append lines to this file...
modprobe evdev

if [ -x /etc/rc.d/rc.firewall ]; then
/etc/rc.d/rc.firewall start
fi
mv /usr/sbin/snapmergepuppy /usr/sbin/snapmergepuppyHOLD
mount -o remount,ro /dev/loop1

Could it be that there is different loops to consider?

Sorry me so eager but not having knowledge for it.

Back when I tried out sfs-exec on Snowpup this did happen while preparing the preferences.

Did I tell you about my failure to change the background picture. It held a kind of copy of Snowpup's snowy Finland and I wanted a Cat or Dog there. And I changed the name of the file and renamed the cat file exactly same and placed it in right folder and so on. Nope the original file was copied over from the sfs or something. Could not be changed.

Could not something similar go on here. The pupsavefile we see is a copy and not the one one need to reach to change to ro and the one we see get copied unto the original that is rw when one reboot.

Just a wild totally long shot kind of hunch

[seaside]

Nooby,

Interesting. In a terminal if you type "mount -o remount,ro /dev/loop1 " and if successful then type "mount". does "/dev/loop1" show as "read-only" ( you can tell because it should look something like "(ro,noatime)" .

Regards,
s

[nooby]

# mount -o remount,ro /dev/loop1
mount: /initrd/pup_rw is busy
#
# mount
rootfs on / type rootfs (rw,relatime)
/dev/sda3 on /initrd/mnt/dev_save type fuseblk (rw,noatime,user_id=0,group_id=0,default_permissions,blksize=4096)
/dev/loop1 on /initrd/pup_rw type ext3 (rw,noatime,errors=continue,barrier=0,data=ordered)
tmpfs on /initrd/mnt/tmpfs type tmpfs (rw,relatime,size=149600k)
/dev/loop0 on /initrd/pup_ro2 type squashfs (ro,noatime)
unionfs on / type aufs (rw,relatime,si=43ca2dd3)
tmpfs on /tmp type tmpfs (rw,relatime,size=256212k)
tmpfs on /mnt/unrootfs type tmpfs (rw,relatime,size=4096k)
none on /proc type proc (rw,relatime)
none on /dev/pts type devpts (rw,relatime,gid=2,mode=620)
none on /sys type sysfs (rw,relatime)
none on /proc/bus/usb type usbfs (rw,relatime)
none on /dev/shm type tmpfs (rw,relatime)
#

[seaside]

[nooby]

Tomorrow or some other day I test it on Quirky 1.4 to see how that goes.

[seaside]

[nooby]

Seaside, if it is too demanding. Too many variables to keep track of then what about the experiment done by one of the active members.
Shutdown without save. I mean how does he do that. Should one not be able to use that one as a reboot without saving then?
I love the SFS.Exec thing that already works part from the little glitch I hit upon. One can warn to not do that and only go the recommended route.

So if one add his shutdown without save then that combination would do what one want. To be able to leave without saving if one have messed up and then it boots and all is okay. okay one can just get a backed up version instead and copy that one over the corrupted one.

[seaside]

[nooby]

There is a chance oops a risk that I've read that text too carelessly. 11PM soon so I look in here tomorrow as usual

[seaside]

Nooby,

I just realized from your post of the "PUPSTATE" file that you were running in "pupmode=12" mode which is a pupsave on a harddisk.

The SFS-Exec was originally conceived for "pupmode=5" and the SFS-Exec-Save-pup expanded that to "pupmode=13" which assumes a pupsave file on a usb thumb drive.

The layering filesystems are different and as far as I know, if you have a pupsave file on a harddisk, everything is written directly to the pupsave file. So this does not prevent saving when used this way.

Regards,
s