trawglodyte wrote: ↑Sun Jan 07, 2024 8:37 am
williwaw wrote: ↑Sun Jan 07, 2024 7:23 am
how does the the generated kernel line or puppy stanza in grub.cfg read?
This is my stripped down menuentry template. Which can be used by replacing the 4 times it says "BionicPup64_8.0" with whatever you name the folder, and replacing "Puppy" and "eea65cbd-8683-4c1a-850a-99888a7a8324" with the label and UUID of your partition. Which you can find with <blkid> in terminal.
Code: Select all
menuentry "BionicPup64_8.0" {
search --fs-uuid --set eea65cbd-8683-4c1a-850a-99888a7a8324
linux /BionicPup64_8.0/vmlinuz acpi_osi=Linux net.ifnames=0 pmedia=usbflash pdrv=Puppy psubdir=/BionicPup64_8.0 pfix=fsck
initrd /BionicPup64_8.0/initrd.gz
}
This boots a pup on my system, but there are many things you can add. On some systems you may need to add additional parameters.
.....and that's pretty much how I do it. I know the recommendation now is to use Grub2config, though I stick with Grub4DOS because it's solid, time-tested and just "works".
I, too, have a "template", for which I just copy, paste a new entry, and change three items. Example:-
Code: Select all
title Quirky 64
find --set-root uuid () b142cd08-ce81-413e-b963-12b393d8eaa3
kernel /Quirky64/vmlinuz pdrv=b142cd08-ce81-413e-b963-12b393d8eaa3 psubdir=/Quirky64 pmedia=satahd pfix=fsckp
initrd /Quirky64/initrd.gz
title Fossapup 64
find --set-root uuid () b142cd08-ce81-413e-b963-12b393d8eaa3
kernel /Fossapup64/vmlinuz pdrv=b142cd08-ce81-413e-b963-12b393d8eaa3 psubdir=/Fossapup64 pmedia=satahd pfix=fsckp edd=off
initrd /Fossapup64/initrd.gz
title Bionicpup 64
find --set-root uuid () b142cd08-ce81-413e-b963-12b393d8eaa3
kernel /Bionicpup64/vmlinuz pdrv=b142cd08-ce81-413e-b963-12b393d8eaa3 psubdir=/Bionicpup64 pmedia=satahd pfix=fsckp
initrd /Bionicpup64/initrd.gz
title Studio 1337
find --set-root uuid () b142cd08-ce81-413e-b963-12b393d8eaa3
kernel /Studio1337/vmlinuz pdrv=b142cd08-ce81-413e-b963-12b393d8eaa3 psubdir=/Studio1337 pmedia=satahd pfix=fsckp
initrd /Studio1337/initrd.gz
You can see the pattern. "edd=off" is just an additional parameter for Fossapup64, 'cos it seems to need it. Yes, I could run the bootloader stuff again every time I add/delete another Pup - I used to in the early days! - until I came to understand that manual editing is quicker, simpler & gives you more control. And I prefer it.
Yes, I could run Grub2Config on the big rig and re-write my boot menu for the modern way of doing things, but frankly, there's no point. I've used it for a couple of recent 'mobile' Puppies - one on a flash-drive, one on an SD card - which may end up running on other machines, and it works well. But my main 'kennels' is staying right where it is; although UEFI, it's set to 'Legacy' in the BIOS.....the MyCrudSoft SecureBoot/FastBoot crap was long ago disabled.......and Grub4DOS does what I want it to; boots my Pups!
My distro-hopping days are over; I'm staying right here in Puppyland. If I was still trying out mainstream distros on a regular basis, I'd repartition/reformat the SSD to GPT, go with UEFI full-time, and use Grub2Config instead.....but for me, there's no need. I use 2 other OSs on an occasional basis; HaikuOS runs from an old PATA/IDE SSD I rescued from the ancient Dell lappie that died year before last, converted to a USB 'external' SSD.......and ChromeOS 'Reflex' runs from a flash drive. Both plug in as & when required; when not, they're quite happy where they are.
95% of the time, it's Puppy all the way. (Yeah, yeah, I know; familiarity DOES breed contempt..!)
Mike.