psav=....conquering/understanding puppy boot command(s)

Using applications, configuring, problems
Message
Author
belham2
Posts: 1715
Joined: Mon 15 Aug 2016, 22:47

psav=....conquering/understanding puppy boot command(s)

#1 Post 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
The question:

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.

User avatar
Burn_IT
Posts: 3650
Joined: Sat 12 Aug 2006, 19:25
Location: Tamworth UK

#2 Post by Burn_IT »

Just use PMEDIA=USBIDE instead?? (I think - that is what I do)
"Just think of it as leaving early to avoid the rush" - T Pratchett

belham2
Posts: 1715
Joined: Mon 15 Aug 2016, 22:47

#3 Post 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'??

User avatar
Burn_IT
Posts: 3650
Joined: Sat 12 Aug 2006, 19:25
Location: Tamworth UK

#4 Post 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.
"Just think of it as leaving early to avoid the rush" - T Pratchett

belham2
Posts: 1715
Joined: Mon 15 Aug 2016, 22:47

#5 Post 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.

User avatar
Burn_IT
Posts: 3650
Joined: Sat 12 Aug 2006, 19:25
Location: Tamworth UK

#6 Post 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.
"Just think of it as leaving early to avoid the rush" - T Pratchett

backi
Posts: 1922
Joined: Sun 27 Feb 2011, 22:00
Location: GERMANY

#7 Post by backi »

Me interested too ........

Good Questions belham !

User avatar
Burn_IT
Posts: 3650
Joined: Sat 12 Aug 2006, 19:25
Location: Tamworth UK

#8 Post 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
"Just think of it as leaving early to avoid the rush" - T Pratchett

backi
Posts: 1922
Joined: Sun 27 Feb 2011, 22:00
Location: GERMANY

#9 Post 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

Sailor Enceladus
Posts: 1543
Joined: Mon 22 Feb 2016, 19:43

#10 Post 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

belham2
Posts: 1715
Joined: Mon 15 Aug 2016, 22:47

#11 Post 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???

Sailor Enceladus
Posts: 1543
Joined: Mon 22 Feb 2016, 19:43

#12 Post 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 :lol:

User avatar
drunkjedi
Posts: 882
Joined: Mon 25 May 2015, 02:50

#13 Post 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.

backi
Posts: 1922
Joined: Sun 27 Feb 2011, 22:00
Location: GERMANY

#14 Post 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

belham2
Posts: 1715
Joined: Mon 15 Aug 2016, 22:47

#15 Post 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 :lol:

Can you post EXACTLY what your grub4dos entry is that you got the savefolder recognized on a RAM-only boot? Gracias :wink:

backi
Posts: 1922
Joined: Sun 27 Feb 2011, 22:00
Location: GERMANY

#16 Post by backi »

Seems your question has never been answered belham .
I am curious too .

User avatar
puppyluvr
Posts: 3470
Joined: Sun 06 Jan 2008, 23:14
Location: Chickasha Oklahoma
Contact:

#17 Post by puppyluvr »

:D 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..
;-)
Close the Windows, and open your eyes, to a whole new world
I am Lead Dog of the
Puppy Linux Users Group on Facebook
Join us!

Puppy since 2.15CE...

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#18 Post 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
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 :shock:
YaPI(any iso installer)

User avatar
drunkjedi
Posts: 882
Joined: Mon 25 May 2015, 02:50

#19 Post 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.

User avatar
drunkjedi
Posts: 882
Joined: Mon 25 May 2015, 02:50

#20 Post 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.

Post Reply