mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David Schwartz" <davids@webmaster.com>
To: "Pascal Schmidt" <der.eremit@email.de>,
	"Andre Hedrick" <andre@linux-ide.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: Driver Model
Date: Wed, 3 Sep 2003 15:41:03 -0700	[thread overview]
Message-ID: <MDEHLPKNGKAHNMBLJOLKMEMAGDAA.davids@webmaster.com> (raw)
In-Reply-To: <E19ucah-0000iH-00@neptune.local>



> On Wed, 03 Sep 2003 20:00:24 +0200, you wrote in linux.kernel:

> > The fact that GPL_ONLY horse sh*t exists means there is a restriction on
> > usage.  So "GPL_ONLY" has in effect violated GPL, by imposing
> > restrictions
> > of usage.

> Where is the restriction? You get the source code, you can roll your
> own and remove the GPL_ONLY stuff. Apart from that I do not recall
> to have seen anything about restrictions of usage in the GPL... the
> only thing it tries to prevent is the source code becoming proprietary.

	If the GPL_ONLY stuff is a license enforcement scheme, the DMCA prohibits
you from removing it. If the GPL_ONLY stuff is not a license enforcement
scheme, nothing prohibits you from stamping your module GPL when it's not.

	However, the GPL (section 2b) prohibits you from imposing any restrictions
other than those in the GPL itself. The GPL contains no restrictions that
apply to mere use and the GPL_ONLY stuff affects use, so it can't be a
license restriction, hence there is no restriction to enforce.

	I don't see anything preventing a GPL'd work from containing code that
imposes restrictions actually contained in the GPL and using the DMCA to
enforce them. But it would have to be a restriction contained in the GPL
itself, and there is no restriction about what code you can use with a GPL'd
work.

	DS



  parent reply	other threads:[~2003-09-03 22:41 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
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-10 14:59               ` People, not GPL [was: Re: Driver Model] Timothy Miller
2003-09-10 20:34                 ` David Schwartz
2003-09-12 19:55                   ` Timothy Miller
2003-09-13 14:18                     ` Geert Uytterhoeven
2003-09-13 17:58                       ` Alan Cox
2003-09-10 23:35                 ` James Clark
2003-09-04  1:37         ` Driver Model Andre Hedrick
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
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

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=MDEHLPKNGKAHNMBLJOLKMEMAGDAA.davids@webmaster.com \
    --to=davids@webmaster.com \
    --cc=andre@linux-ide.org \
    --cc=der.eremit@email.de \
    --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

all inboxes | Powered by JetHome®