From: Nix <nix@esperi.org.uk>
To: Bill Davidsen <davidsen@tmr.com>
Cc: John Richard Moser <nigelenki@comcast.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: When is OSS going to go?
Date: Wed, 19 Oct 2005 18:56:30 +0100 [thread overview]
Message-ID: <87mzl5ie5t.fsf@amaterasu.srvr.nix> (raw)
In-Reply-To: <43556E2E.7090102@tmr.com> (Bill Davidsen's message of "18 Oct 2005 22:50:16 +0100")
On 18 Oct 2005, Bill Davidsen suggested tentatively:
> John Richard Moser wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>> The Open Sound System has been depricated. . . since. . . when the heck?
>> 2.4? Is it ever going to drop off? Are there a few cards in OSS that
>> don't work right in ASLA?
>>
> This has been discussed before, but the major argument is that if
> Linux starts dropping functional features there is no longer even a
> pretense of this kernel line being stable.
The dropping of e.g. devfs has already knocked that idea on the head;
functional features are being removed as well as added.
(And as ALSA can emulate the useful parts of OSS, when all OSS cards are
supported by ALSA, there won't be any function loss anyway.)
--
`"Gun-wielding recluse gunned down by local police" isn't the epitaph
I want. I am hoping for "Witnesses reported the sound up to two hundred
kilometers away" or "Last body part finally located".' --- James Nicoll
next prev parent reply other threads:[~2005-10-19 17:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-18 18:01 John Richard Moser
2005-10-18 18:06 ` Jeff Garzik
2005-10-18 18:48 ` John Richard Moser
2005-10-18 19:12 ` Alejandro Bonilla
2005-10-18 19:15 ` Lee Revell
2005-10-18 19:23 ` John Richard Moser
2005-10-18 19:56 ` Brian Gerst
2005-10-18 19:17 ` Kyle Moffett
2005-10-18 21:50 ` Bill Davidsen
2005-10-19 17:56 ` Nix [this message]
2005-10-19 0:43 ` James Courtier-Dutton
2005-10-19 8:31 ` Jules Colding
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=87mzl5ie5t.fsf@amaterasu.srvr.nix \
--to=nix@esperi.org.uk \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nigelenki@comcast.net \
/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
Powered by JetHome