The patch titled documentation: Documentation/initrd.txt has been added to the -mm tree. Its filename is documentation-documentation-initrdtxt.patch See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find out what to do about this ------------------------------------------------------ Subject: documentation: Documentation/initrd.txt From: Thomas Horsley <tom.horsley@xxxxxxxx> I spent a long time the other day trying to examine an initrd image on a fedora core 5 system because the initrd.txt file is apparently obsolete. Here is a patch which I hope will reduce future confusion for others. Signed-off-by: Thomas Horsley <tom.horsley@xxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxx> --- Documentation/initrd.txt | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff -puN Documentation/initrd.txt~documentation-documentation-initrdtxt Documentation/initrd.txt --- a/Documentation/initrd.txt~documentation-documentation-initrdtxt +++ a/Documentation/initrd.txt @@ -72,6 +72,22 @@ initrd adds the following new options: initrd is mounted as root, and the normal boot procedure is followed, with the RAM disk still mounted as root. +Compressed cpio images +---------------------- + +Recent kernels have support for populating a ramdisk from a compressed cpio +archive, on such systems, the creation of a ramdisk image doesn't need to +involve special block devices or loopbacks, you merely create a directory on +disk with the desired initrd content, cd to that directory, and run (as an +example): + +find . | cpio --quiet -c -o | gzip -9 -n > /boot/imagefile.img + +Examining the contents of an existing image file is just as simple: + +mkdir /tmp/imagefile +cd /tmp/imagefile +gzip -cd /boot/imagefile.img | cpio -imd --quiet Installation ------------ _ Patches currently in -mm which might be from tom.horsley@xxxxxxxx are documentation-documentation-initrdtxt.patch - To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html