How to get Grub to pick a pupsave file.. in dpup wheezy

[charlie6]

Hi,
i'm currently using the legacy grub (version 0.97) with Pemasu's dpup wheezy-3.5.2.5.; and i would like to get Grub to pick a pupsave file.. in dpup wheezy; this maybe could also be applied to other later Puppies as Lucid, Wary, Precise, Raring, Slacko.

This subject had aleardy been introduced in 2009 by fm (i.e. forum member) crash applied to Puppy-4.1.2 and 4.2; here
http://www.murga-linux.com/puppy/viewtopic.php?t=38030
and continued for Puppy-4.3.1 here by fm Rattlehead and CatDude :
http://murga-linux.com/puppy/viewtopic. ... e1d7e9e79a
It is also documented under the Psave paragraph here:
http://puppylinux.org/wikka/BootParametersPuppy

So i did some trials:
1. edited the init file in initrd.gz:
- open initrd.gz using this pet: Edit-Initrdgz-1.4.pet
- edit the init script: added the 5 code lines (1st link) + 1 other line here
http://www.murga-linux.com/puppy/viewto ... 691#298691
- rebuild initrd.gz
- in /boot/grub/menu.lst, i edited the boot parameters as recommended in fm CatDude's post here:
murga-linux.com/puppy/viewtopic.php?t=7 ... e1d7e9e79a

results:
- nothing has changed in Grubs working: i still have a step for selecting one of the present wheezysave-XXX.3fs files.
- something encouraging: as a my-being-script-writing-newby, i meanwhile am happy to get the edited initrd.gz still working OK
- the Grub psave parameter (see 3rd link) does not work in my current puppy: i wonder if that information would'nt be a bit outdated or only limited to puppies version 4.3.1 ...

attached is my init file with a fake .tar.gz extension: just drop the .tar.gz extension to read it.
- the edited code lines are commented with reference 131115 (i.e. line nr 499 ; and lines 833 to 839)

i wonder if those code lines are still relevant to the later pupsave files syntaxes as for instance raringsave-xxx.3fs or wheezysave-xxx.4fs, or else, etc...
rather than pupsave-xxx.3fs in puppies till version 4.3.1...?

Thanks for any help
Charlie

[musher0]

Hello, Charlie6.

I don't know about opening and editing the initrd, but the following menu.lst entry works for me, in Grub4Dos, however:

Code: Select all

title Wheezy 3.5.2.5
root (hd1,1)
kernel (hd1,1)/wheezypup/lancement/vmlinuz quiet pkeys=cf pmedia=satahd root=/dev/ram0 pdev1=sda2 psubdir=wheezypup psave=chr130213.2fs max_loop=14 ramdisk_size=100000
initrd (hd1,1)/wheezypup/lancement/initrd.gz
boot

I indicate:
pmedia, for the type of disk
pdev1, on what disk is the pupsave
psubdir, in what folder
psave, the name of the savefile

The other paramaters are important too, but irrelevant for this subject.

Those precisions reduce the load time greatly because Puppy doesn't have
to look in all the partitions and folders to find its pupsave file.

I hope this helps.

musher0

[charlie6]

Bonjour Musher0,
merci for your quick answer

Hello, Charlie6.
I don't know about opening and editing the initrd, but the following menu.lst entry works for me, in Grub4Dos, however:
...
musher0

just one question: have you more than one save file inside your wheezypup subdir ?

Sure I'll give it a try...but i might perhaps have to install grub4dos instead...

Meilleures salutations, charlie

last edited:i gave it a try ...:
i have copied and adapted the kernel line to my menu.lst file:
no change ...! i again got to choose among the wheezysave-xxx files.
BTW, the init script does not have any psave parameter (it has pfix pmedia etc... but no psave); that was fm crash's purpose: to introduce a psave parameter.
Next trial: migrate to grub4dos...

[musher0]

Hello charlie6.

Yes I do have 2 other pupsaves in my wheezy folder.
And it does stop for the sub-choice of pupsave files...

Ça ne t'aide pas beaucoup, hein ? Désolé. /
This doesn't help you much, eh? Sorry.

However, I can't remember where, but I read in this forum a successful
way of using the parameters so that Puppy launches directly only the
pupsave of Mrs. X, and not the one for Mr. X or for Mr. X junior. (It was a
family context.)

Bye for now.
musher0

[don570]

grub supports UUID

http://en.wikipedia.org/wiki/UUID

______________________________________

[charlie6]

Hi Musher0,

...the following menu.lst entry works for me, in Grub4Dos, however:

Code: Select all

title Wheezy 3.5.2.5
root (hd1,1)
kernel (hd1,1)/wheezypup/lancement/vmlinuz quiet pkeys=cf pmedia=satahd root=/dev/ram0 pdev1=sda2 psubdir=wheezypup psave=chr130213.2fs max_loop=14 ramdisk_size=100000
initrd (hd1,1)/wheezypup/lancement/initrd.gz
boot

i have installed Grub4Dos v1.9 and edited menu.lst as follows:

Code: Select all

title Puppy wheezy 3.5.2.5 (sda3/slaktin)
  root (hd0,2)
  kernel (hd0,2)/slaktin/vmlinuz quiet pmedia=atahd pfix=fsck pdev1=sda3 psubdir=slaktin psave=wheezysave-work.3fs
  initrd (hd0,2)/slaktin/initrd.gz
  boot

which looks quite similar to the one above ...
and ...NO success: grub keeps displaying the sub-choice for savefiles ... !???

... btw how did the name of your savefile be (re)named as chrxxxx.2fs instead of the regular wheezysave-XXX.2fs ...?????
I have tried to rename my wheezysave-work.3fs file to whatever other name (i.e. pupsave-work.3fs): wheezy only looks for wheezysave-XXX files; if none found then it switches to pristine boot ..

@don570

grub supports UUID

would that chrxxx.2fs savefile be relevant to UUID ?

Thanks for any answer !
charlie

[Médor]

Hi charlie6,

try this:

psubdir="slaktin"

Cheers,
Médor.

[charlie6]

Bonjour Médor !

Hi charlie6,
try this:

psubdir="slaktin"

Got a try...no worse... no better
thanks anyway,
Charlie

[musher0]

Hi Musher0,

...the following menu.lst entry works for me, in Grub4Dos, however:

(...)
Thanks for any answer !
charlie

Hello, Charlie.

The sequence

pdev1=sda2 psubdir=wheezypup psave=wheezysave-chr130213.2fs

refers to my own set-up only. It's only an example.

You're right, one of my pupsave files for wheezypup is actually named
wheezysave-chr130213.2fs. Thanks for pointing it out. I'll do the
correction in my menu.lst file. What can I say, to err is human...

Your grub entry looks ok to me.

title Puppy wheezy 3.5.2.5 (sda3/slaktin)
root (hd0,2)
kernel (hd0,2)/slaktin/vmlinuz quiet pmedia=atahd pfix=fsck pdev1=sda3 psubdir=slaktin psave=wheezysave-work.3fs
initrd (hd0,2)/slaktin/initrd.gz
boot

Maybe try Médor's suggestion; he must have his reasons for suggesting
quotes around the subdir target. The wikka pages at
http://puppylinux.org/wikka/BootParametersPuppy
are not that clear, with upper-case letters being used sometimes
and lower-case letters being used at other places.

Bye for now.

musher0

[musher0]

Bonjour Médor !

Hi charlie6,
try this:

psubdir="slaktin"

Got a try...no worse... no better
thanks anyway,
Charlie

Hello again, Charlie.

Maybe browse the wheezypup thread, and if no other user has
had the problem, ask your question directly to pemasu, the author
of this derivative?

On the other hand, I'm sorry to say, it might be one of those
mysteriously incomplete Puppy features that it's no use fighting...

Bye for now.

musher0

[charlie6]

Hi Musher0,

... it might be one of those mysteriously incomplete Puppy features that it's no use fighting...

I like ... such ... fightings!
I believe it's just a question to write some more script lines into the init script ... as forum member crash did a few years ago ...

I perhaps would need months of learning script writing ... to do it... so i hope someone much experienced would be interested ...

It has something to do with the DISTRO_FILE_PREFIX in the FINDING PUPPY FILES section of init script:
- files having the relevant distro DISTRO_FILE_PREFIX (here "wheezy") and located in the same SUBDIR have their name copied to a /tmp/PUPSAVES directory (or file ...?)
- to pick-up the wanted wheezysave-XYZ.3fs file (what was done through the psave parameter in fm's crash 5 script lines addon version - see above), one needs to "grep" the file having the XYZ matching the wheezysave-XYZ's extension;
- and, at last, select and load it ...!
Thanks anyway, Charlie

[musher0]

Hi Musher0,

... it might be one of those mysteriously incomplete Puppy features that it's no use fighting...

I like ... such ... fightings!
I believe it's just a question to write some more script lines into the init script ... as forum member crash did a few years ago ...

I perhaps would need months of learning script writing ... to do it... so i hope someone much experienced would be interested ...

It has something to do with the DISTRO_FILE_PREFIX in the FINDING PUPPY FILES section of init script:
- files having the relevant distro DISTRO_FILE_PREFIX (here "wheezy") and located in the same SUBDIR have their name copied to a /tmp/PUPSAVES directory (or file ...?)
- to pick-up the wanted wheezysave-XYZ.3fs file (what was done through the psave parameter in fm's crash 5 script lines addon version - see above), one needs to "grep" the file having the XYZ matching the wheezysave-XYZ's extension;
- and, at last, select and load it ...!
Thanks anyway, Charlie

Allô, Charlie.

No-no, I believe that it is very simple, no scripts required. I know for a
fact that someone on this forum has posted a solution, I read it maybe 2
years ago. I was surprised at the simplicity.

But where is it... on which thread... to find it again.
"Une aiguille dans un tas de foin..." (Transl.: "A needle in a haystack...")

BFN.

musher0

[bigpup]

kernel (hd0,2)/slaktin/vmlinuz quiet pmedia=atahd pfix=fsck pdev1=sda3 psubdir=slaktin psave=wheezysave-work.3fs

This is what psave is suppose to do.

Psave allows a user to specify which PupSave files to use. This allows the pupsave selection menu to be skipped (shows if more than one savefile is found).

I think where you are putting psave, in the kernel line, could be your problem.

The pfix=fsck

(do filesystem check on pupsave and host partition).

should be at end of kernel line.

I think you need to identify the save file to use before giving the command to do a filesytem check of it.

[charlie6]

Bigpup,
thanks for your answer !
i have put psave (and Psave) as show hereunder without booting straight on the referenced wheezysave-xxx.3fs file.

kernel (hd0,2)/slaktin/vmlinuz psave=wheezysave-work.3fs quiet root=/dev/ram0 pmedia=atahd psubOK=true psubdir=/slaktin pfix=fsck

As the init script in initrd.gz does not have any psave parameter in it
(see also http://murga-linux.com/puppy/viewtopic. ... &start=475),
would the psave be a kernel parameter?
Charlie

[musher0]

Bigpup,
thanks for your answer !
i have put psave (and Psave) as show hereunder without booting straight on the referenced wheezysave-xxx.3fs file.

kernel (hd0,2)/slaktin/vmlinuz psave=wheezysave-work.3fs quiet root=/dev/ram0 pmedia=atahd psubOK=true psubdir=/slaktin pfix=fsck

As the init script in initrd.gz does not have any psave parameter in it
(see also http://murga-linux.com/puppy/viewtopic. ... &start=475),
would the psave be a kernel parameter?
Charlie

Hi, charlie6.

Sorry to trump bigpup.

No, psave is not a kernel parameter, it is a Puppy parameter.

Secondly, with a Puppy, AFAIK, no parameters should ever be added on
the initrd.gz line in grub's menu.lst.

Bye for now.

musher0