From: A Guy Called Tyketto <tyketto@wizard.com>
To: Hell.Surfers@cwctv.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: Re: Re: Why is Nvidia given GPL'd code to use in closed source drivers?
Date: Tue, 31 Dec 2002 21:51:45 -0800 [thread overview]
Message-ID: <20030101055145.GA8790@wizard.com> (raw)
In-Reply-To: <0f8e32227050113DTVMAIL7@smtp.cwctv.net>
On Wed, Jan 01, 2003 at 05:30:18AM +0000, Hell.Surfers@cwctv.net wrote:
> They are stealing by changing GPL files, and not giving the source, its
And just how the smeg do you KNOW they're CHANGING these files, aye?
Do you have some super secret K-9 nose that the rest of us don't, and can
tell? Have you reverse engineered the binary to see? Please, enlighten us.
not for personal use so they are DISTRIBUTING it, and INCLUDING IT.
This does not make sense. You're saying they're changing GPL'd files,
though they can use them any way they choose, as long as they notify the
original author of the changes they made. Whether they redistribute the CODE,
is up to them. They chose not to. As long as they have notified those who
wrote the headers, no GPL violation has been made.
BUT they dont give out their DERIVED source.
Once again, there is no clause in the GPL that states they MUST give
out the code. All they need to do is notify the author. Also, They MUST give
out the code, if they've MODIFIED the headers. You'd be stewing and eating
your boots for dinner if NVidia released the code, and you found no headers to
be modified. their code, they can do anything they want. But for the headers,
all they'd need to do for changing their code, is to keep a current version of
the headers from the kernel, and program their C code to their content. Once
again, No. GPL. Violation.
I work with C everyday and when you put in a header file you are including it,
all kernel headers are GPL. I read the license 4 times a day and have
since 1995.
And we don't deal with C at all. The kernel is programmed in COBOL,
ADA, Modula-2, Mumps, and Pick. Hell, I just might port it part of it over to
Logo. Oh damn.. Apple will sue me for that.. Let's port it to C! I'll learn
it, with my trusty Visual C, and Borland C compilers! </sarcasm>
BL.
--
Brad Littlejohn | Email: tyketto@wizard.com
Unix Systems Administrator, | tyketto@ozemail.com.au
Web + NewsMaster, BOFH.. Smeghead! :) | http://www.wizard.com/~tyketto
PGP: 1024D/E319F0BF 6980 AAD6 7329 E9E6 D569 F620 C819 199A E319 F0BF
next prev parent reply other threads:[~2003-01-01 5:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-01 5:30 RE:Re: Re: Why is Nvidia given GPL'd code to use in closed source drivers? Hell.Surfers
2003-01-01 5:51 ` A Guy Called Tyketto [this message]
2003-01-01 7:38 ` Andre Hedrick
-- 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:51 Hell.Surfers
2003-01-01 5:46 ` David Lang
2003-01-01 7:43 ` Andre Hedrick
2003-01-01 5:45 RE:Re: " Hell.Surfers
2003-01-01 5:55 ` 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=20030101055145.GA8790@wizard.com \
--to=tyketto@wizard.com \
--cc=Hell.Surfers@cwctv.net \
--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