On Tue, Aug 30, 2005 at 02:40:01AM +0200, Marco Amadori wrote: > > From: Sven Luther <[EMAIL PROTECTED]> > > On Mon, Aug 29, 2005 at 12:22:08PM +0200, Bastian Blank wrote: > > > > > > - initrd-tools needs to loose devfs usage. > > > > BTW, isn't it time to switch to initramfs ? > > > Does it work? > > > Supposedly, best time now to find out, don't you think ? > > I saw that ubuntu use "initramfs-tools" and in debian we have "yaird" that I > personally use since it hit sid to boot from lvm on a md array. > > The superficial differences between the two tools are that initramfs checks > for hardware at boot time and yaird at run time, so initramfs-tools promits > to change the underlying hardware and boot equally well. > > Look at the bts if you want to try yaird, if you have to boot using mdadm, it > needs a little patch to work with sid tools.
My personal believe is that something like yaird will produce smaller intram filesystems, and thus better suited to arches and subarches who have actually trouble with bigger bloated initrds. I am also a bit curious how initramfs behaves on the kernel wise, i mean i understand and all that it is just a bunch of cpio archives which are copied at the end of the kernel, but, taking the powerpc case for an example, there is either a bootwrapper, like the arch/ppc/boot/openfirmware stuff, or boot loaders, like yaboot, who know how to put the kernel and initrd in ram, and then pass the right info to the kernel to find the ramdisk back (passed as argument in r3/r4 if i remember well. Now, initramfs is nothing more than a file organisation which is a bit different for the initial ramdisk, or is there more to it, and the above code path, for which i have seen no major change recently, will still work ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
