Bug#361270: Upgrade of initramfs-tools made kernel unbootable with lilo

[maximilian attems <maks@sternwelten.at>]

On Fri, Apr 07, 2006 at 09:58:07PM +0100, David Jarvie wrote:
> On Friday 07 April 2006 20:30, maximilian attems wrote:
> > On Fri, Apr 07, 2006 at 08:51:12PM +0100, David Jarvie wrote:
> >
> > if grub is around lilo isn't run.
> > if you really want lilo remove grub from your system and
> > update-initramfs will call lilo.
> >
> > ...
> >
> > i'll document the fact that if you use lilo you shouldn't have grub
> > around in README.Debian.
> 
> If both lilo and grub are installed, I can understand not running lilo 
> automatically, but surely there should at the very least be a warning prompt 
> about the possible need to run lilo. (And I mean a prompt requiring a 
> response, so that it can't be overlooked when you're doing a bit upgrade of 
> the system.) Essentially, if lilo is installed, make sure the upgrader knows 
> that the system might not boot without further action.
> 
> The same issue has hit me more than once recently - not just with 
> initramfs-tools upgrades. A mere warning in README.Debian isn't enough given 
> that it could make a system unbootable.


kernel-package wants to drop ability to run lilo on the postinstall.
grub is the _default_.

update-initramfs can easily check for an lilo.conf and warn in those cases.

--
maks