From 3aa41ff390a80d2e34fa58069344dba9fc297652 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Uwe=20Kleine-K=C3=B6nig?= Date: Sun, 3 Feb 2008 14:54:41 +0200 Subject: [PATCH] --- yaml --- r: 82734 b: refs/heads/master c: a7b1a68b25093753155ea752ff865c9dfcf33d79 h: refs/heads/master v: v3 --- [refs] | 2 +- trunk/Documentation/initrd.txt | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/[refs] b/[refs] index 49b18449494d..55d3ce732755 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 33b1302545d117f368135387c73f78e2a08c7c4b +refs/heads/master: a7b1a68b25093753155ea752ff865c9dfcf33d79 diff --git a/trunk/Documentation/initrd.txt b/trunk/Documentation/initrd.txt index 74f68b35f7c1..1ba84f3584e3 100644 --- a/trunk/Documentation/initrd.txt +++ b/trunk/Documentation/initrd.txt @@ -85,7 +85,7 @@ 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 +find . | cpio --quiet -H newc -o | gzip -9 -n > /boot/imagefile.img Examining the contents of an existing image file is just as simple: