[arch-general] Problems with mkinitcpio

Thomas Bächler thomas at archlinux.org
Sat Mar 6 00:21:24 CET 2010


Am 06.03.2010 00:15, schrieb Ihad:
>> There is udevadm monitor - we could start that very early and redirect
>> the output into a file inside rootfs. Then, we kill it and look at the
>> file. Not sure if that will work well, haven't tried it.
> 
> 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=Documentation/filesystems/ramfs-rootfs-initramfs.txt;h=a8273d5fad209b4ab4393c0667c03b549c83091c;hb=HEAD

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <http://mailman.archlinux.org/pipermail/arch-general/attachments/20100306/46482d86/attachment.bin>


More information about the arch-general mailing list