LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Helge Hafting <helge.hafting@aitel.hist.no>
To: davids@webmaster.com
Cc: sofar@foo-projects.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Ban module license tag string termination trick
Date: Fri, 02 Feb 2007 11:45:32 +0100	[thread overview]
Message-ID: <45C3164C.1050805@aitel.hist.no> (raw)
In-Reply-To: <MDEHLPKNGKAHNMBLJOLKOEBOBFAC.davids@webmaster.com>

David Schwartz wrote:
> In any event, even if you assume it is a copyright enforcement scheme, it is
> not circumvention to remove or disable such a scheme with the permission of
> the copyright holder. Section 2 of the GPL grants just such permission.
>   

The way I see this:
There is a copyright enforcement scheme.  (A simple test for
the word GPL.) Trivial, but still an enforcement scheme.

You are of course allowed to remove the test completely,
as the GPL lets you change the kernel source in any way you wish.

But you are still not allowed to circumvent the scheme as long as
it is in place - in those parts of the world were circumventing is
illegal.

So a vendor using the \0 trick is on very shaky ground. 
He has another option - to patch out the test.  But he
don't want that, for then he have to distribute a kernel,
not only a module.

Helge Hafting

  reply	other threads:[~2007-02-02 10:48 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-28  0:41 [PATCH] Blacklist hsfmodem module Alexey Dobriyan
2006-11-01 11:21 ` Jan Engelhardt
2007-02-01 21:20   ` [PATCH] Ban module license tag string termination trick Jan Engelhardt
2007-02-01 21:28     ` [m-i-t part] " Jan Engelhardt
2007-02-01 21:55     ` [PATCH] " Randy Dunlap
2007-02-01 22:17     ` Jon Masters
2007-02-01 22:30       ` Trent Waddington
2007-02-01 23:34         ` Auke Kok
2007-02-02  8:24           ` David Schwartz
2007-02-02 10:45             ` Helge Hafting [this message]
2007-02-03 18:31               ` David Schwartz
2007-02-03 20:47                 ` Jan Engelhardt
2007-02-03 22:21                   ` Alan
2007-02-03 23:32                     ` Jon Masters
2007-02-04  0:05                       ` Alan
2007-02-04  7:56                   ` David Schwartz
2007-02-07 12:18                 ` Helge Hafting
2007-02-07 18:56                   ` David Schwartz
2007-02-12 15:50                     ` Helge Hafting
2007-02-12 16:42                       ` Alan
2007-02-12 22:37                       ` David Schwartz
2007-02-02  0:17       ` Tomas Carnecky
2007-02-02  0:51         ` Trent Waddington
2007-02-02  2:19           ` Valdis.Kletnieks
2007-02-02  3:12           ` Arjan van de Ven
2007-02-02  6:15             ` Jon Masters
2007-02-02 14:53     ` Paul Rolland
2007-02-02 15:11       ` Jan Engelhardt
2007-02-02 16:53         ` Randy Dunlap
2007-02-02 17:41           ` Jan Engelhardt
2007-02-02 17:49             ` Randy Dunlap
2007-02-02 19:06               ` Jan Engelhardt
2007-02-03  1:12                 ` Randy Dunlap
2007-02-03  1:29                   ` Jan Engelhardt
2007-02-02 18:37         ` Paul Rolland
2007-02-02 19:08           ` Jan Engelhardt
2007-02-04  8:14             ` Paul Rolland

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=45C3164C.1050805@aitel.hist.no \
    --to=helge.hafting@aitel.hist.no \
    --cc=davids@webmaster.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sofar@foo-projects.org \
    --subject='Re: [PATCH] Ban module license tag string termination trick' \
    /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

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