Remove Auto Pupsave with SaveFolder? -- Questions
Remove Auto Pupsave with SaveFolder? -- Questions
Hi All,
Perhaps this has been covered elsewhere? If so, could a link to the discussion be posted. The last post to the "Remove automatic pupsave for frugal installs" thread, http://murga-linux.com/puppy/viewtopic.php?t=81911, was on May 10, 2014, before the advent of the SaveFolder. I'm posting here because that thread is a "sticky" and posts to it may be overlooked.
If a discussion has already taken place, perhaps someone can post a link to it on that thread. If not, should this inquiry generate useful information, someone can later link this thread to it.
As I understand it --please correct me if I'm confused, my normal state-- a frugally installed Puppy operates as a "merged file system": merging in RAM, those applications written to the storage and loaded into RAM at bootup, those opened from storage media during operations, and those just existing in RAM. The default mode for running a frugal Puppy installed on a hard drive is PUPMODE=12. Running under Pupmode 12, a Puppy using a SaveFile will periodically save changes to settings, configurations and the files of newly installed applications to the SaveFile; that is write them to a storage media configured and identified as the Pup's SaveFile. Prior to such saving, those changes are only in RAM.
On the other hand, when a Pup is frugally installed to a USB-Key, its default mode is Pupmode 13. Running under Pupmode 13, a "Save" icon appears on the desktop [or elsewhere? for Pup without desktop icons?]. Unless the "Save" routine is executed, changes to settings, configurations, and applications "installed" are not written to the SaveFile; not even on shutdown. Running Puppy from a USB-key, Pupmode 13 has the obvious advantage of lessening "wear and tear" on such drive.
But Pupmode 13 can be used in a Frugal Install to a hard-drive. Basically, if you've screwed something up, or just wanted to try something without making it a permanent part of your system, Pupmode 13 enables you do do that. Simply don't execute a Save before shutting down.
Again, as I understand it --please correct me if I'm confused-- when a SaveFolder is employed changes are immediately, and automatically written to the SaveFolder if Pupmode 12 is in effect.
Can Pupmode 13 be used in conjunction with a SaveFolder?
If so, are the instructions provided by jpeps and/or sylvander on the above thread valid and sufficient? Or those provided by kleung21? http://www.murga-linux.com/puppy/viewtopic.php?t=13430.
If not, what additional actions must be taken.
Does it matter whether the Pup is using the original formulation for a SaveFolder or gyro's modifications which creates a Savefolder without 'mount -o bind'? http://www.murga-linux.com/puppy/viewtopic.php?t=95922
If Pupmode 13 can be used with SaveFolders, shouldn't it be the default mode? When a new Pet is installed, it will overwrite libs having the same name as those previously written to storage when an earlier application was installed. Wouldn't the later removal of such pet result in removal of all its libs, including the libs also needed by the earlier applications, thus breaking those applications?
Thanks,
mikesLr
Perhaps this has been covered elsewhere? If so, could a link to the discussion be posted. The last post to the "Remove automatic pupsave for frugal installs" thread, http://murga-linux.com/puppy/viewtopic.php?t=81911, was on May 10, 2014, before the advent of the SaveFolder. I'm posting here because that thread is a "sticky" and posts to it may be overlooked.
If a discussion has already taken place, perhaps someone can post a link to it on that thread. If not, should this inquiry generate useful information, someone can later link this thread to it.
As I understand it --please correct me if I'm confused, my normal state-- a frugally installed Puppy operates as a "merged file system": merging in RAM, those applications written to the storage and loaded into RAM at bootup, those opened from storage media during operations, and those just existing in RAM. The default mode for running a frugal Puppy installed on a hard drive is PUPMODE=12. Running under Pupmode 12, a Puppy using a SaveFile will periodically save changes to settings, configurations and the files of newly installed applications to the SaveFile; that is write them to a storage media configured and identified as the Pup's SaveFile. Prior to such saving, those changes are only in RAM.
On the other hand, when a Pup is frugally installed to a USB-Key, its default mode is Pupmode 13. Running under Pupmode 13, a "Save" icon appears on the desktop [or elsewhere? for Pup without desktop icons?]. Unless the "Save" routine is executed, changes to settings, configurations, and applications "installed" are not written to the SaveFile; not even on shutdown. Running Puppy from a USB-key, Pupmode 13 has the obvious advantage of lessening "wear and tear" on such drive.
But Pupmode 13 can be used in a Frugal Install to a hard-drive. Basically, if you've screwed something up, or just wanted to try something without making it a permanent part of your system, Pupmode 13 enables you do do that. Simply don't execute a Save before shutting down.
Again, as I understand it --please correct me if I'm confused-- when a SaveFolder is employed changes are immediately, and automatically written to the SaveFolder if Pupmode 12 is in effect.
Can Pupmode 13 be used in conjunction with a SaveFolder?
If so, are the instructions provided by jpeps and/or sylvander on the above thread valid and sufficient? Or those provided by kleung21? http://www.murga-linux.com/puppy/viewtopic.php?t=13430.
If not, what additional actions must be taken.
Does it matter whether the Pup is using the original formulation for a SaveFolder or gyro's modifications which creates a Savefolder without 'mount -o bind'? http://www.murga-linux.com/puppy/viewtopic.php?t=95922
If Pupmode 13 can be used with SaveFolders, shouldn't it be the default mode? When a new Pet is installed, it will overwrite libs having the same name as those previously written to storage when an earlier application was installed. Wouldn't the later removal of such pet result in removal of all its libs, including the libs also needed by the earlier applications, thus breaking those applications?
Thanks,
mikesLr
The newest versions of Puppy, like Tahrpup 6.0, have these options.
Set save interval to 0 to turn off auto save,
Select ask at shutdown so you will be asked if you want to save,
Set save interval to 0 to turn off auto save,
Select ask at shutdown so you will be asked if you want to save,
- Attachments
-
- capture7716.png
- (37.02 KiB) Downloaded 1831 times
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
@bigpup
1. That dialog says: "Currently, PUPMODE=13"...
a. What if the PUPMODE isn't 13?
b. Normally....
When I intend to hold my pupsave file on a partition on the internal HDD [somewhere other than a Flash Drive]...
I must edit the isolinux.cfg file within the ISO so that pmedia=ataflash.
This is done so that the pupsave [on the internal HDD] will be treated is if on a Flash Drive, and thence resulting in a "Save..." icon being displayed on the Puppy desktop. [PUPMODE=13]
Does the new method...
Or is there a way to make the new method...
Do the necessary without the need to edit the ISO file?
@mikeslr
My thoughts on some of your questions:
2.
a. "Unless the "Save" routine is executed, changes to settings, configurations, and applications "installed" are not written to the SaveFile"
That's only the case provided the "Save interval" has been reset to zero [0].
If not reset to zero, the Puppy will still auto-save during the session [at the "Save interval" set; default=30 (minutes)].
b. "...not even on shutdown"
No, this isn't true.
Even when running in PUPMODE=13, and even with the "Save interval" set to zero, the non-new Puppies would normally save at shutdown/reboot.
I normally make special changes, so I will be asked at shutdown/reboot whether I want "to save or not to save".
bigpup has displayed the new "Puppy Event Manager" dialog window, with its tick-box to configure that the user be asked at "shutdown" [and therefore reboot also], whether to "Save" or "no".
Regarding the SaveFolder:
c. "Can Pupmode 13 be used in conjunction with a SaveFolder?"
I too would like to know the answer to that question.
d. "If not, what additional actions must be taken."
Again...
I too would like to know the answer to that question.
1. That dialog says: "Currently, PUPMODE=13"...
a. What if the PUPMODE isn't 13?
b. Normally....
When I intend to hold my pupsave file on a partition on the internal HDD [somewhere other than a Flash Drive]...
I must edit the isolinux.cfg file within the ISO so that pmedia=ataflash.
This is done so that the pupsave [on the internal HDD] will be treated is if on a Flash Drive, and thence resulting in a "Save..." icon being displayed on the Puppy desktop. [PUPMODE=13]
Does the new method...
Or is there a way to make the new method...
Do the necessary without the need to edit the ISO file?
@mikeslr
My thoughts on some of your questions:
2.
a. "Unless the "Save" routine is executed, changes to settings, configurations, and applications "installed" are not written to the SaveFile"
That's only the case provided the "Save interval" has been reset to zero [0].
If not reset to zero, the Puppy will still auto-save during the session [at the "Save interval" set; default=30 (minutes)].
b. "...not even on shutdown"
No, this isn't true.
Even when running in PUPMODE=13, and even with the "Save interval" set to zero, the non-new Puppies would normally save at shutdown/reboot.
I normally make special changes, so I will be asked at shutdown/reboot whether I want "to save or not to save".
bigpup has displayed the new "Puppy Event Manager" dialog window, with its tick-box to configure that the user be asked at "shutdown" [and therefore reboot also], whether to "Save" or "no".
Regarding the SaveFolder:
c. "Can Pupmode 13 be used in conjunction with a SaveFolder?"
I too would like to know the answer to that question.
d. "If not, what additional actions must be taken."
Again...
I too would like to know the answer to that question.
Test successfull. I copied the files of my standard lightencripted tahr savefile in a tahrsave-t6 dir and changed "atahd" with "ataflash" in the grub4dos entry. I can boot my install with the savefolder in pupmode 13. Setting to 0 the save interval appears the box to choose to save or not to save at shutdown. Booting with pmedia=atahd the pupmode is 12.
Just for clarification
Pupmode=12 .. changes are instantaneous as they always have been...save folder behaves in exactly the same why...it just happens to occupy a real partition rather than an image file.
Any pupmode=13 saving does involve snapmerge(puppy) which does have some quirks... folder or save file again will not alter this... another point is having a save folder with mode 13 you would lose all that space for working in since you are limited to ram size minus system needs which sort of defeats the main point of the exercise with only the apparent gain of reducing flash writes IF on flash (which may only have been of value in the early days of flash memory)
Previously there was...or may still be saving to partition with ram layer... pupmode=7 ...perhaps this would be of interest to you.
mike
Pupmode=12 .. changes are instantaneous as they always have been...save folder behaves in exactly the same why...it just happens to occupy a real partition rather than an image file.
Any pupmode=13 saving does involve snapmerge(puppy) which does have some quirks... folder or save file again will not alter this... another point is having a save folder with mode 13 you would lose all that space for working in since you are limited to ram size minus system needs which sort of defeats the main point of the exercise with only the apparent gain of reducing flash writes IF on flash (which may only have been of value in the early days of flash memory)
Previously there was...or may still be saving to partition with ram layer... pupmode=7 ...perhaps this would be of interest to you.
mike
-
- Posts: 902
- Joined: Mon 22 Jun 2009, 01:36
- Location: Philadelphia, PA
lose space!!??
Mike, I just started using a save folder (rather than save file) in Super Lucid Puppy 2 (by rerwin), pupmode 13.mikeb wrote:having a save folder with mode 13 you would lose all that space for working in since you are limited to ram size minus system needs
I didn't realize there was a drawback, and I don't understand what you said; please excuse my dumbness.
Do you want to explain this alarming loss of working space so even I can understand?
Thank you,
Sheldon
Dell E6410: BusterPup, BionicPup64, Xenial, etc
Intel DQ35JOE, Dell Vostro 430
Dell Inspiron, Acer Aspire One, EeePC 1018P
Intel DQ35JOE, Dell Vostro 430
Dell Inspiron, Acer Aspire One, EeePC 1018P
Observations>removing auto Pupsave with SaveFolder
Thank you bigpup for the clear explanation, and sylvander for your further insights and corrections. Watchdog's above post reveals the need that a Pup's listing in Grub4dos menu.lst specify pmedia=ataflash for a Pup to run under Pupmode 13.
From my own exploration, I can only add the following:
1. With regard to a Pup's boot parameters, specifying that pmedia=ataflash sets Pupmode to 13, even if prior thereto its Pupmode was 12.
2. With Pupmode set to 13, a “Save
From my own exploration, I can only add the following:
1. With regard to a Pup's boot parameters, specifying that pmedia=ataflash sets Pupmode to 13, even if prior thereto its Pupmode was 12.
2. With Pupmode set to 13, a “Save
Re: Observations>removing auto Pupsave with SaveFolder
[quote="mikeslr"]
Changing the boot parameter between atahd and ataflash establishes whether a Pup will operate under Pupmode 12 or 13. With the exception of being able to switch from Pupmode 12 to Pupmode 13, all my experiments were run under Pupmode 13. Does anyone have experience under Pupmode 12 with setting Pup Event Manager, Save Interval to 0 (=Never), and clicking the radio box relating to “Ask at shutdown whether to save or not
Changing the boot parameter between atahd and ataflash establishes whether a Pup will operate under Pupmode 12 or 13. With the exception of being able to switch from Pupmode 12 to Pupmode 13, all my experiments were run under Pupmode 13. Does anyone have experience under Pupmode 12 with setting Pup Event Manager, Save Interval to 0 (=Never), and clicking the radio box relating to “Ask at shutdown whether to save or not
Sheldon.... the limitation is only applicable if you have forced mode 13 (or on usb stick?)
And mikesir... related reply.... well in your case you have a ton of ram so you are hardly limited I would say. If someone was doing this with say 512MB RAM and no swap then life starts to get cramped...it was just a general warning for anyone considering tinkering.
Yes the space is dependant on RAM (plus swap if present if included) but not the save file/folder. The periodic saves do not empty the RAM (though was claimed it would one day) so there is no caching. The idea was that the current session is all in ram and your persistent save is only used periodically and at the end if at all. df -h should show tmpfs space remaining.
Cannot think why 13 would be slower.... only difference is the creation and insertion of the tmpfs layer for pup_rw. Usually slowdowns are associated with reading and writing to usb sticks.
I use sfs saves so the tmpfs/ramdisk/pup_rw is saved as one sfs file and loaded back at boot...with 1GB+ this works nicely and is a much simpler option since you are effectively running in PUPMODE=5 and not saving is easy to implement. Perhaps one day someone will pick up that method...someone like debian has I believe now but don't quote me. It also avoids snapmerge altogether and still gives usb sticks an easy time like mode 13 plus you can remove the stick and keep running assuming sufficient ram.
The save folder is the method that Slax has always used...I added it to puppy 2.12 as a test and it worked nicely so have it on all my pups. It just gives the flexibility of a full install but the robustness and flexibility of a layered sfs based system. Never really considered the mode 13 since i find sfs save does the job...but an interesting option.
Yes it has to be a posix file system...ext2/3/4, reiserfs, xfs and so on...if supported..does also mean its easy to access from another system if you want files or need to fix.
Mike
And mikesir... related reply.... well in your case you have a ton of ram so you are hardly limited I would say. If someone was doing this with say 512MB RAM and no swap then life starts to get cramped...it was just a general warning for anyone considering tinkering.
Yes the space is dependant on RAM (plus swap if present if included) but not the save file/folder. The periodic saves do not empty the RAM (though was claimed it would one day) so there is no caching. The idea was that the current session is all in ram and your persistent save is only used periodically and at the end if at all. df -h should show tmpfs space remaining.
Cannot think why 13 would be slower.... only difference is the creation and insertion of the tmpfs layer for pup_rw. Usually slowdowns are associated with reading and writing to usb sticks.
I use sfs saves so the tmpfs/ramdisk/pup_rw is saved as one sfs file and loaded back at boot...with 1GB+ this works nicely and is a much simpler option since you are effectively running in PUPMODE=5 and not saving is easy to implement. Perhaps one day someone will pick up that method...someone like debian has I believe now but don't quote me. It also avoids snapmerge altogether and still gives usb sticks an easy time like mode 13 plus you can remove the stick and keep running assuming sufficient ram.
The save folder is the method that Slax has always used...I added it to puppy 2.12 as a test and it worked nicely so have it on all my pups. It just gives the flexibility of a full install but the robustness and flexibility of a layered sfs based system. Never really considered the mode 13 since i find sfs save does the job...but an interesting option.
Yes it has to be a posix file system...ext2/3/4, reiserfs, xfs and so on...if supported..does also mean its easy to access from another system if you want files or need to fix.
Mike