Seaside, Jasper and all of you here is how Sylvander learned from a site to edit a file so that Puppy treat the HDD as if it is a DVD and that way one get a choice to only save at reboot or to not save at all???
Read here http://www.murga-linux.com/puppy/viewto ... 458#497458
oops it only works if one have isolinux.config does grup4dos have such file within it as a kind of left over if they made grub legacy and grub4dos by reworking the older isolinux? Or can one learn from that one to find the same part in grub4dos and change that one in same fashion?
SFS-Exec
Jasper,Jasper wrote:Hi seaside,
Your code works, but
I get a yellow box with a message:
----
"Request to save the current session is queued. Please
wait and a message will pop up when the saving occurs."
----
A couple of times I have waited 10 minutes and more with no change to the message. However, if I move my cursor over the message it disappears immediately.
My regards
Perhaps (on Lupu) you might try the # sign (because I use the power-off button on my Tower - which I have to because the reboot which is not supposed to save - would otherwise save whatever code was used in the save file).
Thanks for trying out the code and affirming that it works. I tried it in pup431 and it works with the yellow message appearing only briefly - so I can't explain why yours remains, as the coding for "save2flash" in 525 is exactly the same as pup431.
If you eliminate the "exec poweroff" by placing a "#" in front , when you click on the "Save-pup" icon, the door is open to save to the pupsave file but no actual save will take place. At that point, a menu >poweroff or reboot will create a save - but then you've lost a specific save-now capability and a reset to a "don't save" posture.
Regards,
s
EDIT: Jasper are you certain that there was in fact an actual "save" made, because it just occurred to me that one reason the yellow message would not briefly go away is that the command to save was not picked up?
Last edited by seaside on Tue 19 Apr 2011, 22:11, edited 1 time in total.
Seaside what about this one then?
http://www.murga-linux.com/puppy/viewtopic.php?t=56077
title PupShutdown-1.6
He describe it to do this:
Maybe there is some trick there that can help your program to do what you like it to do?
http://www.murga-linux.com/puppy/viewtopic.php?t=56077
title PupShutdown-1.6
He describe it to do this:
Purpose and Base Features
PupShutdown permits menu-like access to sixteen common functions that one may find helpful when closing a Puppy session. Backup and task manager selections in the main menu have multi-program support to provide flexibility in managing the shutdown process. If the panel application selector does not have your program, you can add it manually. In addition to the configurable menu options, the appearance of the graphic interface can be quickly changed to complement a personal preference or match a Puppy theme. PupShutdown integrates seamlessly with PupControl Panel and PupApps Launcher.
Caveats
1 - PupShutdown typically requires Puppy versions 4.3.1 and above to assure accurate markup of title text attributes and to allow automatic retrieval of the font name list.
2 - Program access is by Puppy Menu->Utility->PupShutdown or by the default Ctrl+Shift+X keyboard shortcut which is configured for IceWm, JWM, Openbox, Fluxbox, LXDE and LXPanel. If the Xfce window manager is currently active, the hotkey can be set manually as follows: Xfce Settings->Keyboard->Application Shortcuts.
3 - For those with laptops or notebooks, version 1.6 supports suspend (standby) in ACPI compliant systems. This function is mediated by Acpitool, and the PupShutdown suspend icon turns blue if the utility is installed, or grey if disabled. Keep in mind, the suspend option does not work equally in all systems. More information is available here, here, and here.
4 - PupShutdown is compatible with zigbert's Stardust desktop environment (DuDe), but Stardust uses a proprietary jwmrc-personal file which may overwrite the PSD hotkey entry. This is easily restored through PSD menu->Set preferences->Configuration options->H-key.
Maybe there is some trick there that can help your program to do what you like it to do?
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
Nooby,nooby wrote:Seaside what about this one then?
http://www.murga-linux.com/puppy/viewtopic.php?t=56077
title PupShutdown-1.6
That looks very nice and useful.
I'll have to check that out.
Thks,
s
-
Jasper
Hi seaside,
Thank you for your continuing time, patience and help.
I reset the Event Manager time interval to 10 minutes with just my Wine sfs running with two Wine programs minimised to my system tray/task bar.
Then after some 12 minutes powered-off from my tower button - the save was effected because on rebooting the Event Manager save time was still set to 10 minutes.
As a separate trial I also used htop sorted by "S" to see what happened when I clicked the blue desktop save icon. The save was quick and effective (as checked upon rebooting), but the yellow message did not clear.
The way your main pet and your save pet programs work in my Lupu 5.25 is to my absolute satisfaction - but I do have a small concern that you intended my only option to be to use the new desktop save icon to save and power-off - so that perhaps some circumstance may arise which could leave me at risk of save file corruption. Normally I would save without any programs running and with all sfs unloaded and I run an automatic fsck on booting. I also take regular backups.
I will let you know if anything happens that I think you would want to read about and I'll keep an eye on this thread in case you discover the currently unexplained reasons as to how and why your program operates differently in 431 and 525.
My regards and huge thanks
Added:
seaside - to answer your question - yes, 100% sure.
Thank you for your continuing time, patience and help.
I reset the Event Manager time interval to 10 minutes with just my Wine sfs running with two Wine programs minimised to my system tray/task bar.
Then after some 12 minutes powered-off from my tower button - the save was effected because on rebooting the Event Manager save time was still set to 10 minutes.
As a separate trial I also used htop sorted by "S" to see what happened when I clicked the blue desktop save icon. The save was quick and effective (as checked upon rebooting), but the yellow message did not clear.
The way your main pet and your save pet programs work in my Lupu 5.25 is to my absolute satisfaction - but I do have a small concern that you intended my only option to be to use the new desktop save icon to save and power-off - so that perhaps some circumstance may arise which could leave me at risk of save file corruption. Normally I would save without any programs running and with all sfs unloaded and I run an automatic fsck on booting. I also take regular backups.
I will let you know if anything happens that I think you would want to read about and I'll keep an eye on this thread in case you discover the currently unexplained reasons as to how and why your program operates differently in 431 and 525.
My regards and huge thanks
Added:
seaside - to answer your question - yes, 100% sure.
SFS-Exec-pupsave-noshut
Maybe we can kill many birds with one stone.
Here's "SFS-Exec-pupsave-noshut" which is a pure "save to the pupsave only". No poweroff - just save.
This version locks down every door to the pupsave file (probably overkill) so that any process that tries to write to the pupsave file will fail. No reboot will save to the pupsave file.
See first post for "SFS-Exec-pupsave-noshut.pet"
Cheers,
s
NOTE: I forgot to mention that this version provides the opportunity to back up your pupsave file with no risk of corruption because it has been made "read-only"
Here's "SFS-Exec-pupsave-noshut" which is a pure "save to the pupsave only". No poweroff - just save.
This version locks down every door to the pupsave file (probably overkill) so that any process that tries to write to the pupsave file will fail. No reboot will save to the pupsave file.
See first post for "SFS-Exec-pupsave-noshut.pet"
Cheers,
s
NOTE: I forgot to mention that this version provides the opportunity to back up your pupsave file with no risk of corruption because it has been made "read-only"
-
Jasper
Hi seaside,
Thank you very much for your "SFS-Exec-pupsave-noshut" which is a pure "save to the pupsave only". No poweroff - just save.
It had (for me) a few side effects, perhaps because of the way I installed it; but for anyone else who tries it - I'd suggest (merely as a sensible precaution) backup your current save file before installing and using that save pet.
The side effects were 5.25 reverted to Openbox whereas I had switched to JWM, your sfs loader stopped working and Firefox (my default browser) offered to import some settings.
My regards
Personally I like the non-corruption facet; but I much prefer having the normal save at intervals/reboot/power-off as well. nooby knows of some forum members who are likely to be interested. Also, it's 3.45 a.m. here so I'm going to do a nooby and hit the sack.
Thank you very much for your "SFS-Exec-pupsave-noshut" which is a pure "save to the pupsave only". No poweroff - just save.
It had (for me) a few side effects, perhaps because of the way I installed it; but for anyone else who tries it - I'd suggest (merely as a sensible precaution) backup your current save file before installing and using that save pet.
The side effects were 5.25 reverted to Openbox whereas I had switched to JWM, your sfs loader stopped working and Firefox (my default browser) offered to import some settings.
My regards
Personally I like the non-corruption facet; but I much prefer having the normal save at intervals/reboot/power-off as well. nooby knows of some forum members who are likely to be interested. Also, it's 3.45 a.m. here so I'm going to do a nooby and hit the sack.
Wow indeed. By all means let the imagination run wild and sooner or later this will be really cool. I wish I understood what is going on better.
I should first make a trusty copy of my current pupsavefile and then install your new thing and that would allow me to save without being shut down.
And this save is would unfortunately change some things as Jasper noticed so that maybe has to be sorted out.
Seaside any clue why his FF suddenly thought it started anew? Not good.
But I love that you are at it. Wish me could contribute. It is very exciting.
Re "why your program operates differently in 431 and 525."
As I remember one of the two main guys making Lupu525 wrote in that thread that 525 are different so one need to get it at that level because he did warn that one need to be aware of that.
So maybe one should list which Puppy that is best to experiment with.
1. Seaside use Puppy 431 mainly.
2. Jasper test on oops sorry have forget.
3. Nooby test mainly on Snowpup that has both Lupu511 and Lupu525 base.
Puppies in the 5 series seems to be different enough to run into some trouble
So we need to find a puppy derivate of 431 that I can use on my computer or I have to wait until you Seaside get more fond of develop for the 511 or 525 versions
I will eat now and then test on Snow using a copy of snow renamed to Snowsfs
I should first make a trusty copy of my current pupsavefile and then install your new thing and that would allow me to save without being shut down.
And this save is would unfortunately change some things as Jasper noticed so that maybe has to be sorted out.
Seaside any clue why his FF suddenly thought it started anew? Not good.
But I love that you are at it. Wish me could contribute. It is very exciting.
Re "why your program operates differently in 431 and 525."
As I remember one of the two main guys making Lupu525 wrote in that thread that 525 are different so one need to get it at that level because he did warn that one need to be aware of that.
So maybe one should list which Puppy that is best to experiment with.
1. Seaside use Puppy 431 mainly.
2. Jasper test on oops sorry have forget.
3. Nooby test mainly on Snowpup that has both Lupu511 and Lupu525 base.
Puppies in the 5 series seems to be different enough to run into some trouble
So we need to find a puppy derivate of 431 that I can use on my computer or I have to wait until you Seaside get more fond of develop for the 511 or 525 versions
I will eat now and then test on Snow using a copy of snow renamed to Snowsfs
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
This link is important?
http://www.murga-linux.com/puppy/viewto ... 325#371325
2byte describe it thus:
http://www.murga-linux.com/puppy/viewto ... 325#371325
2byte describe it thus:
So maybe we have to read there or even ask him if he has tested it on Lupu525?A tiny gtkdialog utility for backing up the live pupsave file. You no longer need to reboot with pfix=ram in order to backup the savefile. Lots of built-ins and safety features make it very "oops" proof.
Auto-detects the current savefile.
Generates the backup file name with the date and time appended.
Checks the available space for the backup file.
Will not perform the backup if anything is incorrect.
Displays real-time status and progress feedback.
Supports 2fs and 3fs save file types.
It's easy fast and works very well.
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
-
Jasper
Hi nooby,
seaside has contributed to the "important" thread linked in your post immediately above. Further, it seems that method is not always totally safe from corruption.
I saw somewhere that you have tested seaside's "sfs" program(s) on 5 different Puppy versions.
Since you want to contribute here, your best efforts might be just testing this new super-safe save pet on your many Puppy versions and reporting here what, if any, side effects you noticed on each version tried.
My regards
seaside has contributed to the "important" thread linked in your post immediately above. Further, it seems that method is not always totally safe from corruption.
I saw somewhere that you have tested seaside's "sfs" program(s) on 5 different Puppy versions.
Since you want to contribute here, your best efforts might be just testing this new super-safe save pet on your many Puppy versions and reporting here what, if any, side effects you noticed on each version tried.
My regards
Seaside the most unusual error did happen.
I tried to find sfs-exec-shutdown in ppm but it was not there in Fluppy13 that I test on
So I got two save buttons and could not decide which is which so I deleted the one that shut the computer totally off and kept the new one that only save without any shut down.
That took away sfs-exec from ROX and it made teh sfs-exec to refuse to start FF.sfs
So I tried to delete the savefile to put in the old savefile there and start all over but then this one poppedup
fluppy13s/.fuse_hidden0000000300000002
Is that something that Jemimah has built in or did you add the fuse whatever a fuse is? I go do pfix=ram instead but much work to change everything that Jemimah think is the best for me Double click and such
oops yes I should go for finding out.
I guess I have to make a list of which puppy is not 511 or 525.
Snow 5 is 513 and Snow 16 is 525
Lighthouse seems to be based on 420 so that is a good target to practice on.
Fluppy seems to be based on 430? so that would be a good one too.
Maybe fluppy is the one that can confirm what Seaside says about 511 and up being different. So I go for preparing a Fluppy now to do the test on my computer to see what happens.
I tried to find sfs-exec-shutdown in ppm but it was not there in Fluppy13 that I test on
So I got two save buttons and could not decide which is which so I deleted the one that shut the computer totally off and kept the new one that only save without any shut down.
That took away sfs-exec from ROX and it made teh sfs-exec to refuse to start FF.sfs
So I tried to delete the savefile to put in the old savefile there and start all over but then this one poppedup
fluppy13s/.fuse_hidden0000000300000002
Is that something that Jemimah has built in or did you add the fuse whatever a fuse is? I go do pfix=ram instead but much work to change everything that Jemimah think is the best for me
Double click and suchoops yes I should go for finding out.
I guess I have to make a list of which puppy is not 511 or 525.
Snow 5 is 513 and Snow 16 is 525
Lighthouse seems to be based on 420 so that is a good target to practice on.
Fluppy seems to be based on 430? so that would be a good one too.
Maybe fluppy is the one that can confirm what Seaside says about 511 and up being different. So I go for preparing a Fluppy now to do the test on my computer to see what happens.
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
-
Jasper
Hi seaside,
I am delighted with your "SFS-Exec" and your original "save and power-off" pets and, personally, I neither need nor ask for any changes.
However, whilst I have not the least understanding of what may be practicable; it may (most highly improbably, just may) please all of the users all of the time if the blue save icon were made into a right click menu.
So that say,
In off mode it would show a large red cross (flashing or static) on the blue background and any auto save setting would be set to zero and it would be impossible to save by any normal method (with or without any useful additional reminder note).
In super-save mode there would be a large green tick on the blue background indicating that it is safe to save (and/or backup to any location) on-the-fly (without prospective corruption) and any timer setting would be reset to zero and no other normal save method would be available.
In normal save mode there would be the original blue desktop icon, but a save interval could be set as preferred (perhaps even superimposed on the icon) and the normal save would take place on a menu reboot or power-off as well as adhoc use of this mode.
My regards
I am delighted with your "SFS-Exec" and your original "save and power-off" pets and, personally, I neither need nor ask for any changes.
However, whilst I have not the least understanding of what may be practicable; it may (most highly improbably, just may) please all of the users all of the time if the blue save icon were made into a right click menu.
So that say,
In off mode it would show a large red cross (flashing or static) on the blue background and any auto save setting would be set to zero and it would be impossible to save by any normal method (with or without any useful additional reminder note).
In super-save mode there would be a large green tick on the blue background indicating that it is safe to save (and/or backup to any location) on-the-fly (without prospective corruption) and any timer setting would be reset to zero and no other normal save method would be available.
In normal save mode there would be the original blue desktop icon, but a save interval could be set as preferred (perhaps even superimposed on the icon) and the normal save would take place on a menu reboot or power-off as well as adhoc use of this mode.
My regards
Haha Seaside I am so sorry. I was wrong and you where very right
One need to do it the way you described. To not save a pupsave before installing sfs-exec-noshut So now that thing works but still ...
I still fail to get what is supposed to not get saved?
I installed a pet and that one are still there after reboot. That is not supposed to happen on a puppy431 Fluppy flavor OS when I do just a reboot is it? The pet should just go int o RAM and then get flushed at reboot?
One need to do it the way you described. To not save a pupsave before installing sfs-exec-noshut So now that thing works but still ...
I still fail to get what is supposed to not get saved?
I installed a pet and that one are still there after reboot. That is not supposed to happen on a puppy431 Fluppy flavor OS when I do just a reboot is it? The pet should just go int o RAM and then get flushed at reboot?
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
Nooby,nooby wrote:
I still fail to get what is supposed to not get saved?
I installed a pet and that one are still there after reboot. That is not supposed to happen on a puppy431 Fluppy flavor OS when I do just a reboot is it? The pet should just go int o RAM and then get flushed at reboot?
After you have installed the "SFS-Exec-pupsave-noshut.pet", saved to the pupsave file and rebooted, could you post the results of typing in a terminal "mount".
This might help to discover what's happening.
Regards,
s
Maybe you mean before I start using firefox to be able to answer you?
Okay I do the cli now.
Okay I do the cli now.
That fuse file what is that?# 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)
#
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
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 '
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 '
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
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
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