From: Andrew Morton <andrewm@uow.edu.au>
To: Alexander Viro <viro@math.psu.edu>
Cc: Andries.Brouwer@cwi.nl, bcrl@redhat.com, torvalds@transmeta.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFD w/info-PATCH] device arguments from lookup, partion codein userspace
Date: Sat, 19 May 2001 22:06:02 +1000 [thread overview]
Message-ID: <3B0661AA.A2D6933B@uow.edu.au> (raw)
In-Reply-To: <3B065C78.C20BBCA@uow.edu.au> <Pine.GSO.4.21.0105190750380.5339-100000@weyl.math.psu.edu>
Alexander Viro wrote:
>
> It's way past ugly.
I knew you'd like it.
It kind of makes sense, because it puts the two primary stream-of-bytes
objects in Unix into the same namespace, with the same accessors.
So if some random application is expecting a filename well heck, you
just give it a path-to-executable with args. It won't care, although
it may have trouble lseek()ing on it.
It wasn't very serious at all.
-
next prev parent reply other threads:[~2001-05-19 12:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-19 11:09 [RFD w/info-PATCH] device arguments from lookup, partion code in userspace Andries.Brouwer
2001-05-19 11:43 ` Andrew Morton
2001-05-19 12:00 ` Alexander Viro
2001-05-19 12:06 ` Andrew Morton [this message]
2001-05-19 15:56 ` Ben LaHaise
2001-05-19 16:25 ` [RFD w/info-PATCH] device arguments from lookup, partion code Alan Cox
2001-05-19 16:36 ` Alexander Viro
2001-05-19 16:44 ` Matthew Wilcox
2001-05-19 18:01 ` Nicolas Pitre
2001-05-19 18:34 ` Linus Torvalds
2001-05-19 22:34 ` Ingo Oeser
2001-05-19 23:42 ` Alexander Viro
2001-05-20 0:11 ` Alan Cox
2001-05-20 17:10 ` Padraig Brady
2001-05-20 19:53 ` Pavel Machek
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=3B0661AA.A2D6933B@uow.edu.au \
--to=andrewm@uow.edu.au \
--cc=Andries.Brouwer@cwi.nl \
--cc=bcrl@redhat.com \
--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