From: Kyle Moffett <mrmacman_g4@mac.com>
To: John Richard Moser <nigelenki@comcast.net>
Cc: Jeff Garzik <jgarzik@pobox.com>, linux-kernel@vger.kernel.org
Subject: Re: When is OSS going to go?
Date: Tue, 18 Oct 2005 15:17:15 -0400 [thread overview]
Message-ID: <7FC9027A-9939-4010-9D23-AD21AA53D7A6@mac.com> (raw)
In-Reply-To: <43554385.6000706@comcast.net>
On Oct 18, 2005, at 14:48:37, John Richard Moser wrote:
> Got a lkml.org link or a subject line I should search for? "OSS
> remove"
> "OSS sound remove" "Open sound system" all return garbage.
http://www.zipworld.com.au/~akpm/linux/patches/stuff/top-posting.txt
http://catb.org/~esr/jargon/html/T/top-post.html
> Jeff Garzik wrote:
>> On Tue, Oct 18, 2005 at 02:01:43PM -0400, John Richard Moser wrote:
>>> 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?
>>
>> Already been discussed; check the archives.
I don't remember if it ever got patched, but linux/Documentation/
feature-removal-schedule.txt should contain a mention of it and
pertinent quotes from the LKML thread.
Cheers,
Kyle Moffett
--
There is no way to make Linux robust with unreliable memory
subsystems, sorry. It would be like trying to make a human more
robust with an unreliable O2 supply. Memory just has to work.
-- Andi Kleen
next prev parent reply other threads:[~2005-10-18 19:17 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 [this message]
2005-10-18 21:50 ` Bill Davidsen
2005-10-19 17:56 ` Nix
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=7FC9027A-9939-4010-9D23-AD21AA53D7A6@mac.com \
--to=mrmacman_g4@mac.com \
--cc=jgarzik@pobox.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
all inboxes | Powered by JetHome®