From: John Richard Moser <nigelenki@comcast.net>
To: Alejandro Bonilla <abonilla@linuxwireless.org>
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:23:17 -0400 [thread overview]
Message-ID: <43554BA5.8030200@comcast.net> (raw)
In-Reply-To: <20051018191051.M41267@linuxwireless.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Alejandro Bonilla wrote:
> On Tue, 18 Oct 2005 14:48:37 -0400, John Richard Moser wrote
>
>>-----BEGIN PGP SIGNED MESSAGE-----
>>Hash: SHA1
>>
>>Got a lkml.org link or a subject line I should search for? "OSS remove"
>>"OSS sound remove" "Open sound system" all return garbage.
>
>
> Why would you want it to go away? People can decide from which one to use and
> make Linux more flexible.
>
ever growing code base; I want it to go away for the same reason I'd
love a binary driver model in the kernel (in fact I'm looking at getting
fuse to supply the driver for my rootfs from initrd)
> Anyway, I think the archives say something like, it doesn't have to go away,
> so why remove it?
>
> .Alejandro
>
- --
All content of all messages exchanged herein are left in the
Public Domain, unless otherwise explicitly stated.
Creative brains are a valuable, limited resource. They shouldn't be
wasted on re-inventing the wheel when there are so many fascinating
new problems waiting out there.
-- Eric Steven Raymond
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFDVUukhDd4aOud5P8RArBGAJ99rqujkD+9EAS5eWOVLpdztgLuGwCfdpk4
ucd/6eHiqJLiPjjTSTJxkHE=
=bz62
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2005-10-18 19:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-18 18:01 When is OSS going to go? 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 [this message]
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
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=43554BA5.8030200@comcast.net \
--to=nigelenki@comcast.net \
--cc=abonilla@linuxwireless.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
/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.