From: walt <wa1ter@hotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Why is Nvidia given GPL'd code to use in non-free drivers?
Date: Sun, 05 Jan 2003 13:46:18 -0800 [thread overview]
Message-ID: <3E18A7AA.9020005@hotmail.com> (raw)
In-Reply-To: <fa.ff58bdv.193ou06@ifi.uio.no>
Henning P. Schmiedehausen wrote:
> "Dimitrie O. Paun" writes:
>
>
> > software. For how much money MS has, what have they innovated?
>
> Face it. Microsoft Software is what made the breakthrough to really
> put a powerful machine in every home and allow the 2-5% of the owner
> base which are Linux users to get really cheap commodity hardware.
I think you are correct in this. The dinosaurs had their day --
we all got our DNA from them -- and now they are gone.
next parent reply other threads:[~2003-01-05 21:37 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.glgbuvv.1m1g1he@ifi.uio.no>
[not found] ` <fa.ff58bdv.193ou06@ifi.uio.no>
2003-01-05 21:46 ` walt [this message]
2003-01-07 22:30 ` Why is Nvidia given GPL'd code to use in non-free drivers? Adrian Bunk
2003-01-02 1:37 Why is Nvidia given GPL'd code to use in closed source drivers? Bill Huey
2003-01-02 2:57 ` Paul Jakma
2003-01-02 5:58 ` Bill Huey
2003-01-02 6:14 ` Mark Mielke
2003-01-03 3:32 ` Richard Stallman
2003-01-03 7:51 ` Mark Mielke
2003-01-03 20:30 ` Why is Nvidia given GPL'd code to use in non-free drivers? Richard Stallman
2003-01-03 21:26 ` Larry McVoy
2003-01-03 21:27 ` Dimitrie O. Paun
2003-01-05 21:24 ` Henning P. Schmiedehausen
2003-01-05 22:08 ` Eric Ortega
2003-01-05 22:34 ` Ian Molton
2003-01-05 23:09 ` Henning P. Schmiedehausen
2003-01-04 0:55 ` Shane R. Stixrud
2003-01-04 2:22 ` Larry McVoy
2003-01-04 3:18 ` Shane R. Stixrud
2003-01-04 3:18 ` Matthew D. Pitts
2003-01-04 6:00 ` Werner Almesberger
2003-01-04 7:34 ` Mark Mielke
2003-01-04 7:45 ` Andre Hedrick
2003-01-04 8:36 ` Werner Almesberger
2003-01-04 8:52 ` Shane R. Stixrud
2003-01-04 9:16 ` Mark Mielke
2003-01-04 21:47 ` Roman Zippel
2003-01-05 11:15 ` Eric W. Biederman
2003-01-04 1:19 ` Mark Mielke
2003-01-04 23:44 ` Richard Stallman
2003-01-05 1:32 ` Mark Mielke
2003-01-06 3:25 ` Richard Stallman
2003-01-06 3:25 ` Richard Stallman
2003-01-05 2:22 ` venom
2003-01-05 9:38 ` Geert Uytterhoeven
2003-01-05 21:33 ` Henning P. Schmiedehausen
2003-01-05 22:10 ` Andre Hedrick
2003-01-05 22:22 ` Mark Mielke
2003-01-04 3:10 ` David Schwartz
2003-01-04 23:44 ` Richard Stallman
2003-01-05 0:17 ` David Schwartz
2003-01-05 4:39 ` Wolfgang Walter
2003-01-05 5:35 ` David Schwartz
2003-01-06 16:24 ` Wolfgang Walter
2003-01-06 22:04 ` David Schwartz
2003-01-07 0:08 ` Steven Barnhart
2003-01-07 15:53 ` Georg Nikodym
2003-01-07 18:05 ` Mike Galbraith
2003-01-05 21:46 ` Henning P. Schmiedehausen
2003-01-05 22:06 ` David Schwartz
2003-01-05 21:17 ` Henning P. Schmiedehausen
2003-01-05 22:44 ` Alan Cox
2003-01-05 22:45 ` Henning P. Schmiedehausen
2003-01-05 23:03 ` Xavier Bestel
2003-01-05 23:40 ` Alan Cox
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=3E18A7AA.9020005@hotmail.com \
--to=wa1ter@hotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox