Michael Prokop <m...@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 breaks existing deployment environments. What do you want to say here? Please give me a (short) example. > 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". Have a nice day, Joachim (Germany) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101213175348.7d4f6...@jupiter.home
