From: Rob Landley <rob@landley.net>
To: Felix Oxley <lkml@oxley.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] Kconfig help text for RAM Disk & initrd
Date: Mon, 17 Oct 2005 16:32:02 -0500 [thread overview]
Message-ID: <200510171632.02436.rob@landley.net> (raw)
In-Reply-To: <200510171344.18416.lkml@oxley.org>
On Monday 17 October 2005 07:44, Felix Oxley wrote:
> On Monday 17 October 2005 08:33, Rob Landley wrote:
> > > On Monday 17 October 2005 06:37, Rob Landley wrote:
> > > > Actually if this is a patch against 2.6, between ramfs (including
> > > > initramfs) and the ability to loopback mount files, I personally
> > > > consider ramdisks semi-obsolete. (This might be _why_ it says most
> > > > normal users won't need them.)
>
> You are right in all you say.
> However, my system uses initrd and I thought that a help message warning
> newbies that these options are required if inrd is used, would be useful.
> Since I removed it and was uanble to boot :-)
Understandable concern.
> Do you think the slimmed down patch below is appropriate, or shall I just
> drop the subject?
Well, it's better. The first part's a clear correction.
When you note that some systems need it to build, I'd mention that newer
systems should probably be using initramfs. Other than that, no objection.
Rob
prev parent reply other threads:[~2005-10-18 1:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-17 0:02 [PATCH 1/1] Kconfig help text for RAM Disk & initrd Felix Oxley
2005-10-17 5:37 ` Rob Landley
2005-10-17 7:12 ` Felix Oxley
2005-10-17 7:33 ` Rob Landley
2005-10-17 12:44 ` Felix Oxley
2005-10-17 21:32 ` Rob Landley [this message]
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=200510171632.02436.rob@landley.net \
--to=rob@landley.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@oxley.org \
/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