From 5672a0e4e892c04ec599733498c8dc2ca6fe6db2 Mon Sep 17 00:00:00 2001 From: Thomas Horsley Date: Sun, 30 Jul 2006 03:04:12 -0700 Subject: [PATCH] --- yaml --- r: 32975 b: refs/heads/master c: 0a5eca6530eb4d0120981936058537c24a2f92ce h: refs/heads/master i: 32973: a454384b843c0cc913eeb0fed654941526c9eb9b 32971: f73494247c361b5fe2ad05d47c69a39d124a735a 32967: 1a26d1a38e0eb03596493d15e3d2bc0b7cbf8c94 32959: 659ed8ea9483830ee1dc3f94ab49860133c32b1d v: v3 --- [refs] | 2 +- trunk/Documentation/initrd.txt | 16 ++++++++++++++++ 2 files changed, 17 insertions(+), 1 deletion(-) diff --git a/[refs] b/[refs] index 4a3633c4ccd8..b81a9b678461 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 5a06a363ef48444186f18095ae1b932dddbbfa89 +refs/heads/master: 0a5eca6530eb4d0120981936058537c24a2f92ce diff --git a/trunk/Documentation/initrd.txt b/trunk/Documentation/initrd.txt index b1b6440237a6..15f1b35deb34 100644 --- a/trunk/Documentation/initrd.txt +++ b/trunk/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 ------------