From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Richard Gooch <rgooch@ras.ucalgary.ca>,
Jonathan Lundell <jlundell@pobox.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] adding PCI bus information to SCSI layer
Date: Wed, 2 May 2001 17:03:03 +0200 [thread overview]
Message-ID: <20010502170303.M706@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <200105011653.f41Grwm12595@vindaloo.ras.ucalgary.ca> <E14ugpA-0002J3-00@the-village.bc.nu>
In-Reply-To: <E14ugpA-0002J3-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Tue, May 01, 2001 at 09:32:41PM +0100
On Tue, May 01, 2001 at 09:32:41PM +0100, Alan Cox wrote:
> Having thought over the issues I plan to maintain a 32bit dev_t kernel with
> conventional mknod behaviour, even if Linus won't. One very interesting item
> that Peter Anvin noted is that its not clear in POSIX that
>
> mknod /dev/ttyF00 c 100 100
>
> open("/dev/ttyF00/speed=9600,clocal");
>
> is illegal. That may be a nice way to get much of the desired
> behaviour without totally breaking compatibility
Ouch!
How is that supposed to work with the dcache?
1. Does POSIX state, that "/" is the directory/entry[1] separator?
2. Can a device node be an directory?
If 1. and not 2., there is no way to implement it like that.
I don't know how people call this, if they call sth. like DevFS
"crappy", but I would be very surprised, if they call it "clean".
Just think of:
test -r /dev/ttyF00/speed=9600,clocal && cat /dev/ttyF00/speed=9600,clocal
Or the equivalent in C in most of the programs, which read sth.
POSIX might not forbid this, because common sense already does ;-)
Regards
Ingo Oeser
[1] entry := directory | file
--
10.+11.03.2001 - 3. Chemnitzer LinuxTag <http://www.tu-chemnitz.de/linux/tag>
<<<<<<<<<<<< been there and had much fun >>>>>>>>>>>>
next prev parent reply other threads:[~2001-05-02 15:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-24 21:02 Matt_Domsch
2001-04-24 21:59 ` Richard Gooch
2001-04-27 4:31 ` Richard Gooch
2001-05-01 1:27 ` Richard Gooch
2001-05-01 8:46 ` Ingo Oeser
2001-05-01 16:53 ` Richard Gooch
2001-05-01 20:32 ` Alan Cox
2001-05-02 15:03 ` Ingo Oeser [this message]
2001-05-02 15:54 ` Alan Cox
2001-05-03 8:57 ` Chris Wedgwood
2001-05-03 9:49 ` Alan Cox
2001-05-03 10:23 ` Chris Wedgwood
2001-04-24 23:16 ` Jonathan Lundell
2001-04-27 5:24 ` Jonathan Lundell
2001-05-01 14:38 ` Jonathan Lundell
2001-05-03 7:32 ` Kai Henningsen
2001-05-03 7:51 ` Jonathan Lundell
2001-05-11 16:32 ` Ralf Baechle
2001-05-11 23:00 ` Steven Willoughby
2001-05-11 22:49 ` Jonathan Lundell
2001-05-12 2:20 ` Ralf Baechle
2001-05-12 4:21 ` Jonathan Lundell
[not found] <p0510030db7221c090810@[10.128.7.49]=FE2>
2001-05-12 11:00 ` Kai Henningsen
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=20010502170303.M706@nightmaster.csn.tu-chemnitz.de \
--to=ingo.oeser@informatik.tu-chemnitz.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jlundell@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rgooch@ras.ucalgary.ca \
/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
all inboxes | Powered by JetHome®