Puppy Linux Discussion Forum

Hello all, I have a puppy currently with two savefolders, one's mine and the other for my dad, to avoid messing up my dad's workflow and so I can make stuff on mine.
Now, I want to know how do I let the BOOT to boot directly into an specific savefolder.
Is there a way?

To be clear, the idea is to have two different boot-menu entries like
puppy frenchiveruti -> boots and loads my savefolder
puppy dad -> boots and loads my dad's savefolder.


Thanks.

Hello frenchiveruti
about what you want exactly is not possible because of these factors ...

• Grub4dos is installed on MS-Dos, it is independent of the puppy installation

• the function is to recognize all the S.O. installed and create a visual menu in MS-Dos

The savefolder could be considered as a username in other Linux distributions, therefore, here and in any other S.O. It is not possible to start this way, it would be something like starting a car and then turning the key ... something like that

In the case of puppy, the search for savefolders is performed by the init file that is inside init.gz and if there are more than two savefolders, it makes a menu where it asks which one you want to continue loading puppy with (check my screen)...

In my case, every time I start a new installation of any puppy what I do is essentially this:
Start puppy / save session with savefolder / reboot system ===> start again / I enter the puppy installation folder and create a new empty folder and copy the name of savefolder and add this to the name "-empty" looking like this: Example "precisesave-empty" without any type of extension ...
When the system restarts it will detect two savefolders and will be forced to ask which one to start with, regardless of whether one of them is completely empty and thus also have the possibility to start or create a new session

This would be the way to have what you are looking for, perhaps there is another method activating the users function in puppy but I do not know the process and with the original system this is what can be done without making any kind of adjustment to said program and system. .

I hope this information is useful to you and if you find a way to obtain what you are looking for exactly, do not hesitate to share us how you did it

Cheers!

The psave parameter is supposed to do that:

psave=:dad.3fs

psave=:frenchiveruti.3fs

The colon character (:) is necessary.

This should be faster because it does not need to search the partitions:

psave=sda1:/dad.3fs

psave=sda1:/frenchiveruti.3fs

which is assuming that the save files are on sda1 at the root (top) of the file system and not in a folder.

williams2 wrote: Tue Sep 22, 2020 11:02 pm The psave parameter is supposed to do that:

psave=:dad.3fs

psave=:frenchiveruti.5fs

The colon character (:) is necessary.

This should be faster because it does not need to search the partitions:

psave=sda1:/dad.3fs

psave=sda1:/frenchiveruti.3fs

which is assuming that the save files are on sda1 at the root (top) of the file system and not in a folder.

Hi williams2

thnks for your apport

I really didn't know about this interesting fact and I have one question...

this works with savefolder too or only with savefile?

will it work this way?

psave=sda1: /focalpup_9.0.0/ focalpupsave-dad or

psave=:focalpup_9.0.0/ focalpupsave-dad

I appreciate your comment

Cheers!

You are asking questions with us having no specific information.

What Puppy specific version?
If it is focalpup_9.0.0.
And it is a frugal install in a directory named focalpup_9.0.0
The save is a folder named focalpupsave-dad and it is also in the directory focalpup_9.0.0

This should work:

psave=:/focalpup_9.0.0/ focalpupsave-dad

But do you know where to but it in the menu.lst entry?

It would be best for good advice if you posted what is in your menu.lst

Open the menu.lst file in a text editor.
Copy and paste the contents into a post, so we can see what your actual entries are and can give good advice, on where to put psave=

sometimes the specific questions are not asked because we lack the knowledge to make the correct questions.
Indeed, the solution was the psave parameter for boot.
Just using the path to the save folders makes the boot to distinguish between them
Thanks all!

this works with savefolder too or only with savefile?

Yes, it should work with a save folder.

The information is from the README.txt file in the Fossapup iso.

So, "psave=sdb4:/lxpupsc/mysave" says that the savefolder is on the sdb4 partition
in the "/lxpupsc" directory, named "mysave".

FossaPup64 9.5 viewtopic.php?f=40&t=88

williams2 wrote: Wed Sep 23, 2020 6:17 am

this works with savefolder too or only with savefile?

Yes, it should work with a save folder.

The information is from the README.txt file in the Fossapup iso.

So, "psave=sdb4:/lxpupsc/mysave" says that the savefolder is on the sdb4 partition
in the "/lxpupsc" directory, named "mysave".

FossaPup64 9.5 viewtopic.php?f=40&t=88

hello williams2/bigpup
it really works !!
I did as is inside the readme in focalpup and I just had to duplicate the input so that one went directly to the savefolder and another to ask which session to load
this is my entry in menu.lst

title Puppy focalpup dad (sda1 / focalpup_9.0.0)
find --set-root uuid () 641945f7-a018-4b64-89b4-9b153931b2e6
kernel /focalpup_9.0.0/vmlinuz pdrv = 641945f7-a018-4b64-89b4-9b153931b2e6 psubdir = / focalpup_9.0.0 pmedia = atahd (pupsfs = 641945f7-a018-4b64-89b4-9b64-89b4-9b153931b2e6 psubdir = / focalpup_9.0.0 pmedia = atahd (pupsfs = 641945f7-a018-4b64-89b4-9b1p1539save = sfopup6 pmedia = atahd) dad) pfix = fsck, nocopy
initrd /focalpup_9.0.0/initrd.gz

title Puppy focalpup 9.0.0 (sda1 / focalpup_9.0.0)
find --set-root uuid () 641945f7-a018-4b64-89b4-9b153931b2e6
kernel /focalpup_9.0.0/vmlinuz pdrv = 641945f7-a018-4b64-89b4-9b153931b2e6 psubdir = / focalpup_9.0.0 pmedia = atahd pfix = fsck, nocopy
initrd /focalpup_9.0.0/initrd.gz

bigpup
this is how this works, check the first entry, highlight it in parentheses

and woof, I learned something new this day ...