On Mon, Dec 12, 2005 at 12:24:09PM +0000, Ricardo Ferreira wrote: > > Yup, that works, at least with initramfs-tools, will try going back to yaird > later. Any comments on using one instead of the other?
they are very different. initramfs-tools uses udev, bb and klibc and wants max hardware support yaird like to reimplement work in perl and tries to produce minimal for the use case of copying around your root, pulling out your harddisc from one pc to another initramfs-tools is your friend. the drivers need to generate uevents for udev loading. yaird will boot your exotic archs easier, because no need to port klibc, but you need working perl and modules outside of perl-base. the minimal image has also advantages on broken bootloader size assumptions. initramfs-tools is used by ubuntu's breezy release and will feature dapper. the ease of hooks make it very extensible. yaird has a pretty impressive doc section, anyway there is also a wiki page documenting both: -> http://wiki.debian.org/InitrdReplacementOptions yaird is set as default for 2.6.14 to get good test coverage. when reading this, take into account that i'm current initramfs-tools maintainer and thus my preference is clear. :) enjoy -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
