From: Andries.Brouwer@cwi.nl
To: Andries.Brouwer@cwi.nl, aaronl@vitelus.com
Cc: andrewm@uow.edu.au, bcrl@redhat.com, clausen@gnu.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
torvalds@transmeta.com, viro@math.psu.edu
Subject: Re: [RFD w/info-PATCH] device arguments from lookup, partion code inuserspace
Date: Sat, 19 May 2001 20:05:02 +0200 (MET DST) [thread overview]
Message-ID: <UTC200105191805.UAA51010.aeb@vlet.cwi.nl> (raw)
> initrd is an unnecessary pain in the ass for most people.
> It had better not become mandatory.
You would not notice the difference, only your kernel would be
a bit smaller and the RRPART ioctl disappears.
[Besides: we have lived with DOS-type partition tables for ten years,
but they will not last another ten years. Very soon disk partitions
will look very different. It will be good to move knowledge about
these things out of the kernel before this happens.]
Andries
next reply other threads:[~2001-05-19 18:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-19 18:05 Andries.Brouwer [this message]
2001-05-19 18:07 ` [RFD w/info-PATCH] device arguments from lookup, partion code inuserspace Aaron Lehmann
2001-05-19 19:50 ` Brad Boyer
2001-05-19 19:37 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2001-05-19 19:17 Andries.Brouwer
2001-05-19 11:30 Andries.Brouwer
2001-05-19 17:50 ` Aaron Lehmann
2001-05-19 18:43 ` Richard Gooch
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=UTC200105191805.UAA51010.aeb@vlet.cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=aaronl@vitelus.com \
--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