On Fri, 7 Apr 2006 22:44:41 +0200 maximilian attems wrote: > 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. I would be very surprised if this wasn't simply an act of no longer _special-casing_ lilo as has been done till now. Please provide a reference to avoid further speculation. > grub is the _default_. So what? Being used by default by official Debian kernels does not allow any package to overrule a user favoring a different boot loader. The use of lilo must be respected, until officially unsupported generally in Debian. - Jonas -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ - Enden er nær: http://www.shibumi.org/eoti.htm
Attachment:
pgpt3Z1QasFGN.pgp
Description: PGP signature