How to stop "SAVING TO FILE" at shutdown?
- linuxsansdisquedur
- Posts: 248
- Joined: Tue 13 Jan 2009, 21:17
- Location: South of France
A simple way to don't save file at shutdown or re-use other savepup without running in ram :
you delete savepup and copy an already saved one in home and shutdown when the copy is just done.
Next boot you will find this savepup instead of the last session one
(i use pizzapup in frugaal -puppy2.14 puplet- )
you delete savepup and copy an already saved one in home and shutdown when the copy is just done.
Next boot you will find this savepup instead of the last session one
(i use pizzapup in frugaal -puppy2.14 puplet- )
le max avec le min
Could you tell more exactly how one do this?linuxsansdisquedur wrote: A simple way to don't save file at shutdown or re-use other savepup without running in ram :
you delete savepup and copy an already saved one in home and shutdown when the copy is just done.
Next boot you will find this savepup instead of the last session one
(i use pizzapup in frugaal -puppy2.14 puplet- )
Would not that only work if you do this within the 30 minutes before it has saved automatically or if you have set it to not save ever?
And Can one really delete a savefile that is booted? Don't you have to unmount the savefile in some way?
You suggest that one copy the savefile one want from a secured place over to the subdir of the deleted one.
But that one get run over by the shutdown version. So that is not working as I get it.
Sure I know almost nothing but something in your way of describing it fail to make me sure it works. Could it be that the older 2.14 version allowed it while the more recent puppy 431 would not?
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
- linuxsansdisquedur
- Posts: 248
- Joined: Tue 13 Jan 2009, 21:17
- Location: South of France
sorry for late answer (in holidays )
dunno if it work with puppy4 (gotta try in my 2 testing pupplet... and i tell u ) but yes i just copy my pupsave and when i want it back i copy it on the pupsave and reboot just when that done ! and it work !
(it make the same thing when you boot with other puppy or live cd and change the pupsave with your backup!)
dunno if it work with puppy4 (gotta try in my 2 testing pupplet... and i tell u ) but yes i just copy my pupsave and when i want it back i copy it on the pupsave and reboot just when that done ! and it work !
(it make the same thing when you boot with other puppy or live cd and change the pupsave with your backup!)
le max avec le min
I am still wondering about this one. I know too little to decide on it.linuxsansdisquedur wrote:sorry for late answer (in holidays )
dunno if it work with puppy4 (gotta try in my 2 testing pupplet... and i tell u ) but yes i just copy my pupsave and when i want it back i copy it on the pupsave and reboot just when that done ! and it work !
(it make the same thing when you boot with other puppy or live cd and change the pupsave with your backup!)
I did a few test but how does one protect from this happening at same time it automatically does a pupsave?
If one look at Htop then it shows if a pupsave is being done or???
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
Thanks! Using this stops the session from always saving without my permission in 421retro on a flash stick. There was 3 of them around lines 600-700 for me and I had to comment out the last one under "13)".sc0ttman wrote:Open the terminal, type 'geany /etc/rc.d/rc.shutdown' (without the quotes)
then find this line, it should be around line 825 (use search - Ctrl+F)
The line above is the one the launches snapmergepuppy, comment it out, with a # at the start of the line. So it looks like this:Code: Select all
/usr/sbin/snapmergepuppy /initrd/pup_ro1 /initrd/pup_rw
Code: Select all
#/usr/sbin/snapmergepuppy /initrd/pup_ro1 /initrd/pup_rw
Then I changed this to stop it from saving every 30 minutes:
And added this to stop each bootup from warning me that the shutdown doesn't save "properly":Jasper wrote:You could permanently change System>Puppy Event Manager>Save Session> Interval to 0.
Basically I have my "base" set up exactly how I want, with always 18M free, and if I want to make any changes to it (not too common since I'm using it mostly as an old "Firefoxbook") I can just press the Save button on the desktop.Smithy wrote:Another simple way to get around this is to just add to /etc/rc.d/rc.local:
Code:
rm /etc/.XLOADED
I know it is an old thread, but i can not see any other forumthreads that do apply to my problem.
I tried first the solution for getting a option to save or not saving the session. But then did not work after several trials, i tried to disable all lines corresponding to saving the session. As it is now:
So does puppy linux still use this config file or is it something i do wrongly?
I tried first the solution for getting a option to save or not saving the session. But then did not work after several trials, i tried to disable all lines corresponding to saving the session. As it is now:
So does puppy linux still use this config file or is it something i do wrongly?
Last edited by sitdown on Sun 04 Jan 2015, 14:55, edited 1 time in total.
Asked to save at shutdown
More updated info here:
http://murga-linux.com/puppy/viewtopic.php?t=81911
Also here:
http://murga-linux.com/puppy/viewtopic.php?t=77418
More updated info here:
http://murga-linux.com/puppy/viewtopic.php?t=81911
Also here:
http://murga-linux.com/puppy/viewtopic.php?t=77418
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)
What i did to disable saving session automaticly and to give me a textbox with choice every shutdown.
1. I disabled autosavefunction every 30 minuts.
System/puppy event manager/session:0
2. Disable autosave on shutdown, geany /etc/rc.d/rc.shutdown
I edited the lines below like this:
I also disabled lines with #, not sure if that was correct, but it does work as it is now. So i will not change anything if not i would hear something else from a geek out there :
- I also changed the System/Cpu scaling function, as i had problems with flash beeing "choppy", i guess others might have the same problem.
______________________________________________________________________
I will look into that, i did find more lines with the simular save session, as i understand it is different ways of installing puppy. CD/Flash/HD:
Thank you for that quick response.
I do find some interesting things with Puppy, it actually is quite informative. As now i found out that there is a cpu frequency adjusting "app?", i can easily find out how to change this. Probably it is the same with Ubuntu, but i never new it.
So maybe this could be a good platform to play the "corrupt" tetris battle game. I think that players beside hacking for unlimited cheats, as i never use also hack my game, so the pieces does slow down. I should not play it, but i find it relaxing but frustrating and i am hooked. LOL
1. I disabled autosavefunction every 30 minuts.
System/puppy event manager/session:0
2. Disable autosave on shutdown, geany /etc/rc.d/rc.shutdown
I edited the lines below like this:
Code: Select all
13) #PDEV1 and PUPSFS and PUPSAVE
#/initrd/pup_rw has tmpfs, pup_ro1 has ${DISTRO_FILE_PREFIX}save.2fs file (PUPSAVE), pup_ro2 has PUPSFS file.
#the above are in unionfs at /.
#(echo "$(eval_gettext "Saving session to \${SAVEFILE} (\${SAVEPART})...")" >/dev/console)
#(echo "Saving session to $SAVEFILE (${SAVEPART})..." >/dev/console)
#(/usr/sbin/snapmergepuppy /initrd/pup_ro1 /initrd/pup_rw)
dialog --yesno "Save session?" 0 0 >/dev/console
if [ $? -eq 0 ]; then
echo "Saving session to $SAVEFILE (${SAVEPART})..." >/dev/console
/usr/sbin/snapmergepuppy /initrd/pup_ro1 /initrd/pup_rw
fi
;;
Code: Select all
12)
TXT=`basename $SAVEFILE`
echo "$(eval_gettext "\${TXT} mounted directly top layer, session already saved.")" >/dev/console
#echo "`basename $SAVEFILE` mounted directly top layer, session already saved." >/dev/console
;;
3) #PDEV1.
echo "$(eval_gettext "Saving session to \${PDEV1}...")" >/dev/console #121104
echo "Saving session to $PDEV1..." >/dev/console
#the above are in unionfs at /.
#dialog --yesno "Save this session?" 0 0 >/dev/console
#if [ $? -eq 0 ]; then
#echo "Saving session to $SAVEFILE (${SAVEPART})..." >/dev/console
#/usr/sbin/snapmergepuppy /initrd/pup_ro1 /initrd/pup_rw
#fi
;;
# Følgende 2 linjer er default setting for lagring av session, fjern linjer
# over til første(#):
# :/usr/sbin/snapmergepuppy /initrd/pup_ro1 /initrd/pup_rw
# ;;
7) #PDEV1 and PUPSFS.
echo "$(eval_gettext "Saving session to \${PDEV1}...")" >/dev/console
#echo "Saving session to $PDEV1..." >/dev/console
#/usr/sbin/snapmergepuppy /initrd/pup_ro1 /initrd/pup_rw
;;
13) #PDEV1 and PUPSFS and PUPSAVE
#/initrd/pup_rw has tmpfs, pup_ro1 has ${DISTRO_FILE_PREFIX}save.2fs file (PUPSAVE), pup_ro2 has PUPSFS file.
#the above are in unionfs at /.
#(echo "$(eval_gettext "Saving session to \${SAVEFILE} (\${SAVEPART})...")" >/dev/console)
#(echo "Saving session to $SAVEFILE (${SAVEPART})..." >/dev/console)
#(/usr/sbin/snapmergepuppy /initrd/pup_ro1 /initrd/pup_rw)
dialog --yesno "Save session?" 0 0 >/dev/console
if [ $? -eq 0 ]; then
echo "Saving session to $SAVEFILE (${SAVEPART})..." >/dev/console
/usr/sbin/snapmergepuppy /initrd/pup_ro1 /initrd/pup_rw
fi
;;
______________________________________________________________________
I will look into that, i did find more lines with the simular save session, as i understand it is different ways of installing puppy. CD/Flash/HD:
Thank you for that quick response.
I do find some interesting things with Puppy, it actually is quite informative. As now i found out that there is a cpu frequency adjusting "app?", i can easily find out how to change this. Probably it is the same with Ubuntu, but i never new it.
So maybe this could be a good platform to play the "corrupt" tetris battle game. I think that players beside hacking for unlimited cheats, as i never use also hack my game, so the pieces does slow down. I should not play it, but i find it relaxing but frustrating and i am hooked. LOL
Pupsaveconfig will give you the choice
Pupsaveconfig will give you the choice. Nevertheless, one Puppy, a French one, does not care of pupsaveconfig and saves the session each time. The nice french Triton (Precise 5.7.1) perhaps will obey your scripts. On test.
To make "Don't save" the default in the dialog:
Include --defaultno in the code as shown here.
Include --defaultno in the code as shown here.
-
- Posts: 43
- Joined: Tue 20 Dec 2016, 23:16
A related question: How to clean up savefile ?
Last time I used Puppy i downloaded the light-49.0.linux-i686_6.sfs
(light Firefox). I tried to expand it using unsquashfs and it stopped dead
at about 65%, apparently for insufficient memory or disk space.
My savefile isize s 64M, and the icon on the taskbar used to report
62M personal storage, 35M free. After I rebooted, it reports 62M
personal storage, 1M free. and warnings about the personal
storage getting full are popping up. I think it is most probable
that what is filling the storage space is junk left by unsquashfs, but
whatever it may be, I want to know how to clean it.
(light Firefox). I tried to expand it using unsquashfs and it stopped dead
at about 65%, apparently for insufficient memory or disk space.
My savefile isize s 64M, and the icon on the taskbar used to report
62M personal storage, 35M free. After I rebooted, it reports 62M
personal storage, 1M free. and warnings about the personal
storage getting full are popping up. I think it is most probable
that what is filling the storage space is junk left by unsquashfs, but
whatever it may be, I want to know how to clean it.
-
- Posts: 790
- Joined: Wed 16 Apr 2008, 11:28
-
- Posts: 1543
- Joined: Mon 22 Feb 2016, 19:43
Re: A related question: How to clean up savefile ?
You just need to click on an sfs or right-click and select sfs_load I think (not unsquashfs), that way it won't "install" to the savefile or take up any room in it. If you specifically want it extracted to the savefile instead you probably need at least 128MB savefile or even 256MB savefile for Mozilla browser because it expands to around 100MB before even opening it and then like 20MB more setting up all it's cache stuff. 64MB is not really enough. It would make more sense to download a tar.xz / gz / bz2 or pet than a sfs if you want to do that "extract it to savefile" method though.Jose A. Senna wrote:Last time I used Puppy i downloaded the light-49.0.linux-i686_6.sfs
(light Firefox). I tried to expand it using unsquashfs and it stopped dead
at about 65%, apparently for insufficient memory or disk space.
My savefile isize s 64M, and the icon on the taskbar used to report
62M personal storage, 35M free. After I rebooted, it reports 62M
personal storage, 1M free. and warnings about the personal
storage getting full are popping up. I think it is most probable
that what is filling the storage space is junk left by unsquashfs, but
whatever it may be, I want to know how to clean it.