From: <Hell.Surfers@cwctv.net>
To: paulj@alphyra.ie, linux-kernel@vger.kernel.org
Subject: RE:Re: Why is Nvidia given GPL'd code to use in closed source drivers?
Date: Thu, 2 Jan 2003 06:14:09 +0000 [thread overview]
Message-ID: <0a50d1410060213DTVMAIL4@smtp.cwctv.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 215 bytes --]
if libc used compatible headers, they would be derivative....
Dean McEwan, If the drugs don't work, [sarcasm] take more...[/sarcasm].
On Thu, 2 Jan 2003 01:29:59 +0000 (GMT) Paul Jakma <paulj@alphyra.ie> wrote:
[-- Attachment #2: Type: message/rfc822, Size: 2597 bytes --]
From: Paul Jakma <paulj@alphyra.ie>
To: David Lang <david.lang@digitalinsight.com>
Cc: Paul Jakma <paul@clubi.ie>, Rik van Riel <riel@conectiva.com.br>, <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: Thu, 2 Jan 2003 01:29:59 +0000 (GMT)
Message-ID: <Pine.LNX.4.44.0301020126060.30005-100000@dunlop.admin.ie.alphyra.com>
On Wed, 1 Jan 2003, David Lang wrote:
> well libc uses the kernel headers and basicly all userspace programs
> use libc so that makes oracle a derivitive work of the kernel??????
libc neednt neccessarily use the kernel headers, it needs to use only
headers that are compatible. Also, though it might use kernel headers,
the headers it provides for other programmes to be compiled against it
are not kernel headers.
further, the kernel's licence explicitely exempts the 'normal system
calls', and kernel headers describing these can quite arguably be
considered to fall within this exemption.
> luckly that's not how things actually work.
unfortunately, its not at all clear.
> David Lang
regards,
--
Paul Jakma Sys Admin Alphyra
paulj@alphyra.ie
Warning: /never/ send email to spam@dishone.st or trap@dishone.st
-
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/
next reply other threads:[~2003-01-02 6:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-02 6:14 Hell.Surfers [this message]
-- 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: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: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=0a50d1410060213DTVMAIL4@smtp.cwctv.net \
--to=hell.surfers@cwctv.net \
--cc=linux-kernel@vger.kernel.org \
--cc=paulj@alphyra.ie \
/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
all inboxes | Powered by JetHome®