public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Andre Hedrick <andre@linux-ide.org>
Cc: David Schwartz <davids@webmaster.com>, linux-kernel@vger.kernel.org
Subject: Re: GPL and Nvidia
Date: Thu, 2 Jan 2003 21:14:50 -0800	[thread overview]
Message-ID: <20030103051450.GY9704@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10301021315170.421-100000@master.linux-ide.org>

On Thu, Jan 02, 2003 at 01:26:24PM -0800, Andre Hedrick wrote:
> AH!  A man of reason here!
> It would be nice if "LI" got in the business of issuing license
> subscriptions for binary only modules.  Where the binary vendor must
> register and pay a royality fee.  This fee would be used to support "LI"
> and defend Linux in a court case if needed.
> I personally would gladly pay a reasonable (usual and customary) fee for
> the service and right to sell binary models with out having to pay a
> lawyer to write a "position" and be prepared to sue every snot nose brat
> in the world.
> Otherwise, one has to deal with unreasonable people.
> There are people who do not work for distros or have found that other
> companies want to control their contributions to GPL, but need a means to
> support themselves with there other works related to emerging
> technologies.
> Obviously I am being way to sensible about the issue, and should go use
> NetBSD instead and give them the license money.

I don't give two hoots about the money or the open/closed stuff in the
context of "Is it the right thing to do?" or "What should nvidia do?"
nvidia's drivers have developed a bad reputation, at least in my mind,
and I don't want their bugreports (even though RH was hurt worst here),
and I don't want my betatesters adding that unknown into the equation.

Supposedly they've improved lately, not that I care. One only need be
bitten once.

Maybe having no way to prove a bug's fixed is a downside of binary modules.


Bill

  reply	other threads:[~2003-01-03  5:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-01  4:37 GPL and Nvidia Hell.Surfers
2003-01-01  7:17 ` Andre Hedrick
2003-01-01 16:44   ` Dan Egli
2003-01-02  0:33     ` Paul Jakma
2003-01-02 11:19       ` Andrew Walrond
2003-01-02 17:21         ` Gerhard Mack
2003-01-02 20:48           ` David Schwartz
2003-01-02 21:26             ` Andre Hedrick
2003-01-03  5:14               ` William Lee Irwin III [this message]
2003-01-03  9:17             ` Helge Hafting
2003-01-02 21:33         ` Bill Davidsen
2003-01-02 21:56           ` Andre Hedrick
2003-01-02 21:46         ` Jon Portnoy
2003-01-02 22:39           ` Andrew Walrond
2003-01-02 23:40             ` Jon Portnoy
2003-01-01 16:35 ` Rik van Riel
  -- strict thread matches above, loose matches on Subject: below --
2003-01-01 18:05 Hell.Surfers
2003-01-02 21:44 ` Bill Davidsen

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=20030103051450.GY9704@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=andre@linux-ide.org \
    --cc=davids@webmaster.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