a few questions about the entire sequence of how an initramfs image is processed, so i'd just like to clarify the following points, or let me know if they're wrong. 1) whenever you build a new kernel image, it will *always* have an internal cpio-format initramfs image. by default, it will be empty, but it will still be there. 2) actually, after building a new kernel, under usr/, i can find the created file initramfs_data.cpio.gz which contains simply: drwxr-xr-x 2 root root 0 Sep 7 16:14 /dev crw------- 1 root root 5, 1 Sep 7 16:14 /dev/console drwx------ 2 root root 0 Sep 7 16:14 /root is that the actual initramfs that's built by default into the kernel? so it's not truly "empty", but it clearly doesn't contain an "init" script so it doesn't correspond to a "runnable" initramfs. 3) after unloading the internal initramfs in 2), as i read it, the kernel will then look for an external initramfs image in /boot, with the same name as the kernel version, right? so, on my fedora system, what will be loaded next would be (if it exists) initrd-2.6.23-0.164.rc5.fc8.img, given that the kernel i'm booting is 2.6.23-0.164.rc5.fc8. am i correct in assuming that the external compressed initramfs image is located simply by name under /boot, and is added to the current contents of the mounted rootfs? how am i doing so far? rday -- ======================================================================== Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADA http://crashcourse.ca ======================================================================== -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
