From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: "Richard B. Johnson" <root@chaos.analogic.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Probable module bug in linux-2.6.5-1.358
Date: Thu, 07 Oct 2004 19:59:58 +0100 [thread overview]
Message-ID: <1097175596.31547.111.camel@localhost.localdomain> (raw)
In-Reply-To: <1097175903.29576.12.camel@localhost.localdomain>
On Iau, 2004-10-07 at 20:05, Stephen Hemminger wrote:
> --------------
> /*
> * Since some in the Linux-kernel development group want to play
> * lawyer, and require that a GPL License exist for every kernel
> * module, I provide the following:
> *
> * Everything in this file (only) is released under the so-called
> * GNU Public License, incorporated herein by reference.
> *
> * Now, we just link this with any proprietary code and everybody
> * but the lawyers are happy.
> */
What a fascinating object. I hope thats not reflective of OSDL policy 8)
Is fascinating because my first thought was that if they sign the Induce
act it would be a criminal offence to have it in the USA since its
clearly an incitement and my second thought was that the Bernstein case
appears to argue its protected speech. Interesting times 8)
More seriously the goal of MODULE_LICENSE has never been to -enforce-
GPL licensing. It provides help in understanding what symbols are
definitely off limits and it allows people to identify proprietary stuff
loaded into a system to filter bug reports.
The law on derivative works and copyright in general, murkly alas as it
is, does the enforcing, and unfortunately it is becoming apparent that
the free software world is going to have to go out soon and crack down
hard on abusers, especially those simply shipping Linux binaries with no
source or GPL information.
Alan
next prev parent reply other threads:[~2004-10-07 20:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-06 22:08 Probable module bug in linux-2.6.5-1.358 Richard B. Johnson
2004-10-06 23:20 ` Stephen Hemminger
2004-10-06 22:38 ` Alan Cox
2004-10-06 23:22 ` Stephen Hemminger
2004-10-07 11:50 ` Richard B. Johnson
2004-10-07 9:59 ` Arjan van de Ven
[not found] ` <Pine.LNX.4.61.0410070753060.9988@chaos.analogic.com>
2004-10-07 12:17 ` Arjan van de Ven
2004-10-07 12:26 ` Richard B. Johnson
2004-10-07 12:28 ` Arjan van de Ven
2004-10-07 12:34 ` Richard B. Johnson
2004-10-07 12:57 ` Richard B. Johnson
2004-10-07 17:25 ` Stephen Hemminger
2004-10-07 18:25 ` Richard B. Johnson
2004-10-07 19:05 ` Stephen Hemminger
2004-10-07 18:59 ` Alan Cox [this message]
2004-10-07 20:27 ` Stephen Hemminger
2004-10-07 20:48 ` Richard B. Johnson
2004-10-07 21:35 ` Valdis.Kletnieks
2004-10-07 22:09 ` Stephen Hemminger
2004-10-07 19:12 ` Richard B. Johnson
2004-10-07 19:27 ` Richard B. Johnson
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=1097175596.31547.111.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
--cc=shemminger@osdl.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