From: Andrew Morton <andrewm@uow.edu.au>
To: Andries.Brouwer@cwi.nl
Cc: bcrl@redhat.com, torvalds@transmeta.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
viro@math.psu.edu
Subject: Re: [RFD w/info-PATCH] device arguments from lookup, partion code in userspace
Date: Sat, 19 May 2001 21:43:52 +1000 [thread overview]
Message-ID: <3B065C78.C20BBCA@uow.edu.au> (raw)
In-Reply-To: <UTC200105191109.NAA53719.aeb@vlet.cwi.nl>
Andries.Brouwer@cwi.nl wrote:
>
> Hmm. You know that I wrote this long ago?
Well, let's not get too hung up on the disk thing (yeah,
I started it...).
Ben's intent here is to *demonstrate* how argv-style
info can be passed into device nodes. It seems neat,
and nice.
We can also make use of a strong argument parsing library
in the kernel - there are a great number of open-coded
string bashing functions which could be rationalised
and regularised.
So. When am I going to be able to:
open("/bin/ls,-l,/etc/passwd", O_RDONLY);
?
next prev parent reply other threads:[~2001-05-19 11:48 UTC|newest]
Thread overview: 27+ 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 [this message]
2001-05-19 12:00 ` Alexander Viro
2001-05-19 12:06 ` [RFD w/info-PATCH] device arguments from lookup, partion codein userspace Andrew Morton
2001-05-19 15:56 ` [RFD w/info-PATCH] device arguments from lookup, partion code in userspace 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
-- strict thread matches above, loose matches on Subject: below --
2001-05-22 18:45 [RFD w/info-PATCH] device arguments from lookup, partion code in userspace Andries.Brouwer
2001-05-21 12:43 Andries.Brouwer
2001-05-21 16:08 ` Daniel Phillips
2001-05-19 6:23 Ben LaHaise
2001-05-19 9:42 ` Christer Weinigel
2001-05-19 9:51 ` Christer Weinigel
2001-05-19 11:37 ` Eric W. Biederman
2001-05-19 14:25 ` Daniel Phillips
2001-05-21 8:14 ` Lars Marowsky-Bree
2001-05-22 9:07 ` Daniel Phillips
2001-05-19 13:53 ` Daniel Phillips
2001-05-19 18:31 ` Linus Torvalds
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=3B065C78.C20BBCA@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