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. > IMO this is a bug that shouldn't reach squeeze, therefore choosing > severity serious. I think these defined "Conflicts" does not break the regular functionality of a Debian system, but provide clarification, which bootloader make the work. So the severity should be minor. I have CCed to debian-boot, perhaps there is someone who have more arguments. Have a nice day, Joachim (Germany) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org