From: Stefan Monnier on
> What always bothers me with boot loaders is that they need a system to
> configure & manage them. Now, in a multi-boot system, the next question
> is which one?

100% agreement. As much as I hate Apple, they got some of the boot
loader right. Grub2 should follow their lead: build up (most of) the
grub.cfg at boot time by probing the various drives.

So all that remains is a way to configure the appearance you want,
to specify the rules used to find boot targets (the rules
currently embedded in update-grub and os-prober), and to specify the
boot arguments.


Stefan


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: John Hasler on
Stefan Monnier writes:
> As much as I hate Apple, they got some of the boot loader right.

Easy with total control of the hardware.
--
John Hasler


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: Stefan Monnier on
>> As much as I hate Apple, they got some of the boot loader right.
> Easy with total control of the hardware.

That's just an excuse: from my Grub2 prompt, I can list the contents of
just about all my partitions, so obviously there's no hardware issues in
the way to let Grub2 look for target kernels to load and build up a boot
menu from it.


Stefan


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org