From: Alexander Viro <viro@math.psu.edu>
To: linux-kernel@vger.kernel.org
Subject: Re: no ioctls for serial ports? [was Re: LANANA: To Pending Device Num
Date: Sun, 20 May 2001 10:31:13 -0400 (EDT) [thread overview]
Message-ID: <Pine.GSO.4.21.0105201030550.8940-100000@weyl.math.psu.edu> (raw)
On Sun, 20 May 2001, Tim Jansen wrote:
> That's why I proposed using multi-stream files. With a syscall like
>
> fd2 = open_substream(fd, "somename")
You also have "streams" thay are related to many device nodes at once. Sorry.
> you could have several control streams and also be prepared if you want to
> support multi-stream filesystems like NTFS in the future...
Let's _not_ bring that into this thread, OK?
next reply other threads:[~2001-05-20 14:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-20 14:31 Alexander Viro [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-19 19:43 no ioctls for serial ports? [was Re: LANANA: To Pending Device Number Registrants] Pavel Machek
2001-05-19 19:35 ` Linus Torvalds
[not found] ` <torvalds@transmeta.com>
2001-05-19 19:17 ` Pavel Machek
2001-05-20 9:53 ` no ioctls for serial ports? [was Re: LANANA: To Pending Device Num Kai Henningsen
2001-05-20 13:40 ` Alexander Viro
2001-05-20 14:27 ` Tim Jansen
2001-05-22 5:56 ` 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=Pine.GSO.4.21.0105201030550.8940-100000@weyl.math.psu.edu \
--to=viro@math.psu.edu \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).