linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David Schwartz" <davids@webmaster.com>
To: "John Bradford" <john@grabjohn.com>, <linux-kernel@vger.kernel.org>
Subject: RE: Additional clauses to GPL in network drivers
Date: Sun, 7 Dec 2003 16:29:42 -0800	[thread overview]
Message-ID: <MDEHLPKNGKAHNMBLJOLKCEJMIIAA.davids@webmaster.com> (raw)
In-Reply-To: <200312071515.hB7FFkQH000866@81-2-122-30.bradfords.org.uk>


> Many network drivers in the current 2.6 tree include the following
> licensing condition/clarification, in addition to being placed under
> the GPL:
>
> "This file is not a complete program and may only be used when the
> entire operating system is licensed under the GPL".
>
> as
> grep -C 1 "only be used when"
>
> in drivers/net will confirm.

	If this adds any restriction on use that is not part of the GPL, then this
'license' is not compatible with the GPL. If this reflects the author's
understanding of the GPL, then it's grossly incorrect.

> 2. Is code licensed under this extra term actually compatible with
> code placed under the GPL alone?

	Only if the term is meaningless. I suspect that it's legally meaningless
and simply erroneous, but it does create the risk that someone might argue
that it's an additional restriction.

> 3. I haven't tried to trace the history of this code, but if these
> drivers were based on, and include, other developer's purely GPL'ed
> code, applying this extra condition is presumably not valid, (unless
> specific permission was sought to do so).

	Correct. Most likely this is the case, so it reflects license hijacking on
the part of the person who did it. To take someone else's GPL'd code, modify
it, and release the modified code under a license that is more restrictive
than the GPL is despicable conduct.

> 4. The obvious issue concerning binary modules - does loading a binary
> module which is not licensed under the GPL invalidate your license to
> use these network drivers?  Note that I personally have no interest
> whatsoever in using such binary modules, but whatever ends up being
> decided for the GPL'ed parts of the kernel, this extra clause suggests
> to me that it specifically isn't OK whilst using these network
> drivers.

	I think this is just one way of showing that the clause is erroneous.

	DS



  parent reply	other threads:[~2003-12-08  0:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-07 15:15 Additional clauses to GPL in network drivers John Bradford
2003-12-07 16:15 ` Krzysztof Halasa
2003-12-08  8:32   ` John Bradford
2003-12-08  0:29 ` David Schwartz [this message]
2003-12-08  1:00 ` Alex Belits
2003-12-08  2:32 ` David Schwartz
2003-12-08  3:11   ` Jeremy Maitin-Shepard
2003-12-08  3:51     ` David Schwartz
2003-12-08  6:40       ` Shawn Willden
2003-12-08 20:57       ` Matthias Andree
2003-12-07 17:15 Xose Vazquez Perez

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=MDEHLPKNGKAHNMBLJOLKCEJMIIAA.davids@webmaster.com \
    --to=davids@webmaster.com \
    --cc=john@grabjohn.com \
    --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;
as well as URLs for NNTP newsgroup(s).