LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jon Masters <jonathan@jonmasters.org>
To: Alan <alan@lxorguk.ukuu.org.uk>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
	David Schwartz <davids@webmaster.com>,
	"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Ban module license tag string termination trick
Date: Sat, 03 Feb 2007 18:32:17 -0500	[thread overview]
Message-ID: <45C51B81.5040309@jonmasters.org> (raw)
In-Reply-To: <20070203222141.6f723fd9@localhost.localdomain>

Alan wrote:
> On Sat, 3 Feb 2007 21:47:36 +0100 (MET)
> Jan Engelhardt <jengelh@linux01.gwdg.de> wrote:
> 
>> On Feb 3 2007 10:31, David Schwartz wrote:
>>> The way out of the GPL problem is to make clear that it is *not* a 
>>> copyright enforcement scheme
>> So why do we have EXPORT_SYMBOL_GPL then, if
> 
> Because if you go around modifying code to get around it then regardless
> of the DMCA question you are actively doing it and there is very clear
> intent to do other than the right holder intended. In some ways its the
> difference between walking through an open archway into a private area
> and kicking the door down to get in.

It's a sign, a notice, and the reason I brought up this discussion is 
precisely because I don't think the kernel has any business being an 
enforcement mechanism - that's not what the spirit of our community is 
really about, we're about openness (as much as is possible).

If I go into an airport, open my laptop and connect to a network called 
"Free WiFi network", then I might have a good case to argue that I 
expected the WiFi to be free. If I connect to a network called "Not 
Free, Don't Use" then...I think the intent of the wording is clear.

Anyway. Are we doing this or not - the more I think about it, the more 
I'm kinda "happy" to just leave things as they are. Yes, bad people will 
continuing doing bad things no matter what we do. Do we really want to 
change stuff just to work around obvious abuse? Alan?

Jon.

  reply	other threads:[~2007-02-03 23:33 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
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 [this message]
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=45C51B81.5040309@jonmasters.org \
    --to=jonathan@jonmasters.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davids@webmaster.com \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.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).