mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Rolf Eike Beer <eike-kernel@sf-tec.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: GPLv2 or not GPLv2? (no license bashing)
Date: Thu, 4 Mar 2004 09:11:07 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.53.0403040848530.17622@chaos> (raw)
In-Reply-To: <200403040838.31412.eike-kernel@sf-tec.de>

On Thu, 4 Mar 2004, Rolf Eike Beer wrote:

> Hi all,
>
> just digging a bit in the kernel and found some funny things:
>
> -there is a tag only for "GPL v2" but there are some drivers claiming to be
> v2 and not using this (patch will follow)
> -there are some drivers with the comment ", either version 2 of the License."
> in the header. s/either // ? If so, there are some more files where someone
> should change MODULE_LICENSE("GPL") to "GPL v2".

I don't think anybody, but the original author, can change the
licensing or its symbology. In other words, if there is a
MODULE_LICENSE("ZORK"), that stays until it is changed by
the author that inserted it initially.

In fact, a review of Linux history by a first-year law student
may show that somebody, not the original author, added the
MODULE_LICENSE() macro to a lot of modules that didn't have
any such macro, and thereby assigned some license that did
not previously exist! Such an implied license may not be valid
because the original author of the work did not perform that
assignment.

I think you need to be vigilant and not fall into the RMS trap
where anything that is "found" anywhere, automatically becomes
the property of GPL. It will invalidate the original spirit
and nature of GPL and, likely throw all such works into
the public domain. Caution is necessary, especially now
that there is a Wind River-Red Hat connection, and other such
connections being established in the future. Wind River was
the company that "bought" BSD/OS. I don't know how you do that --

Anyway, be very careful about changing what might have been
the original author's intent.

Cheers,
Dick Johnson
Penguin : Linux version 2.4.24 on an i686 machine (797.90 BogoMips).
            Note 96.31% of all statistics are fiction.



  parent reply	other threads:[~2004-03-04 14:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-04  7:38 Rolf Eike Beer
2004-03-04  7:44 ` [PATCH] Change "GPL" to "GPL v2" where files are GPLv2 Rolf Eike Beer
2004-03-04  7:44   ` [PATCH] Add missing "GPL" Rolf Eike Beer
2004-03-04 14:11 ` Richard B. Johnson [this message]
2004-03-09  7:16   ` GPLv2 or not GPLv2? (no license bashing) vda
2004-03-09  9:04     ` Måns Rullgård
2004-03-09  9:53       ` vda
2004-03-09 10:12         ` Måns Rullgård
2004-03-09 16:58       ` Jesse Pollard
2004-03-09 17:26         ` Måns Rullgård
2004-03-09 17:38           ` Jesse Pollard

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=Pine.LNX.4.53.0403040848530.17622@chaos \
    --to=root@chaos.analogic.com \
    --cc=eike-kernel@sf-tec.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®