From: Dave Jones <davej@redhat.com>
To: Tom Horsley <tom.horsley@ccur.com>
Cc: 7eggert@gmx.de, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] documentation: Documentation/initrd.txt
Date: Thu, 27 Jul 2006 13:29:44 -0400 [thread overview]
Message-ID: <20060727172944.GJ5687@redhat.com> (raw)
In-Reply-To: <1154020546.5166.35.camel@tweety>
On Thu, Jul 27, 2006 at 01:15:46PM -0400, Tom Horsley wrote:
> On Thu, 2006-07-27 at 19:08 +0200, Bodo Eggert 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:
>
> I find it easy to believe my document is wrong, but looking at
> the Documentation/filesystems/ramfs-rootfs-initramfs.txt file
> would never have led me to believe that the initrd.img file
> was related in any way. The ramfs-rootfs-initramfs.txt
> file describes the the archive as being built into the
> kernel, so it needs updating too I guess (and fedora
> should change the name of the initrd files to be
> initramfs files so I'll look for documentation in the right
> place :-).
It's largely kept all the old names for historical reasons.
We *could* rename stuff, but then we'd also have to rename
the mkinitrd package, the scripts that call it, etc etc
for no real gain.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-07-27 17:29 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 ` [PATCH] documentation: Documentation/initrd.txt Bodo Eggert
2006-07-27 17:15 ` Tom Horsley
2006-07-27 17:29 ` Dave Jones [this message]
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=20060727172944.GJ5687@redhat.com \
--to=davej@redhat.com \
--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