* Joachim Wiedorn <ad_debian@joonet.de> [Mon Dec 13, 2010 at 05:53:48PM +0100]: > Michael Prokop <mika@debian.org> wrote on 2010-12-13 16:36: > > update-grub just generates the grub.cfg, the lilo package doesn't > > execute lilo (and therefore doesn't touch MBR) as long as there's no > > /etc/lilo.conf. So both packages can and do co-exist. > Thank for more information - and also thanks to Colin. > I only see one problem if grub-pc and lilo is full configured and > then the both hook scripts will be executed, e.g.: > 1) /etc/kernel/postinst.d/zz-update-grub -> update grub.cfg > 2) /etc/kernel/postinst.d/zz-lilo -> update MBR (for lilo) > Result: lilo is the bootloader > 3) the package grub-pc will be updated -> update MBR (for grub) > Result: grub is the bootloader > Is this the result that the admin want? I don't know. It's better than not having the option to have grub and lilo both installed at the same time at all, IMHO. The fact that iff lilo.conf is present lilo will be executed can be documented proberly with an according warning in for example the long description of the package as well as in the README.Debian. > > It breaks existing deployment environments. > What do you want to say here? Please give me a (short) example. Think of a chroot style installer (working offline and without udebs) where grub and lilo both are available but only one of them will be configured as bootloader (either because of user's choice or because lilo does not support the specific setup and grub will be used therefore). > > Drop the conflicts in the lilo package and everything will continue > > to work as it used to? > Yes, apart from the case I have written above. But o.k. if nobody found > my builded example realistic it is the easiest to remove the "Conflicts". I understand your concerns and would love to have an configurable option to specify which bootloader should be the *active* one so it's possible to have grub, lilo, extlinux, $WHATEVER_BOOTLOADER installed at the same time but execute only the hooks/scripts of the according/specified bootloader. Am I right that there's also no configureable option (chmod -x ... doesn't count as such) to disable the scripts inside /etc/kernel at all? (For example /etc/kernel/postinst.d/zz-update-grub bugs on me, see #597084.) regards, -mika-
Attachment:
signature.asc
Description: Digital signature