Page 1 of 3
psav=....conquering/understanding puppy boot command(s)
Posted: Wed 01 Feb 2017, 11:43
by belham2
Hi all,
First, want to link to a thread that got me to post this thread (didn't continue it there as it was sort of off-topic in that thread):
http://www.murga-linux.com/puppy/viewtopic.php?t=109560
Scroll down to the 4th msg, and read Drunkjedi's question & then read jlst's answer right after.
I'd like to continue that discussion here.
Many times after frugally installing any puppy-related OS, I still find myself scratching my head trying to understand certain boot parameters & why I have to resort to tricks sometimes to get the puppy's to see and read the savefile and/or savefolder.
So let's just start with the basics:
--A Tahr64 6.0.5 frugal installation
--all copied into a folder named "tahr64"
--the whole drive (sda) has one partition, thus sda1
--it is governed by grub4dos
--your 'savefolder' (or savefile, can both apply here?) has been setup too
Here's my question based off of two Tahr64 grub4dos entries, one to have the 'savefolder' used' the other to run in 'ram':
Code: Select all
title Tahr64 6.0.5.3 with Savefolder (sda1)
find --set-root --ignore-floppies --ignore-cd /tahr64/puppy_tahr_6.0.5.3.sfs
kernel /tahr64/vmlinuz pmedia=usbflash psubdir=tahr64 pfix=fsck
initrd /tahr64/initrd.gz
title Tahr64 6.0.5.3 RAM-only (sda1)
find --set-root --ignore-floppies --ignore-cd /tahr64/puppy_tahr_6.0.5.3.sfs
kernel /tahr64/vmlinuz pmedia=usbflash psubdir=tahr64 pfix=ram
initrd /tahr64/initrd.gz
They both boot fine, but I would like to be able, on the 2nd entry, to have it not only boot in RAM, but also boot the savefolder too (before or as it goes into RAM), so I can use Tahr64 in RAM fully with my settings from the savefolder
(but I don't want the USB to stay plugged-in as I don't want to save anything after everything loads into RAM). Possible??
If it is possible, how? I've been reading this link jlst provided:
https://raw.githubusercontent.com/puppy ... README.txt but I honestly am still confused how to get either a pup-created 'savefile' and/or 'savefolder' to load when you want to run in RAM mode (and thus be able to pull the USB completely out of its socket after everything loads into RAM, which many times I am forced to do).
This question applies across all of pup-land for me. I've figured it out how to do it in DebianDogs (thanks to Fred's explaining) and anything debian-related, but I am still unclear how to do this (and indeed if it is it even possible with a 'savefolder' as opposed to the ubiquitous 'savefile') in puppy-land? What should I be entering in grub4dos to make this possible? Should I be using the 'psave=' command in the kernel line of grub4dos? Or something else??
Thanks for any help with this.
Posted: Wed 01 Feb 2017, 11:58
by Burn_IT
Just use PMEDIA=USBIDE instead?? (I think - that is what I do)
Posted: Wed 01 Feb 2017, 12:14
by belham2
Burn_IT wrote:Just use PMEDIA=USBIDE instead?? (I think - that is what I do)
Hi BurnIT,
In my 2nd grub4dos entry above, like this then:
Code: Select all
title Tahr64 6.0.5.3 RAM-only (sda1)
find --set-root --ignore-floppies --ignore-cd /tahr64/puppy_tahr_6.0.5.3.sfs
kernel /tahr64/vmlinuz pmedia=usbide psubdir=tahr64 pfix=ram
initrd /tahr64/initrd.gz
...and then puppy will load either a 'savefile' and/or 'savefolder', whichever it finds? Or does puppy only do it for 'savefile'??
Posted: Wed 01 Feb 2017, 12:20
by Burn_IT
I don't use savefolders, but it certainly finds my savefile.
What's more if there isn't one on that drive it will search as usual.
Posted: Wed 01 Feb 2017, 12:26
by belham2
Burn_IT wrote:I don't use savefolders, but it certainly finds my savefile.
What's more if there isn't one on that drive it will search as usual.
I'll give it a try. I know drunkjedi uses pmedia=satacd sometimes, but I am totally unclear if this works when you have maybe 10-20 frugally-installed pups on just one partition, all enconsced in their own (named) folder.
Just would like to be able to run some of them in RAM, with the savefolder or the savefile (whatever may be the case for that partifular pup) loaded, and then be able to "pull" the USB out and enjoy that pup fully in RAM.
Thanks.
Posted: Wed 01 Feb 2017, 12:30
by Burn_IT
I use several Puppies from that device: each in its own folder.
I am at work at the moment and can't keep plugging in the stick to look as it is not allowed.
Posted: Wed 01 Feb 2017, 12:34
by backi
Me interested too ........
Good Questions belham !
Posted: Wed 01 Feb 2017, 13:30
by Burn_IT
Code: Select all
title Puppy Linux Precise 5.71 frugal
find --set-root /precise57/vmlinuz
kernel /precise57/vmlinuz pmedia=idehd psubdir=precise57
initrd /precise57/initrd.gz
title Puppy Linux Precise 5.71 frugal Fresh
find --set-root /precise57/vmlinuz
kernel /precise57/vmlinuz pmedia=idehd psubdir=precise57 pfix=ram
initrd /precise57/initrd.gz
title Puppy Linux Lucid 528 frugal
find --set-root /lupu5000/vmlinuz
kernel /lupu5000/vmlinuz pmedia=idehd psubdir=lupu5000
initrd /lupu5000/initrd.gz
title Puppy Linux Lucid 528 frugal CF
find --set-root /lupu5000CF/vmlinuz
kernel /lupu5000CF/vmlinuz pmedia=idehd psubdir=lupu5000CF
initrd /lupu5000CF/initrd.gz
title Puppy Linux 420 Frugal
find --set-root /puppy420/vmlinuz
kernel /puppy420/vmlinuz pmedia=idehd psubdir=puppy420
initrd /puppy420/initrd.gz
title Puppy Linux 420 Frugal fresh
find --set-root /puppy420/vmlinuz
kernel /puppy420/vmlinuz pmedia=idehd psubdir=puppy420 pfix=ram
initrd /puppy420/initrd.gz
title Puppy Linux Lucid 528 Frugal fresh
find --set-root /lupu5000/vmlinuz
kernel /lupu5000/vmlinuz pmedia=idehd psubdir=lupu5000 pfix=ram
initrd /lupu5000/initrd.gz
This is from my hard drive.
The only change for my USB is the IDEHDs are changed to USBHD
Posted: Wed 01 Feb 2017, 13:51
by backi
Made a Test with SaveFolder .
As far as i can see ......did not load SaveFolder
menu.lst:
title Puppy tahr 6.0.5 (sdb1/TAHRPUPCE)
find --set-root --ignore-floppies --ignore-cd /TAHRPUPCE/initrd.gz
kernel /TAHRPUPCE/vmlinuz pmedia=usbide psubdir=TAHRPUPCE pfix=ram
initrd /TAHRPUPCE/initrd.gz
Posted: Wed 01 Feb 2017, 14:00
by Sailor Enceladus
If you turn the savefolder into an adrv it should all run in ram. It's not perfect (some settings are reset) but it works
http://www.murga-linux.com/puppy/viewtopic.php?p=882505#882505
Posted: Wed 01 Feb 2017, 14:15
by belham2
Hi Backi and Sailor,
@Backi, yeah, me too, tried many different variations with the pmedia=usb### thing, and no joy. Seems like I just found my reason never to use "Savefolders" again.
Why is it nearly every pup recommends 'savefolders" then? 
I mean, it's not that hard to resize a savefile, but it sure is a pain in the ass when you want to run in RAM and can't enjoy your savefolder while doing it.
@Sailor, an adrv? What about the adrv(s) that are already present in some pups as they boot up? Can you have two differently named adriv(s) and still have them boot (without conflicting with each other) during initial start to go into RAM? This again seems like a pain in the butt (making an 'adrv' and all), haha, when all a poor user wants to do is----if wanting to enjoy RAM only and unplug the USB---to be able to have either the savefile and/or the savefolder loaded. Not sure of the technical challenges behind this, but it sure seems like something the woof-ce Gods could consider, no???
Posted: Wed 01 Feb 2017, 14:38
by Sailor Enceladus
Haha yeah squashing the savefolder into an adrv is like a remaster but a lot quicker. Try it and see if you like the idea
Posted: Wed 01 Feb 2017, 14:59
by drunkjedi
Savefolder works great with Fatdog.
Here's my syslinux.cfg entry for Fatdog to load the folder from my hdd to RAM, the base sfs is also loaded in ram but in expanded state which makes it slower to boot but faster in work, Libreoffice, gimp start in an instant and work fast.
Code: Select all
label fatdog
linux /fd64/vmlinuz
initrd /fd64/split/initrd
append rootfstype=ramfs waitdev=0 basesfs=expand:device:sda7:/FD64-710/fd64.sfs savefile=ram:device:sda7:/fd64save
menu label Fatdog64
text help
Start Fatdog normally with small initrd.
endtext
While I tried what jlst showed for tahr64.
Here's it's entry
Code: Select all
label tahr64-savelocation
linux /tahr64/vmlinuz
initrd /tahr64/initrd.gz
append psave=sda7:/tahr64save/
menu label Tahr64-savelocation
text help
Start Tahr64 puppylinux
endtext
Doesn't work.
I have to add pmedia=satacd for it to find my savefolder.
I will ask him again on previous thread.
Posted: Wed 01 Feb 2017, 15:16
by backi
Hi belham !
Maybe be Puli could give some hints on loading a Puppy completely in Ram ....and removing usb Stick .
A lot of complex methods to load....
http://murga-linux.com/puppy/viewtopic.php?t=96964
Posted: Wed 01 Feb 2017, 19:13
by belham2
drunkjedi wrote:
While I tried what jlst showed for tahr64.
Here's it's entry
Code: Select all
label tahr64-savelocation
linux /tahr64/vmlinuz
initrd /tahr64/initrd.gz
append psave=sda7:/tahr64save/
menu label Tahr64-savelocation
text help
Start Tahr64 puppylinux
endtext
Doesn't work.
I have to add pmedia=satacd for it to find my savefolder.
I will ask him again on previous thread.
Hi drunkjedi,
I have tried to take this (for my tahr64 frugal install):
Code: Select all
label tahr64-savelocation
linux /tahr64/vmlinuz
initrd /tahr64/initrd.gz
append psave=sda7:/tahr64save/
menu label Tahr64-savelocation
text help
Start Tahr64 puppylinux
endtext
...and I have put "pmedia=satacd" in every line, then trying to boot, and it fails each time trying to boot it for RAM-only.. How the heck are ya getting this to work to see your savefolder? Where do I enter in the grub4dos config you posted above? Should I be excluding something (I take out the 'psave=sda#:/tahrsave/', right? And substitute in the pmedia=satacd, yes? Man, I am one wildly confused person right now
Can you post EXACTLY what your grub4dos entry is that you got the savefolder recognized on a RAM-only boot? Gracias
Posted: Mon 06 Feb 2017, 10:48
by backi
Seems your question has never been answered belham .
I am curious too .
Posted: Tue 07 Feb 2017, 01:23
by puppyluvr
Hello,
Frugal install?
Two easy ways.
1.
Make your save to a directory.
Boot in ram.
Mksquashfs the directory.
Put the .sfs in your home directory with the Puppy .sfs etc..
Edit initrd to load it at boot.
2.
Make a save to a directory
Boot in ram
Merge the directory, with the original Puppy .sfs.
Swap the new .sfs with the original
Reboot.
I have a 2gb Puppy 5.1.1 that runs in ram..
Posted: Tue 07 Feb 2017, 07:17
by bigpup
I wish they would change this boot command to something else, because people keep thinking it does something completely different.
puppy pfix=ram (used as a boot command when booting).
or
pfix=ram (used as an option in a boot menu entry).
This tells Puppy to BOOT and NOT use the SAVE!!!!!
Boot options used by Puppy:
acpi=off Default on for PCs >2001, may give boot/shutdown Probs
pfix=ram Run totally in RAM
ignore saved sessions
pfix=nox commandline only, do not start x
pfix=copy copy .sfs files to RAM (slower boot, faster running)
pfix=nocopy do not copy .sfs to RAM (faster boot, slower running
pfix=fsck do filesystem check on lupusave (and host partition)
pfix=clean file cleanup (simulate version upgrade)
pfix=purge more radical file cleanup (to fix broken systems)
pfix=<n> Number of save files to ignore
Example:
Here you are telling Puppy to load and
not use the save.
Code: Select all
title Tahr64 6.0.5.3 RAM-only (sda1)
find --set-root --ignore-floppies --ignore-cd /tahr64/puppy_tahr_6.0.5.3.sfs
kernel /tahr64/vmlinuz pmedia=usbide psubdir=tahr64 pfix=ram
initrd /tahr64/initrd.gz
Posted: Tue 07 Feb 2017, 15:07
by drunkjedi
Hi bigpup,
Which boot parameter will load savefile/folder totally in RAM?
I haven't yet got my tahr64 6.0.5 to honour my boot option of psave= .
For my savefolder, neither psave=sda7:/tahr64save/ nor psave=sda7:/tahr64save work.
Posted: Tue 07 Feb 2017, 15:12
by drunkjedi
Hi belham, sorry I missed your question about pmedia=satacd.
I don't use grub4dos so don't know where to put that in config file.
I guess you should do as bigpup has shown, in front of kernel line.