Puppy Linux Discussion Forum

[benny7440]

As the title states, I can't see anything that isn't produced by the os itself in this machine, so I need to create a pupsave file but can't remember what the system asks (in order) nor what the alternatives it gives me to choose from. With that info beforehand I can, more or less, safely reboot, create the said pupsave file & then install the jre package: I need it. Can't stand surfing the web or staying connected without my favorite web radio station.

Thanks for any screen shots or lists made available for me & others to inspect.

EDIT: BTW, I searched for a while in the we for a command in a Puppy Linux shell that could give me the specific os I'm running but failed to find it, at least uncoded.

[666philb]

hi benny7440

1 save to file default is yes
2 which drive up & down keys to select
3 ext2 or ext3 up & down to select default = ext2
4 name of save (optional)
5 normal - light encryption - heavy encryption default= normal
6 size default 500ish mb
7 are you sure you want to save


so return, return, down return, return return return return gets you a 520mb ext3 savefile on the first partition of the first drive

[benny7440]

Thanks for responding, 666philb!

It worked almost perfectly in the sense that it's persistent now. But there's a problem: I've 3 partitions in my only 120GB internal disk, all my previous linux settings were located at sda2 (2nd part.) including all the puppies & their respective pupsave files and so on. When I rebooted noticed that sda1 & sda2 were mounted & checked & found that the pupsave file went to sda1. I don't like this a bit because all my problems with PL528 started in relation to dealing with an sda1 problem (self-created) by February: d/l W8CP & saved it in sda1 without it been mounted. The latter signified that the part is mounted Read-Only.

A curious point in here: how can the pupsave file be saved in there if the part always complained when mounting it that it was just for Reading? Have to check it now from this newly created puppy...it refuses to be unmounted as well as sda2 because it's been used by puppy... Didn't check if I can put & delete anything in there, yet.

I copied a text file to a newly created folder there successfully then deleted both. So, there's no more problems with that partition from this os, at least.

Back to the main issue now, how should I proceed to avoid mounting at boot time that partition? I guess have to move/link that pupsave file to sda2 or delete/rename it before next reboot/shutdown & follow the same steps as before only more carefully...

PS. There's an option for stating the folder where I want that file, do I have to put in the whole path like: sda2/puppy528-005 benny-pupsavefile.ext3?

[666philb]

hi benny7440

you've a couple of options....

1 when puppy makes a savefile in a place other the folder where the puppy files are kept. It creates a text file called the 'savemark' that tells puppy where to look for the savefile. it'll either be in the lucid folder.,, or just on the top directory of the drive that contains the lucid folder.

delete it , and copy your savefile to the lucid folder.

2. or failing that, deleting the savefile and creating a new one with
return, down return, down return, return return return return should hopefully put it in the right place

[benny7440]

Thanks for responding, 666philb!

I fetched for that file SAVEMARK & it just contain a character = 1 in it, STRANGE!

I've noticed that since I managed to create a pupsave file that it finds it requires me to put something at startup (which I don't know what it might be, since I'm not able to see anything considered to be 'output' on the screen until the os is up & running. Before all this I don't remember having seen such a file: SAVEMARK. So, I conclude that something has changed...

[666philb]

hi benny7440

it maybe because you have created more than one savefile? in which case you are offered a choice at boot up 0=none 1=savefile1 2=savefile2 etc and return

[benny7440]

Thanks for replying, 666philb!

What I would like to do now is to fix things so that partition #1 doesn't get mounted at startup. How can I obtain that without braking my system again?

[666philb]

[benny7440]

Thanks 666philb for replying! I finally did it right.