public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bodo Eggert <7eggert@elstempel.de>
To: Tom Horsley <tom.horsley@ccur.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] documentation: Documentation/initrd.txt
Date: Thu, 27 Jul 2006 19:08:39 +0200	[thread overview]
Message-ID: <E1G69M4-0001Um-Jg@be1.lrz> (raw)
In-Reply-To: 6DfYt-7zU-49@gated-at.bofh.it

(now CCing the list, too)

Tom Horsley <tom.horsley@ccur.com> wrote:

> 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.

Your documentation is technically wrong, and there is a better explanation:

Signed-Off-By: Bodo Eggert <7eggert@gmx.de>

--- 2.6.17/Documentation/initrd.txt.ori 2006-07-27 18:49:25.000000000 +0200
+++ 2.6.17/Documentation/initrd.txt     2006-07-27 18:58:19.000000000 +0200
@@ -15,6 +15,9 @@ initrd is mainly designed to allow syste
 where the kernel comes up with a minimum set of compiled-in drivers, and
 where additional modules are loaded from initrd.

+initrd has recently been obsoleted by initramfs, which is described in
+Documentation/filesystems/ramfs-rootfs-initramfs.txt.
+
 This document gives a brief overview of the use of initrd. A more detailed
 discussion of the boot process can be found in [1].

-- 
Ich danke GMX dafür, die Verwendung meiner Adressen mittels per SPF
verbreiteten Lügen zu sabotieren.

http://david.woodhou.se/why-not-spf.html

       reply	other threads:[~2006-07-27 17:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6DfYt-7zU-49@gated-at.bofh.it>
2006-07-27 17:08 ` Bodo Eggert [this message]
2006-07-27 17:15   ` [PATCH] documentation: Documentation/initrd.txt Tom Horsley
2006-07-27 17:29     ` Dave Jones
2006-07-27 21:09     ` Bodo Eggert
2007-05-21  1:51 Domenico Andreoli
  -- strict thread matches above, loose matches on Subject: below --
2006-07-27 15:26 Tom Horsley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1G69M4-0001Um-Jg@be1.lrz \
    --to=7eggert@elstempel.de \
    --cc=7eggert@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tom.horsley@ccur.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox