-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 12 Dec 2005 16:31:34 +0100 Maximilian Attems <[EMAIL PROTECTED]> wrote:
> 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 The most interesting feature of yaird for me (being the yaird maintainer) is not perl or minimal images, but that it tries hard to spot problems in the image building proces and fails _before_ rebooting in such cases. Sadly, this current bugreport shows a situation not handled that way. > 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. My comparable scenario for yaird would then be a remote-managed server that you cannot afford (distance, downtime or both) to not reboot with a newer kernel on _same_ hardware setup. When you switch hardware around, you are physically close the the box and can (with a fallback kernel and a capable bootloader like GRUB) roll back to the earlier working kernel+ramdisk. > anyway there is also a wiki page documenting both: > -> http://wiki.debian.org/InitrdReplacementOptions Indeed. Let's both include our different arguments from this thread into that page and point to that instead of repeating ourselves here :-) - 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) iD8DBQFDnakHn7DbMsAkQLgRAhnLAJ99RC02BWfvczdy4pKm9u6fQeHYeACfdYFX bM65b6LvVF2eL9gfHuULF+A= =k16q -----END PGP SIGNATURE-----
