Nooby, have a great weekend,nooby wrote: But when one use Firefox or some other broswer do they really remember settings and such.
Perhaps better to have the ".mozilla" directory linked somewhere outside of the pupsave file.
s
nooby wrote: So I should restart with pfix=ram and place the .mozilla on the mnt/home or sda or whatever that works. and make a less big pupsavefile.
You can't use "pfix=ram" because any changes you make will not be saved to the pupsave file.
Usually you move the /root/.mozilla directory to the /mn/home or sda, and then make a link back to /root/.mozilla. In order for the new link of /root/.mozilla to survive, it has to be saved to the pupsave file.
Cheers,
s
Nooby,nooby wrote: But your sfs-exec shut down X and one get to the prompt and have to xwin in again. But it works if one only start the sfs up using right click using roxfiler.
Nooby,nooby wrote:
I go Menu > Files > SFS-Exec-Dir and then at that moment it shut me down to Prompt and I do xwin and it start up but the only way to get sfs-exec working is to instead go to Rox and then go to the Dir with sfs files and do right click and that works without problem.
.
Regards,Jasper wrote:
(a) When I use the new Save-pup icon on my desktop it works but also performs a power off.
Yes, that's as designed
(b) If, on the other hand, instead of using the save icon I make say, a new folder in my /root directory and then use Menu > Shutdown > Reboot computer the new folder is in /root after the reboot.
That should not have happened. Can you create a new file, open a terminal and type "which snapmergepuppy" and then see if it returns a path. If it does not, then do a Menu>Shutdown>Reboot and see if that newly created file appears.
Jasper,Jasper wrote:Hi seaside,
Thank you for your reply and in response:
First I made a new folder in /root named aaseasidetest and then subsequently (after rebooting) a new file named zzzseasidetest.
I copied and pasted your command and both times got only the hash "#".
I rebooted from the Menu and both the new folder and the new file appear in root after completion of the rebooting.
My regards
PS I actually like it this way, but this is not really the point.
Could that explain why the files got saved?
I have never unloaded (or attempted to unload) either of the two standard type files which are listed at the top of the Unloader window.
Cheers,nooby wrote:
My result. I created a folder in mnt/home and did a reboot and it survived.
I made a new folder and rebooted and that one survived too.
/mnt/home is not the pupsave file. So, files written here will survive
I also did the which snapmergepuppy and that gave only the hash sign.
Snowpup5 is Lupu513 so most likely it would also act that way on all the puppies that are based on Lupu511.
I think you've found something here, because these problems seem to come up with pups above 510
I also made a more keen test of my problem with shut down to prompt.
1. Survive if one do Terminal and also
2. if one do Menu > Filesystem > Filemanagers > SFS-Exec-Dir but
3. But if one do right click on desktop and then filesystems > Filemanagers > SFS-Exec-Dir that gives an instant shut down to prompt.
?????????
So that would be needed to get dealt with unless numerous newbies get totally lost with a prompt and wild guess what to write xwin is not that intuitive to write if one are new but usually the text says so though
Nope sfs-exec-dir should not allow changes without one hit save button. That is no good! But if there is no way to protect it at least we should set the save time to zero or nil or 0 and that way it would not save a lot of things?
I agree
which snapmergepuppy
what was that suppose to give in normal circumstances?
If SFS-Exec-Pupsave is installed, then only the # will be returned
Yes, those two files listed at the top are the main sfs file and the pupsave file and cannot be unloaded.nooby wrote:Seaside! Jasper take up something that I also have wondered about.
Could that explain why the files got saved?
I have never unloaded (or attempted to unload) either of the two standard type files which are listed at the top of the Unloader window.
But logically don't sfs-exec need them loaded? when one tell it to save to pupsave using the savebutton and before it shut down then it need to access these files that is loaded during boot why would you load them if the SFS-Exec did not need them?
Nooby,nooby wrote:New report from latest Quirky that is kind of experimental if I get Barry. Okay all of them with that name are such.
Anyway. To my surprise but maybe Seaside warned about it and me poor reader of any text.
If it already have a .mozilla and Qrky has SeaMonkey then SFS-Exec Dir refuse to start Firefox. It says that it has loaded it but nothing show up.
And then when I use the unloader then that one says it is loaded.
How does one get FF going if the Seamonkey is the default browser.
Opera loaded as usual.
I tested to have symlink to another .mozilla outside pupsave but that did not get FF going either.
kind of odd. But using right click did not shut it down.