Bug#336600: I guess yaird should resolve failures early?
ressign 336600 kernel-package
severity 336600 normal
retitle 336600 yaird as default choice a good idea?
thanks
* Sven Luther <sven.luther@wanadoo.fr> [2005-10-31 22:37]:
> maybe we should give each of them its turn of being default to get
> them widely tested and in good shape for the etch
More or less deliberately breaking systems isn't the way to go imho.
I took a brief look at yaird and the README clearly states that it is
experimental software and not a viable replacement for initrd-tools
yet - doesn't sound like a good default choice to me then, even in
unstable.
For reference, this is from yaird's README:
YAIRD -- Yet Another MkInitRd
=============================
This is a proof of concept rewrite of mkinitrd, intended to test the
idea that we can get a more accurate picture of the modules needed
to boot a linux system by fully utilizing the information in sysfs.
It comes with templates that make it possible to generate different
initrd or initramfs images for different distributions.
Proof of concept means this software is barely tested: it may
produce a working image, or it may eat your disk. This is a good
moment to re-read the "NO WARRANTY" part of the licence,
and decide whether you want to test this software.
--
Martin Michlmayr
http://www.cyrius.com/
Reply to: