From: Aaron Lehmann <aaronl@vitelus.com>
To: Andries.Brouwer@cwi.nl
Cc: andrewm@uow.edu.au, viro@math.psu.edu, bcrl@redhat.com,
clausen@gnu.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: [RFD w/info-PATCH] device arguments from lookup, partion code inuserspace
Date: Sat, 19 May 2001 10:50:06 -0700 [thread overview]
Message-ID: <20010519105006.B2648@vitelus.com> (raw)
In-Reply-To: <UTC200105191130.NAA53601.aeb@vlet.cwi.nl>
In-Reply-To: <UTC200105191130.NAA53601.aeb@vlet.cwi.nl>; from Andries.Brouwer@cwi.nl on Sat, May 19, 2001 at 01:30:14PM +0200
On Sat, May 19, 2001 at 01:30:14PM +0200, Andries.Brouwer@cwi.nl wrote:
> I don't think so. It is necessary, and it is good.
>
> But it is easy to make the transition painless.
> Instead of the current choice between INITRD (yes/no)
> we have INITRD (default built-in / external).
> The built-in version can then slowly become smaller and die.
initrd is an unnecessary pain in the ass for most people. It had
better not become mandatory.
next prev parent reply other threads:[~2001-05-19 17:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-19 11:30 [RFD w/info-PATCH] device arguments from lookup, partion code inuserspace Andries.Brouwer
2001-05-19 17:50 ` Aaron Lehmann [this message]
2001-05-19 18:43 ` Richard Gooch
-- strict thread matches above, loose matches on Subject: below --
2001-05-19 19:17 Andries.Brouwer
2001-05-19 18:05 Andries.Brouwer
2001-05-19 18:07 ` Aaron Lehmann
2001-05-19 19:50 ` Brad Boyer
2001-05-19 19:37 ` Linus Torvalds
2001-05-19 6:23 [RFD w/info-PATCH] device arguments from lookup, partion code in userspace Ben LaHaise
2001-05-19 6:57 ` [RFD w/info-PATCH] device arguments from lookup, partion code inuserspace Andrew Clausen
2001-05-19 7:04 ` Alexander Viro
2001-05-19 7:23 ` Andrew Clausen
2001-05-19 8:30 ` Alexander Viro
2001-05-19 10:13 ` Andrew Clausen
2001-05-19 9:11 ` Andrew Morton
2001-05-19 9:20 ` Alexander Viro
2001-05-19 7:58 ` Ben LaHaise
2001-05-19 8:10 ` Alexander Viro
2001-05-19 8:16 ` Ben LaHaise
2001-05-19 8:32 ` Alexander Viro
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=20010519105006.B2648@vitelus.com \
--to=aaronl@vitelus.com \
--cc=Andries.Brouwer@cwi.nl \
--cc=andrewm@uow.edu.au \
--cc=bcrl@redhat.com \
--cc=clausen@gnu.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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