From: "David Schwartz" <davids@webmaster.com>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>,
"Stuart MacDonald" <stuartm@connecttech.com>
Cc: <root@chaos.analogic.com>,
"'James Clark'" <jimwclark@ntlworld.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: RE: Driver Model
Date: Wed, 3 Sep 2003 15:41:02 -0700 [thread overview]
Message-ID: <MDEHLPKNGKAHNMBLJOLKKEMAGDAA.davids@webmaster.com> (raw)
In-Reply-To: <1062601073.19058.70.camel@dhcp23.swansea.linux.org.uk>
> On Mer, 2003-09-03 at 15:36, Stuart MacDonald wrote:
> > If the MODULE_LICENSE() macro is what determines taint, what's to
> > prevent a company from compiling their driver in their own kernel tree
> > with that macro and releasing it binary-only? Wouldn't that module
> > then be taint-free?
> They would be representing their module is GPL when its not, obtaining
> services by deceving people (3rd party support) and if they used _GPL
> symbols probably violating the DMCA by bypassing a digital rights
> system.
Holy crap! You've totally pegged my hypocrisy meter.
It is an outright blatant violation of the GPL to build use limitations
into GPL'd works and then use the DMCA to prevent people from removing or
bypassing those limitations.
Next I'm going to add some new features to Linux and my code will check for
a license certificate before it runs. I'll use the DMCA to protect the
license check but I'll distribute the source code just like the GPL requires
me to.
No, the GPL does not require derived works to be GPL'd. No, the GPL does
not allow you to impose additional usage restrictions and use the DMCA to
prohibit people from modifying the code to use it the way they want.
DS
next prev parent reply other threads:[~2003-09-03 22:41 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-02 18:43 James Clark
2003-09-02 19:13 ` Robert Love
2003-09-02 20:44 ` Richard B. Johnson
2003-09-03 14:36 ` Stuart MacDonald
2003-09-03 14:52 ` Jan-Benedict Glaw
2003-09-03 14:57 ` Alan Cox
2003-09-03 15:13 ` Stuart MacDonald
2003-09-03 15:33 ` Mariusz Zielinski
2003-09-03 15:50 ` Stuart MacDonald
2003-09-03 16:02 ` Mariusz Zielinski
2003-09-03 17:58 ` Stuart MacDonald
2003-09-03 16:58 ` Alan Cox
2003-09-03 18:21 ` Jeff Garzik
2003-09-03 15:50 ` Mariusz Zielinski
2003-09-03 22:41 ` David Schwartz [this message]
2003-09-04 11:03 ` Alan Cox
2003-09-03 15:22 ` Richard B. Johnson
2003-09-02 21:29 ` Patrick Mochel
2003-09-02 21:44 ` James Clark
2003-09-02 22:05 ` Greg KH
2003-09-02 22:08 ` Robert Love
2003-09-02 22:39 ` Jamie Lokier
2003-09-02 23:52 ` Andre Hedrick
2003-09-03 0:20 ` David Schwartz
2003-09-03 17:38 ` Andre Hedrick
2003-09-03 18:19 ` Alan Cox
2003-09-03 18:15 ` Andre Hedrick
2003-09-04 12:40 ` Henning P. Schmiedehausen
2003-09-03 13:10 ` Alan Cox
[not found] <rtHg.3n0.9@gated-at.bofh.it>
[not found] ` <rK5y.1xN.25@gated-at.bofh.it>
2003-09-03 18:42 ` Pascal Schmidt
2003-09-03 19:49 ` Andre Hedrick
2003-09-03 22:41 ` David Schwartz
2003-09-03 23:11 ` Pascal Schmidt
2003-09-03 23:33 ` David Schwartz
2003-09-04 1:38 ` Pascal Schmidt
2003-09-04 3:01 ` David Schwartz
2003-09-04 14:21 ` Pascal Schmidt
2003-09-04 1:37 ` Andre Hedrick
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=MDEHLPKNGKAHNMBLJOLKKEMAGDAA.davids@webmaster.com \
--to=davids@webmaster.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jimwclark@ntlworld.com \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
--cc=stuartm@connecttech.com \
/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®