mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: <Hell.Surfers@cwctv.net>
To: davids@webmaster.com, linux-kernel@vger.kernel.org, rms@gnu.org
Subject: RE:Re: Why is Nvidia given GPL'd code to use in closed source drivers?
Date: Wed, 1 Jan 2003 05:51:28 +0000	[thread overview]
Message-ID: <0facf3248050113DTVMAIL7@smtp.cwctv.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 224 bytes --]

You must understand the GNU/LINUX community is being manipulated by NVidia.

Dean. Three ways to kill yourself, and ive been drove in one...

On 	Mon, 30 Dec 2002 22:55:35 -0800 	David Schwartz <davids@webmaster.com> wrote:

[-- Attachment #2: Type: message/rfc822, Size: 3376 bytes --]

From: David Schwartz <davids@webmaster.com>
To: <Hell.Surfers@cwctv.net>, <linux-kernel@vger.kernel.org>, <rms@gnu.org>
Subject: Re: Why is Nvidia given GPL'd code to use in closed source drivers?
Date: Mon, 30 Dec 2002 22:55:35 -0800
Message-ID: <20021231065537.AAA8309@shell.webmaster.com@whenever>


On Tue, 31 Dec 2002 03:57:06 +0000, Hell.Surfers@cwctv.net wrote:

	To respond first to your subject, GPL'd code is given to everyone to do what 
they wish with, subject to certain very specific and narrow limitations.

>Why does the community continue to make pacts with a company that steals
>from its rivals, makes pacts with M$, and refuses to clearly GPL and open
>source its work on drivers,

	What type of "pact" are you talking about?

>there is a clear difference between their use of
>GPL files, and what the GPL says they can do.

	I presume you're talking about the inclusion of GPL'd header files into 
non-GPL'd code that is then distributed without source code? IMO, if the 
header file only includes things like structs and thin macros, that's 
insufficient to consider the compilation a derived work.

	You are welcome to argue for stronger and stronger copyright law enforcement 
and narrower and narrower constructions of fair use and first sale doctrines. 
However, IMO, it would be the stupidest possible thing the open source 
community could ever do.

>You cannot expect embedded
>kernel developers to GPL, if you excuse Nvidia, its a vain hope to grab M$
>users, but in the long run it destroys the community.

	I don't expect anyone to GPL unless they think they get more benefit from 
GPLing than the potential harm done. People GPL code because they want to 
'donate' it to improve the open source movement, community, and code base. 
Attempting to arm twist such donations is worse than foolish. You think the 
open source community should be a bunch of bullies? Convince people open 
source is best, and avoid them if they don't agree.

	DS


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

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

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-01  5:51 Hell.Surfers [this message]
2003-01-01  5:46 ` David Lang
2003-01-01  7:43 ` Andre Hedrick
2003-01-01 16:13   ` Mark Rutherford
2003-01-01 21:34     ` Rik van Riel
2003-01-02  9:57       ` Jos Hulzink
  -- strict thread matches above, loose matches on Subject: below --
2003-01-08 16:26 Hell.Surfers
2003-01-05  6:14 Hell.Surfers
2003-01-02 17:39 Hell.Surfers
2003-01-02  6:25 Hell.Surfers
2003-01-02  6:16 Hell.Surfers
2003-01-02  6:14 Hell.Surfers
2003-01-02  6:04 Hell.Surfers
2003-01-02  5:37 Hell.Surfers
2003-01-02 21:42 ` Rik van Riel
2003-01-02  5:33 Hell.Surfers
2003-01-03 13:02 ` NEURONET
2003-01-01 18:10 Hell.Surfers
2003-01-01  5:45 RE:Re: " Hell.Surfers
2003-01-01  5:55 ` A Guy Called Tyketto
2003-01-01  5:30 Hell.Surfers
2003-01-01  5:51 ` A Guy Called Tyketto
2003-01-01  5:08 Hell.Surfers
2003-01-01  5:01 Hell.Surfers
2003-01-01  1:51 Hell.Surfers

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=0facf3248050113DTVMAIL7@smtp.cwctv.net \
    --to=hell.surfers@cwctv.net \
    --cc=davids@webmaster.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rms@gnu.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

Powered by JetHome