linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Bradford <john@grabjohn.com>
To: linux-kernel@vger.kernel.org
Subject: Additional clauses to GPL in network drivers
Date: Sun, 7 Dec 2003 15:15:46 GMT	[thread overview]
Message-ID: <200312071515.hB7FFkQH000866@81-2-122-30.bradfords.org.uk> (raw)

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.

*Please*, can we resist the temptation to 'play' with licenses in this
way?  I suspect this extra clause was added just to clarify what the
GPL already says, but in doing so, it just confuses matters, and ends
up causing more work.

For example, it brings up a few issues:

1. How is 'operating system' supposed to be defined in this context?

I assume that if it meant just the kernel, it would say 'kernel'.

If you define 'operating system' as including some userspace
utilities, it's going to cause problems, as some common utilities are
not GPL'ed, (the extra clause doesn't say 'GPL-compatible', it
specifically specifies GPL).

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

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).

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.

John.

             reply	other threads:[~2003-12-07 15:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-07 15:15 John Bradford [this message]
2003-12-07 16:15 ` Additional clauses to GPL in network drivers Krzysztof Halasa
2003-12-08  8:32   ` John Bradford
2003-12-08  0:29 ` David Schwartz
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=200312071515.hB7FFkQH000866@81-2-122-30.bradfords.org.uk \
    --to=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).