diff options
| author | Jeff Garzik <jeff@garzik.org> | 2006-08-03 23:20:37 +0200 |
|---|---|---|
| committer | Jeff Garzik <jeff@garzik.org> | 2006-08-03 23:20:37 +0200 |
| commit | 23946a8a980d13af7b84bcf3ce023e0d166ec83f (patch) | |
| tree | 193d2959a7b62b48aaf2236447f1378779e55104 /Documentation/initrd.txt | |
| parent | Merge branch 'master' into upstream (diff) | |
| parent | Merge branch 'upstream-fixes' of git://git.kernel.org/pub/scm/linux/kernel/gi... (diff) | |
| download | linux-23946a8a980d13af7b84bcf3ce023e0d166ec83f.tar.xz linux-23946a8a980d13af7b84bcf3ce023e0d166ec83f.zip | |
Merge branch 'upstream-fixes' into upstream
Diffstat (limited to 'Documentation/initrd.txt')
| -rw-r--r-- | Documentation/initrd.txt | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/Documentation/initrd.txt b/Documentation/initrd.txt index b1b6440237a6..15f1b35deb34 100644 --- a/Documentation/initrd.txt +++ b/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 ------------ |