Re: In preparation for 2.6.13 - initrd issues
-----BEGIN PGP SIGNED MESSAGE-----
On Mon, 12 Sep 2005 19:52:28 -0700 (PDT)
Jurij Smakov <firstname.lastname@example.org> wrote:
> One thing which I am not too comfortable with yet, is how we are going to
> switch to an alternative initrd generator in the kernel deb postinsts.
> The command to generate initrd is currently configurable in
> /etc/kernel-img.conf, which is owned by kernel-package, so the actual
> kernel packages cannot easily fiddle with it. A suggestion by Jonas
> for yaird to provide mkinitrd script and conflict with initrd-tools is not
> too good either, as people might want to have 2.6.12 and 2.6.13 installed
> at the same time. Anybody has any thoughts on that?
I agree, now that I think more about it. I would be really pissed myself if a new kernel indirectly forced removal of mkinitrd still used for my older kernels.
Currently I believe the postinst code of all official kernels look into /etc/kernel-img.conf for ramdisk script, with fallback to mkinitrd.
How about simply changing the fallback for newer kernels to mkinitrd.yaird, and invoke a warning if ramdisk is defined in kernel-img.conf but to something not on an internal list of known initramfs-capable scripts (currently initramfs and mkinitrd.yaird)?
Should I keep cross-posting, or which of the lists is most relevant for me to subscribe and for all of us to continue this thread?
* Jonas Smedegaard - idealist og Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
- Enden er nær: http://www.shibumi.org/eoti.htm
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
-----END PGP SIGNATURE-----