Save-pup-lock
SFR,
Thanks for all that testing.
My tests are on a usb thumb drive formatted as ext3 with an ext3 savefile booted from Racy5.3.
Since, this does not happen with an ext2 formatted savefile, I'm wondering if there is some "timing" issue due to journalllng in your case.
Since this only happens after the second boot, and only after snapmergepuppy has been run once, suggests that snapmergepuppy might be involved. However, it would seem in that case that it would affect both filesystem formats.
So, I'm at a loss to suggest a solution. Perhaps ext2 is ok since the idea is to keep save activity under direct control.
Cheers,
s
(Found this somewhat related reference to ext3 remounts
http://serverfault.com/questions/124051 ... y-from-a-d )
Thanks for all that testing.
My tests are on a usb thumb drive formatted as ext3 with an ext3 savefile booted from Racy5.3.
Since, this does not happen with an ext2 formatted savefile, I'm wondering if there is some "timing" issue due to journalllng in your case.
Since this only happens after the second boot, and only after snapmergepuppy has been run once, suggests that snapmergepuppy might be involved. However, it would seem in that case that it would affect both filesystem formats.
So, I'm at a loss to suggest a solution. Perhaps ext2 is ok since the idea is to keep save activity under direct control.
Cheers,
s
(Found this somewhat related reference to ext3 remounts
http://serverfault.com/questions/124051 ... y-from-a-d )
pupSaveconfig V.2.2.2 is perfect
pupSaveconfig V.2.2.2 is perfect
It does like if it was the first run. you can save or not the things you have done during the session. Each time. very good, very well, très bon.
It does like if it was the first run. you can save or not the things you have done during the session. Each time. very good, very well, très bon.
@Pelo:
I used to use PupSaveconfig 2.2.2 & 2.2.4, until I noticed that it behaves the same way as the first version of Save-pup-lock (qafe0331's posts on previous page) - if I install some .pet(s) and choose not to save session, only /root is not being saved.
But I've checked PupSaveconfig + latest Petget a while ago...and it seems to work ok in this case.
@Seaside:
I downloaded Racy 5.3 and fell into the same problem (in Lucid too), so there's a big chance that this is "it's just me" type of issue. But like I said - it's no big deal.
The good news is that I've done quick test in Slacko:
Upgraded Petget & installed Save-pup-lock (first version!).
Pets are being installed properly and if I don't save the session, files belonging to installed .pets don't remain in the savefile.
Looks like Petget is crucial factor in both cases and the easiest way to use Save-pup-lock or PupSaveconfig happily is to upgrade Petget before.
I need to do more tests...
Thanks guys & Greetings!
I used to use PupSaveconfig 2.2.2 & 2.2.4, until I noticed that it behaves the same way as the first version of Save-pup-lock (qafe0331's posts on previous page) - if I install some .pet(s) and choose not to save session, only /root is not being saved.
But I've checked PupSaveconfig + latest Petget a while ago...and it seems to work ok in this case.
@Seaside:
I downloaded Racy 5.3 and fell into the same problem (in Lucid too), so there's a big chance that this is "it's just me" type of issue. But like I said - it's no big deal.
The good news is that I've done quick test in Slacko:
Upgraded Petget & installed Save-pup-lock (first version!).
Pets are being installed properly and if I don't save the session, files belonging to installed .pets don't remain in the savefile.
Looks like Petget is crucial factor in both cases and the easiest way to use Save-pup-lock or PupSaveconfig happily is to upgrade Petget before.
I need to do more tests...
Thanks guys & 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]
SFR,
Apparently snapmergepuppy sends a flag file after it's first use. Perhaps this causes the problem. Try this script in a terminal and see what happens
Regards,
s
Apparently snapmergepuppy sends a flag file after it's first use. Perhaps this causes the problem. Try this script in a terminal and see what happens
Code: Select all
#/bin/sh
#test snapmergepuppy affect
for i in {1..4}; do
mount -o remount,ro /dev/loop1
mount -o remount,rw /dev/loop1
sync && snapmergepuppy
[ -e /initrd/pup_ro1/tmp/flagnextpassthru] && rm -f /initrd/pup_ro1/tmp/flagnextpassthru
mount -o remount,ro /dev/loop1
mount -o remount,rw /dev/loop1
done
s
Hey Seaside
Unfortunately, the same situation: at the first boot - ok, next boots - fail...
I even commented the appropriate line in snapmergepuppy:
before saving for the first time - nothing changed...
Something tells me that the problem might be initrd (or wherever it is)..?
You know, the line:
Maybe thanks to "that" everything works at the first reboot, and at the next - it doesn't..?
But it's just an unjustified guess...
Again, I can live with that, since I know workarounds.
I think there's no need to waste your time on the (apparently only mine) problem...unless someone else will report similar issue.
Thanks a lot for trying to help me out &
Greetings!
Unfortunately, the same situation: at the first boot - ok, next boots - fail...
I even commented the appropriate line in snapmergepuppy:
Code: Select all
# [ -e /tmp/flagnextpassthru ] && NEXTPASSTHRU="yes"
Something tells me that the problem might be initrd (or wherever it is)..?
You know, the line:
right after the first reboot after creating savefile.Updating... layered-filesystem next boot will be faster!
Maybe thanks to "that" everything works at the first reboot, and at the next - it doesn't..?
But it's just an unjustified guess...
Again, I can live with that, since I know workarounds.
I think there's no need to waste your time on the (apparently only mine) problem...unless someone else will report similar issue.
Thanks a lot for trying to help me out &
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]
I am sorry to jump in without knowing how. I was reading this discussion about Save-pup-lock. This seemed like exactly what I need. I downloaded Save-pup-Lock 2 and installed it. I did not know what I was doing but finally got the icon title to change. Then I discovered that I had both Icons and separated them. The Save-pup-lock Icon provides the menu as it is supposed to do.
The problem I have is that when I power off or reboot, the file is still saved.
I do not understand much of what is talked about in this discussion, especially about the required pupmode.
I am working with Puppy 5.28 installed on a USB stick. The computer has no hard drive.
Thanks for any help!
The problem I have is that when I power off or reboot, the file is still saved.
I do not understand much of what is talked about in this discussion, especially about the required pupmode.
I am working with Puppy 5.28 installed on a USB stick. The computer has no hard drive.
Thanks for any help!
comcoco,comcoco wrote:.
The problem I have is that when I power off or reboot, the file is still saved.
I do not understand much of what is talked about in this discussion, especially about the required pupmode.
I am working with Puppy 5.28 installed on a USB stick. The computer has no hard drive.
Thanks for any help!
Sorry that you are having some difficulties.
I assume you are booting directly from the usb thumbdrive and not a cd. Would you mind opening a terminal, type "mount", and then post the output here.
Thanks,
s
(You call tell which pupmode you are running in by typing in a terminal "cat /etc/rc.d/PUPSTATE" )
seaside,
This is what I get when I type "mount" from the terminal:
sh-4.1# mount
rootfs on / type rootfs (rw,relatime)
/dev/sda1 on /initrd/mnt/dev_save type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,quiet,errors=remount-ro)
/dev/loop1 on /initrd/pup_ro1 type ext2 (ro,noatime,errors=continue)
tmpfs on /initrd/pup_rw type tmpfs (rw,relatime)
tmpfs on /initrd/mnt/tmpfs type tmpfs (rw,relatime,size=130608k)
/dev/loop0 on /initrd/pup_ro2 type squashfs (ro,noatime)
unionfs on / type aufs (rw,relatime,si=f4b0de13)
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)
shmfs on /dev/shm type tmpfs (rw,relatime,size=746060k)
none on /proc/bus/usb type usbfs (rw,relatime)
/dev/sdb1 on /mnt/sdb1 type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,quiet,errors=remount-ro)
sh-4.1# ^C
sh-4.1#
Thanks for your help!
This is what I get when I type "mount" from the terminal:
sh-4.1# mount
rootfs on / type rootfs (rw,relatime)
/dev/sda1 on /initrd/mnt/dev_save type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,quiet,errors=remount-ro)
/dev/loop1 on /initrd/pup_ro1 type ext2 (ro,noatime,errors=continue)
tmpfs on /initrd/pup_rw type tmpfs (rw,relatime)
tmpfs on /initrd/mnt/tmpfs type tmpfs (rw,relatime,size=130608k)
/dev/loop0 on /initrd/pup_ro2 type squashfs (ro,noatime)
unionfs on / type aufs (rw,relatime,si=f4b0de13)
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)
shmfs on /dev/shm type tmpfs (rw,relatime,size=746060k)
none on /proc/bus/usb type usbfs (rw,relatime)
/dev/sdb1 on /mnt/sdb1 type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,quiet,errors=remount-ro)
sh-4.1# ^C
sh-4.1#
Thanks for your help!
Seaside,
Sorry I could not get the other command to work at first. It gives:
sh-4.1# cat /etc/rc.d/PUPSTATE
PUPMODE=13
PDEV1='sda1'
DEV1FS='vfat'
PUPSFS='sda1,vfat,/lupu_528.sfs'
PUPSAVE='sda1,vfat,/lupusave-Puppy2_12_02.2fs'
PMEDIA='usbflash'
#ATADRIVES is all internal ide/pata/sata drives, excluding optical, excluding usb...
ATADRIVES=''
#ATAOPTICALDRIVES is list of non-usb optical drives...
ATAOPTICALDRIVES=''
#these directories are unionfs/aufs layers in /initrd...
SAVE_LAYER='/pup_ro1'
PUP_LAYER='/pup_ro2'
#The partition that has the lupusave 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'
#Partition no. override on boot drive to which session is (or will be) saved...
PSAVEMARK=''
sh-4.1#
Thanks, again!
Sorry I could not get the other command to work at first. It gives:
sh-4.1# cat /etc/rc.d/PUPSTATE
PUPMODE=13
PDEV1='sda1'
DEV1FS='vfat'
PUPSFS='sda1,vfat,/lupu_528.sfs'
PUPSAVE='sda1,vfat,/lupusave-Puppy2_12_02.2fs'
PMEDIA='usbflash'
#ATADRIVES is all internal ide/pata/sata drives, excluding optical, excluding usb...
ATADRIVES=''
#ATAOPTICALDRIVES is list of non-usb optical drives...
ATAOPTICALDRIVES=''
#these directories are unionfs/aufs layers in /initrd...
SAVE_LAYER='/pup_ro1'
PUP_LAYER='/pup_ro2'
#The partition that has the lupusave 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'
#Partition no. override on boot drive to which session is (or will be) saved...
PSAVEMARK=''
sh-4.1#
Thanks, again!
comcoco,
I am quite puzzled. These two items-
If you make up a test file and save it in the home puppy directory, does this file survive after a shutdown?
Cheers,
s
(Incidentally, upon shutdowns there is a message that states" saving to pup-save....." but it does not actually save)
I am quite puzzled. These two items-
andSAVE_LAYER='/pup_ro1'
tell me that your pup save file is "pup_ro1" and is mounted as a "Read Only" filesystem./dev/loop1 on /initrd/pup_ro1 type ext2 (ro,noatime,errors=continue)
If you make up a test file and save it in the home puppy directory, does this file survive after a shutdown?
Cheers,
s
(Incidentally, upon shutdowns there is a message that states" saving to pup-save....." but it does not actually save)
seaside,
Please bear with me. I do not know how to find the items you just requested.
My pup save file is:
/lupusave-Puppy2-12-02.2fs (sda1) as stated when Puppy is booting. I can not find this using ROX.
Also using ROX I can not find "pup_ro1".
I concluded that I am saving my pupsave file when I power down or reboot because when I move items around on the desktop, they come back after booting in the new place.
I told you I need a lot of help.
Please bear with me. I do not know how to find the items you just requested.
My pup save file is:
/lupusave-Puppy2-12-02.2fs (sda1) as stated when Puppy is booting. I can not find this using ROX.
Also using ROX I can not find "pup_ro1".
I concluded that I am saving my pupsave file when I power down or reboot because when I move items around on the desktop, they come back after booting in the new place.
I told you I need a lot of help.
comcoco,comcoco wrote:seaside,
Please bear with me. I do not know how to find the items you just requested......
Also using ROX I can not find "pup_ro1"........
No need to find any of those items. Use a text editor (geany) and save a file named "testsurviveboot" (can be blank).
Then do a reboot and see if this file is now still there.
Cheers,
s
seaside,
Thanks for your patience in working with me!
I generated a test file, saved to the home folder, rebooted using the Menu>Shutdown>Reboot.
The test file survived the reboot. This shows that the Save-pup-lock is not working, I think. I guess I did not know that the save covered the whole file system, not just the lupusave.2fs file.
Do you have a suggestion for me to try which I can do?
Thanks for your patience in working with me!
I generated a test file, saved to the home folder, rebooted using the Menu>Shutdown>Reboot.
The test file survived the reboot. This shows that the Save-pup-lock is not working, I think. I guess I did not know that the save covered the whole file system, not just the lupusave.2fs file.
Do you have a suggestion for me to try which I can do?
comcoco,comcoco wrote:seaside,
Thanks for your patience in working with me!
I generated a test file, saved to the home folder, rebooted using the Menu>Shutdown>Reboot.
The test file survived the reboot. This shows that the Save-pup-lock is not working, I think. I guess I did not know that the save covered the whole file system, not just the lupusave.2fs file.
Do you have a suggestion for me to try which I can do?
That result is very odd. Since the pup save file appears from your test to be locked as "Read Only", I can't explain how anything would be saved.
Perhaps you might use Pupsaveconfig found here-
http://murga-linux.com/puppy/viewtopic. ... 23&t=60678
It was made for the latest puppies and might work better for your pup version.
Cheers,
s