I wrote a patch back then to support specifying root filesystem by its
label or UUID, see URL below.
But it was never merged (except into some versions of OpenWRT, google it).
The simpler way it to use an initrd, as already mentioned.
See:
Hi Pascal,
Thanks. Thus many of grub's options. I doubt I will ever really
understand it :). Amazing.
warm regards,
John
On Sun, 29 Mar 2020, Pascal Hambourg wrote:
Le 29/03/2020 ? 07:46, j...@nhfn.net a ?crit :
One more question. Initrd is what actually reads and
Pascal Hambourg composed on 2020-03-29 10:31 (UTC+0200):
> j...@nhfn.net composed:
>> On the other hand, Knoppix 7.2 has a larger kernel and a
>> smaller minirt.gz file. I am guessing Knoppix adds another boot level to
>> getting the final linux system up and running?
> I don't know about
Le 28/03/2020 à 20:49, Pascal Hambourg a écrit :
You'd rather use a persistent identifier that the kernels kows about :
PARTUUID. Get the value with blkid.
Can't remember whether the kernel knows about PARTLABEL too, which would
be nicer. Guess not.
Just checked in the Linux kernel
Le 29/03/2020 à 07:46, j...@nhfn.net a écrit :
One more question. Initrd is what actually reads and executes grub
and friends?
I don't know what you mean by "friends" but no, the initrd does not read
and execute GRUB.
Boot sequence is :
- platform firmware (BIOS, UEFI) loads and run
Hi Pascal,
Thanks for your clear explanation. Finally makes sense to me.
One more question. Initrd is what actually reads and executes grub and
friends?
In the system I am running, antiX, initrd is much bigger than vmlinuz.
On the other hand, Knoppix 7.2 has a larger kernel and a
Le 28/03/2020 à 21:47, Felix Miata a écrit :
What's a LABEL or PARTLABEL or UUID for if the kernel doesn't understand it?
As I wrote, they are meant for use by an initramfs.
Without an initramfs, the kernel must mount the root filesystem by itself.
With an initramfs, the kernel mounts the
Pascal-liste composed on 2020-03-28 21:20 (UTC+0100):
> Felix Miata in English composed:
>> Pascal Hambourg composed on 2020-03-28 20:49 (UTC+0100):
>>> The kernel
>>> itself does not understand UUID or LABEL.
>> ...
>>> You'd rather use a persistent identifier that the kernels kows about :
>>>
Le 28/03/2020 à 21:04, Felix Miata a écrit :
Pascal Hambourg composed on 2020-03-28 20:49 (UTC+0100):
The kernel
itself does not understand UUID or LABEL.
...
You'd rather use a persistent identifier that the kernels kows about :
PARTUUID. Get the value with blkid.
Can't remember whether
Pascal Hambourg composed on 2020-03-28 20:49 (UTC+0100):
> The kernel
> itself does not understand UUID or LABEL.
...
> You'd rather use a persistent identifier that the kernels kows about :
> PARTUUID. Get the value with blkid.
> Can't remember whether the kernel knows about PARTLABEL too,
Le 28/03/2020 à 17:56, Toerless Eckert a écrit :
I would like to have a grub config that will work even
if the disk is re-plugged into a different SATA port
and independent of whether other disks are plugged in.
Lets say i today have this config:
set root='hd5,gpt2'
search --no-floppy
I would like to have a grub config that will work even
if the disk is re-plugged into a different SATA port
and independent of whether other disks are plugged in.
Lets say i today have this config:
set root='hd5,gpt2'
search --no-floppy --fs-uuid --set=root 4bdb3675-62ff-499f-9fc4-e5fd8c7ba777
12 matches
Mail list logo
