[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#356850: initramfs-tools: upon udev upgrade, system becomes unbootable if using lilo



[responding to the bug rather than only the d-kernel list]

On Tue, 14 Mar 2006 12:29:19 -0500
Anthony DeRobertis <aderobertis@metrics.net> wrote:

> Adeodato Simó wrote:
> 
> >   when udev gets upgraded, the latest initram is regenerated via
> >   udev's postinst.
> 
> This sounds to me to be a fundamentally bad idea. The current initrd
> clearly works --- the system did, after all, boot --- why would you
> want to regenerate it?
> 
> If there is some *really* good reason to regenerate it, why does only
> the latest initrd need regenerating? Shouldn't they all? And doesn't
> the admin need to be prompted, in case he needs to copy the image to a
> floppy, burn it to a CD, etc.?

I believe udev cintained within ramdisk needs to match udev outside -
so if udev on the system is updated then (all!) initramfs-based ramdisks
needs to be regenerated in order to survive _next_ boot.

That is a fundamental challenge to using udev in initial ramdisks. Not
because of udev itself, but because of its lack of backwards
compatibility (which can be a plus, as it means less ugly workarounds to
fight with kernel maintainers about).


> >   If using lilo, the system becomes then unbootable 
> >   due to lilo needing to get rerun in order to ack the changed
> > initrd.
> 
> Yep. It'd be nice if Debian had some way to handle
> adding/removing/changing kernels for all bootloaders... I imagine
> similar problems arise on other platforms, too.

Something like kernel-install-helper[1] perhaps?


 - Jonas

[1] http://wiki.debian.org/FlexibleKernelHandling

-- 
* 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: pgp3v2Jf1mJcw.pgp
Description: PGP signature


Reply to: