[arch-general] Problems with mkinitcpio

[Ihad]

Hi,

On Saturday 06 March 2010 00:21:24 Thomas Bächler wrote:
> 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=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.

But it's not that important. Get some sleep :)

--
Regards,

Ihad.