Am 06.03.2010 00:27, schrieb Ihad:
How early? Maybe keeping the ramdisk mounted helps. This way udevadm monitor could write its results do /somewhere. I did that with images having a defined size, creating a container with an ext2 fs and then mount it rw. If it's big enough we can see the results after booting. But I don't know if it works with cpio-archives...
There is no ramdisk. There is just "rootfs". See http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=D ocumentation/filesystems/ramfs-rootfs-initramfs.txt;h=a8273d5fad209b4ab4393 c0667c03b549c83091c;hb=HEAD
Ok, didn't know that. works with ext[23]-images though. They're rw and stay mounted after boot, if you do a pivot_root in initrd.
You can always write a hook that creates a ramdisk, create a filesystem on it, mount it and mount --move it into the real root before switch_root.
But it's not that important. Get some sleep :)
Not yet.