From: "David Schwartz" <davids@webmaster.com>
To: "Jamie Lokier" <jamie@shareable.org>,
"Eric W. Biederman" <ebiederm@xmission.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: Using GPL'd Linux drivers with non-GPL, binary-only kernel
Date: Tue, 6 May 2003 15:21:35 -0700 [thread overview]
Message-ID: <MDEHLPKNGKAHNMBLJOLKMEHHCMAA.davids@webmaster.com> (raw)
In-Reply-To: <20030506215552.GA6284@mail.jlokier.co.uk>
> If you build a kernel to run Linux drivers that seems to scream
> derivative work to me.
Then WINE is a derivative work of Windows. Then any product designed to use
AA batteries is a derivative work of the AA battery design.
If you want to say that if you design X to be compatible with Y, then X is
a derivative work of Y, you can do it. But that's not the kind of world I
want to live in.
It's not the world the GPL talks about:
The "Program", below, refers to any such program or work, and a "work based
on the Program"
means either the Program or any derivative work under copyright law: that is
to say, a work containing the Program or a portion of it, either verbatim or
with modifications and/or translated into another language.
You would pretty much have to argue that these were derivative works not of
the kernel or of Windows itself, but of the APIs. In other words, Windows is
a derivative work of the Windows API, as is WINE. Linux is a derivative work
of the Linux kernel API, as is any module that uses this API.
The only problem with this argument is that it results in the type of world
you don't want to live in. You are not suppose to be able to use copyright
to prohibit compatability.
DS
next prev parent reply other threads:[~2003-05-06 22:09 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-06 16:42 Jamie Lokier
2003-05-06 17:35 ` Alan Cox
2003-05-06 18:54 ` Jamie Lokier
2003-05-06 19:28 ` Jean-Marc Lienher
2003-05-06 19:53 ` Alan Cox
2003-05-06 22:31 ` Jamie Lokier
2003-05-06 21:38 ` Alan Cox
2003-05-08 21:36 ` Pavel Machek
2003-05-06 19:17 ` Eric W. Biederman
2003-05-06 21:55 ` Jamie Lokier
2003-05-06 22:21 ` David Schwartz [this message]
2003-05-07 8:21 ` Eric W. Biederman
2003-05-07 14:25 ` Valdis.Kletnieks
2003-05-07 14:31 ` Jamie Lokier
2003-05-07 15:50 ` Eric W. Biederman
2003-05-06 20:43 ` Pavel Machek
2003-05-06 22:18 ` Jamie Lokier
2003-05-06 21:31 ` Alan Cox
2003-05-06 22:48 ` Jamie Lokier
2003-05-07 12:20 ` Alan Cox
2003-05-07 14:26 ` Jamie Lokier
2003-05-07 15:18 ` Pavel Machek
2003-05-08 11:11 ` Krzysztof Halasa
[not found] <20030506165014$3d57@gated-at.bofh.it>
[not found] ` <20030506193019$0d29@gated-at.bofh.it>
[not found] ` <20030506220018$5b96@gated-at.bofh.it>
2003-05-07 1:17 ` Tony 'Nicoya' Mantler
[not found] <BKEGKPICNAKILKJKMHCAAEBCCLAA.Riley@Williams.Name>
2003-05-07 16:57 ` Eric W. Biederman
2003-05-09 1:23 Jean Tourrilhes
2003-05-13 9:08 Dean McEwan
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=MDEHLPKNGKAHNMBLJOLKMEHHCMAA.davids@webmaster.com \
--to=davids@webmaster.com \
--cc=ebiederm@xmission.com \
--cc=jamie@shareable.org \
--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
Powered by JetHome