Bug#336600: I guess yaird should resolve failures early?
On Mon, Oct 31, 2005 at 07:10:18PM +0000, Martin Michlmayr wrote:
> * Manoj Srivastava <srivasta@golden-gryphon.com> [2005-10-31 11:48]:
> > It would be very difficult for kerel-package to determine
> > which initrd tool can or can not handle the local system
> > configuration.
>
> Maybe yaird should not be the default given that it doesn't support
> many of the configurations that initrd-tools does.
Well, at choice time, initramfs-tools failed to build/install/whatever, so
that only yaird was a sane choice, we may change this, but i understand
initramfs-tools has its own problem, and maybe we should give each of them its
turn of being default to get them widely tested and in good shape for the etch
release, which is more than a year off. We decided to have another look at the
decision of which to make default a bit later anyway.
Don't you think now is the best moment to find out about those issues ? Also,
you can always override this default with ramdisk=/usr/sbin/mkinitramfs in
/etc/kernel-img.conf. And you are also welcome to complete the
initrd-tools-replacement wiki (jona, care to provide the link ?).
Friendly,
Sven Luther
Reply to: