-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Martin wrote: > /usr/sbin/mkinitrd works on my system while yaird doesn't. > kernel-package should take into account whether yaird actually > supports the system before choosing it.
Manoj responded: > It would be very difficult for kerel-package to determine > which initrd tool can or can not handle the local system > configuration. I agree that this is a bug with yaird (and initramfs-tools, but since yaird is currently first choice and there's no meta-package to hang this on, let's stick to yaird for now). I see two possible solutions: 1) yaird supports everything mkinitrd-tools did 2) yaird, k-p and kernels negotiate better what is required For 1) we need documented what mkinitrd-tools actually supported. Let's expand wiki.debian.org/InitrdReplacementOptions with mkinitrd-tools... For 2) see draft at http://wiki.debian.org/FlexibleKernelHandling Ideally both should be met, off course :-) - 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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDZnUpn7DbMsAkQLgRAr2CAKCespf7Dm/pihOdZ5+84U2RWSaXKwCgmJQJ NNqQsTuMcsMy2lxJWOvo4CE= =1tL+ -----END PGP SIGNATURE-----
