Bug#522909: linux-image-2.6.29-1-amd64: Package cannot be configured due to invalid mkinitrd options
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, Apr 07, 2009 at 01:54:05PM +0200, Frank Blendinger wrote:
>Hi.
>
>On Tue 2009-04-07 13:31, maximilian attems <max@stro.at> proclaimed:
>> On Tue, Apr 07, 2009 at 01:27:45PM +0200, Frank Blendinger wrote:
>> > > post the output of
>> > > cat /etc/kernel-img.conf
>> >
>> > # Kernel image management overrides
>> > # See kernel-img.conf(5) for details
>> > do_symlinks = yes
>> > relative_links = yes
>> > do_bootloader = no
>> > do_bootfloppy = no
>> > do_initrd = yes
>> > link_in_boot = no
>> > ramdisk=mkinitrd.yaird mkinitramfs
>>
>> well that is wrong, easiest way is to just scratch that last line.
>
>Indeed. It works fine without that line.
What Max suggests above is to stop favoring yaird, and instead use the
default one (initramfs-tools).
If you have no interest in using a specific ramdisk tool, then I agree
that you can *avoid* this bug by not explicitly using a ramdisk
generator that triggers the bug.
Above config file of yours is not "wrong", however.
...or more precisely it is not wrong to have "yaird" in that line - it
might be wrong to use "mkinitramfs" (use "mkinitramfs-kpkg" instead) but
that is a different issue which does not relate to the currently
discussed bug.
>> longer explanation
>> * yaird doesn't fully implement update-initramfs compat syntax
>> so can no longer install any linux image since 2.6.28
>> #518315
If you read that bugreport you will notice the lack of response from the
kernel team on the questions raised there.
>> (beside beeing not recommended, not distributed in Lenny, buggy
>> in many ways, not developed anymore and thus deprecated)
The package maintainer of initramfs-tools (Max) do not recommend the use
of the alternative ramdisk tool yaird.
Yaird is bugy in *different* ways than initramfs-tools.
Yaird is still developed.
Please do not spread FUD!
>> * mkinitramfs was never the direct wrapper to call
>> previously in lenny you could have had mkinitramfs-kpkg
>> in aboves line.
>> now you want update-initramfs that is the upper layer
>> and the recommended command to generat an initramfs
>> since at least etch.
>
>Thanks for the explanation. Would you recommend purging yaird
>completely then?
I maintain yaird, and I do not recommend purging it. I depend on it for
server installations that need a different degree of reliability than
the default ramdisk generator, initramfs-tools, can provide. I am not
the only user of yaird.
Max obviously has a different opinion, as indicated by his filing
http://bugs.debian.org/457177 blocking it from being released with
Lenny.
>After all, I am wondering how the line ended up in kernel-img.conf at
>all. I never touched it myself (etckeeper helps my unreliable brain
>here), so it has to be generated by some package, but I could not find
>which one it is. Do you happen to know that? Should a bug against that
>package be filed?
Again, it is not a bug to have that line.
Debian-installer at some point favored yaird over initramfs-tools.
Hope that helps,
- Jonas
- --
* Jonas Smedegaard - idealist og Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAknbUvEACgkQn7DbMsAkQLhVWACfWZB91ZwP3rHGbIZ41eD3QpuF
sIoAnRHixJkNqyiTynSbwSMArdOUpdyZ
=DV9B
-----END PGP SIGNATURE-----
Reply to: