From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: root@chaos.analogic.com
Cc: Thomas Sailer <sailer@ife.ee.ethz.ch>,
torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: Poll and OSS API
Date: Thu, 02 Nov 2000 09:35:59 -0500 [thread overview]
Message-ID: <3A017BCF.DAAE9827@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.3.95.1001102091346.8760A-100000@chaos.analogic.com>
"Richard B. Johnson" wrote:
> The specification is bogus and should be fixed. select() is not
> a function that was designed to start/stop anything. Writing
> a specification to qualify some particular implementation's
> side-affects is patently wrong. ioctl() was designed to control
> things.
>
> You should contact a committee member and get it fixed. Further,
> all should fail to write code to such a so-called specification.
>
> If specifications are allowed to be written like this, soon
> the lights will go out when you open a file. This cannot be
> allowed. Don't support such diatribe.
We are stuck with the current OSS API, including warts aplenty, until
ALSA replaces it. (but even then OSS will live on in infamy...)
Jeff
--
Jeff Garzik | Dinner is ready when
Building 1024 | the smoke alarm goes off.
MandrakeSoft | -/usr/games/fortune
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-02 14:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-02 14:03 Poll and OSS API Thomas Sailer
2000-11-02 14:23 ` Richard B. Johnson
2000-11-02 14:27 ` Thomas Sailer
2000-11-02 14:47 ` Richard B. Johnson
2000-11-02 14:35 ` Jeff Garzik [this message]
2000-11-02 14:50 ` Jeff Garzik
2000-11-02 17:38 ` Linus Torvalds
2000-11-02 17:59 ` Alan Cox
2000-11-04 6:18 ` Jeff Garzik
2000-11-04 6:39 ` Linus Torvalds
2000-11-04 7:18 ` Jeff Garzik
2000-11-04 7:26 ` Jeff Garzik
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=3A017BCF.DAAE9827@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
--cc=sailer@ife.ee.ethz.ch \
--cc=torvalds@transmeta.com \
/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.