On Mon, Dec 13, 2010 at 04:00:04PM +0100, Joachim Wiedorn wrote: > Michael Prokop <m...@debian.org> wrote on 2010-12-13 11:11: > > Now version 1:22.8-9 introduces: > > > > Conflicts: grub-legacy, grub-pc > > > > I don't see any reason why this should be enforced, actually this > > avoids deployments of systems where users can choose between lilo > > and grub as bootloader as both can't be distributed at the same time > > with the conflicts mentioned above. > > To manage newer kernel in Debian the system need hook scripts for kernel > and initrd which can be found in /etc/kernel and /etc/initramfs/. These > hook scripts will always be executed after kernel update or initrd update. > > If more then one bootloader is installed, each bootloader (say: grub- > legacy, grub-pc or others) will try to install his code into MBR while > kernel or initrd will be updated. This is not usefull.
This is a misunderstanding of GRUB. /etc/kernel/*/zz-update-grub only updates /boot/grub/grub.cfg, and never touches the MBR. The only time the grub-pc package touches the MBR is when the grub-pc package itself is installed or upgraded, and even that can be turned off in debconf. -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
