From: Ingo Oeser <ioe@axxeo.de>
To: Al Viro <viro@parcelfarce.linux.theplanet.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problem with ioctl command TCGETS
Date: Fri, 10 Dec 2004 05:01:04 +0100 [thread overview]
Message-ID: <200412100501.04972.ioe@axxeo.de> (raw)
In-Reply-To: <20041128130319.GB26051@parcelfarce.linux.theplanet.co.uk>
You wrote:
[read/write vs ioctl]
> > Tell me how? E.g. how would you set/get sound stream parameters if
> > not with ioctl()?
>
> Have several related files.
Look at your monitor. Technically this is an output device.
But there are little controls, where you can make adjustments.
ioctl is nothing else: A controller for an io-stream.
It also makes quite clear, that we are packetizing read/writes now.
And it cannot be fdopen()ed ;-)
Maybe we COULD split strictly for reads and writes, but
we still need a side channel for that to be opened by
passing a file descriptor.
How else would you control a tty/pty which you got as stdin/stdout?
Maybe one could hack this into xattr-support? ;-)
Regards
Ingo Oeser
next prev parent reply other threads:[~2004-12-10 4:01 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-28 0:22 Problem with ioctl command TCGETS Ozan Eren Bilgen
2004-11-28 0:39 ` Al Viro
2004-11-28 9:59 ` Miklos Szeredi
2004-11-28 10:08 ` Jan Engelhardt
2004-11-28 10:18 ` Miklos Szeredi
2004-11-28 10:28 ` Bernd Eckenfels
2004-11-28 10:56 ` Wichert Akkerman
2004-11-28 11:52 ` Bernd Eckenfels
2004-11-28 11:22 ` Miklos Szeredi
2004-11-28 12:18 ` Al Viro
2004-11-28 12:32 ` Miklos Szeredi
2004-11-28 12:48 ` Al Viro
2004-11-28 12:52 ` Miklos Szeredi
2004-11-28 13:03 ` Al Viro
2004-11-28 14:30 ` Tomas Carnecky
2004-11-28 15:27 ` Al Viro
2004-11-28 18:23 ` Tomas Carnecky
2004-11-28 18:51 ` Miklos Szeredi
2004-12-10 4:01 ` Ingo Oeser [this message]
2004-11-28 13:20 ` Tomas Carnecky
2004-11-28 14:05 ` Al Viro
2004-11-28 13:07 ` Tomas Carnecky
2004-11-28 13:11 ` Al Viro
2004-11-28 13:19 ` Tomas Carnecky
2004-11-28 17:42 ` Alan Cox
2004-11-30 13:26 ` Pavel Machek
2004-11-30 15:46 ` Al Viro
2004-11-28 12:23 ` Bernd Eckenfels
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=200412100501.04972.ioe@axxeo.de \
--to=ioe@axxeo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.