Bug#494422: It IS a bug somewhere that installing 2 bootloader packages breaks booting
On Wed, Aug 27, 2008 at 10:16:40AM +0200, Jonas Smedegaard wrote:
> 2) bootloader packages conflict with each other
> (bad - leaves a moment with *no* bootloader if switching)
Not that bad IMHO. Not having a bootloader package is _not_ the same as
not having a bootloader. GRUB (both Legacy and 2) propagates its files
to /boot/grub which is not handled by the package system. I think LILO
Ah, and both GRUBs already conflict with each other.
> 3) bootloader packages coordinate to flag which of them is in use,
> and other packages must respect this flagging
I'd have to see the details, but I'm not very fond of the extra burden
this could mean to bootloader maintainers.
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org