Re: Problems with mkinitcpio

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



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

Attachment: signature.asc
Description: OpenPGP digital signature


[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux