From: Al Viro <viro@parcelfarce.linux.theplanet.co.uk>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: ecki-news2004-05@lina.inka.de, linux-kernel@vger.kernel.org
Subject: Re: Problem with ioctl command TCGETS
Date: Sun, 28 Nov 2004 13:03:19 +0000
Message-ID: <20041128130319.GB26051@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <E1CYOXh-0001nn-00@dorka.pomaz.szeredi.hu>
On Sun, Nov 28, 2004 at 01:52:41PM +0100, Miklos Szeredi wrote:
>
> > > > Think read(2)/write(2). We already have several barfbags too many,
> > > > and that includes both ioctl() and setsockopt(). We are stuck with
> > > > them for compatibility reasons, but why the hell would we need yet
> > > > another one?
> > >
> > > You can't replace either ioctl() or setsockopt() with read/write can
> > > you? Both of them set out-of-band information on file descriptors.
> >
> > Out-of-band == should be on a separate channel...
>
> Tell me how? E.g. how would you set/get sound stream parameters if
> not with ioctl()?
Have several related files.
next prev parent reply index
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-28 0:22 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 [this message]
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
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=20041128130319.GB26051@parcelfarce.linux.theplanet.co.uk \
--to=viro@parcelfarce.linux.theplanet.co.uk \
--cc=ecki-news2004-05@lina.inka.de \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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
LKML Archive on lore.kernel.org
Archives are clonable:
git clone --mirror https://lore.kernel.org/lkml/0 lkml/git/0.git
git clone --mirror https://lore.kernel.org/lkml/1 lkml/git/1.git
git clone --mirror https://lore.kernel.org/lkml/2 lkml/git/2.git
git clone --mirror https://lore.kernel.org/lkml/3 lkml/git/3.git
git clone --mirror https://lore.kernel.org/lkml/4 lkml/git/4.git
git clone --mirror https://lore.kernel.org/lkml/5 lkml/git/5.git
git clone --mirror https://lore.kernel.org/lkml/6 lkml/git/6.git
git clone --mirror https://lore.kernel.org/lkml/7 lkml/git/7.git
git clone --mirror https://lore.kernel.org/lkml/8 lkml/git/8.git
git clone --mirror https://lore.kernel.org/lkml/9 lkml/git/9.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 lkml lkml/ https://lore.kernel.org/lkml \
linux-kernel@vger.kernel.org
public-inbox-index lkml
Example config snippet for mirrors
Newsgroup available over NNTP:
nntp://nntp.lore.kernel.org/org.kernel.vger.linux-kernel
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git