LKML Archive on
help / color / mirror / Atom feed
From: "David Schwartz" <>
To: <>
Cc: <>,
	"Andrew Morton" <>,
	"Ingo Molnar" <>,
	"Arnaldo Carvalho de Melo" <>,
	<>, "Alan Cox" <>
Subject: RE: [PATCH] 2.6.25-rc2-mm1 - fix mcount GPL bogosity.
Date: Tue, 26 Feb 2008 16:28:43 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <m3wsorb6wq.fsf@maximus.localdomain>

> "David Schwartz" <> writes:

> > This is an obviously-wrong argument,

> Even if it's proven wrong in the end, the defendant may at least be
> found acting in a good faith.

If they were in fact acting in good faith, they should be found to have been
acting in good faith. If you think this reasonably might result in
confusion, the solution is better documentation.

> > All you can do in code is implement technical things.

> The GPL itself is the weapon, not the technical measures which can be
> legally trivially disabled (even if the modules are illegal).


> > You cannot enforce or
> > implement the license because the GPL prohibits that.

> Not sure what do you mean. I was under impression that a copyright
> holder can enforce GPL :-)

I mean you can't enforce or implement the license in code because the GPL
specifically permits modification without exclusion. Someone cannot use the
GPL to force you to use code you do not wish to use. The GPL does not
contain any technical enforcement mechanism and would not permit one because
it would be a "further restriction" (it's a restriction, it's not in the
GPL, so it's further).

Perhaps some kind of technical rule that didn't prohibit anything the GPL
allowed might be a legitimate license enforcement scheme, not restricting
anything "further". That's a stretch, but the GPL symbol tagging doesn't
apply since it prohibits non-GPL modules from using those symbols even if
they are not distibuted. This is not a restriction found in the GPL, so it's
a "further restriction". (Which is fine. Not being able to remove any file
as 'root' is a restriction not found in the GPL too. The point is, these are
technical restrictions, not license enforcement mechanisms.)


  reply	other threads:[~2008-02-27  0:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-25 17:59 Valdis.Kletnieks
2008-02-25 18:23 ` Steven Rostedt
2008-02-25 18:19   ` Alan Cox
2008-02-25 19:27     ` Adrian Bunk
2008-02-25 19:48       ` Alan Cox
2008-02-25 20:09         ` Adrian Bunk
2008-02-25 20:38           ` Alan Cox
2008-02-25 21:17       ` Valdis.Kletnieks
2008-02-26  1:30   ` David Schwartz
2008-02-26 12:29     ` Alan Cox
2008-02-26 15:43     ` Krzysztof Halasa
2008-02-26 17:04       ` Krzysztof Halasa
2008-02-26 17:21         ` Alan Cox
2008-02-26 17:44           ` Krzysztof Halasa
2008-02-26 18:04             ` Alan Cox
2008-02-26 18:19       ` David Schwartz
2008-02-26 23:13         ` Krzysztof Halasa
2008-02-26 23:35           ` David Schwartz
2008-02-27  0:05             ` Krzysztof Halasa
2008-02-27  0:28               ` David Schwartz [this message]
2008-02-27 10:31           ` Alan Cox
2008-02-27 10:55             ` Krzysztof Halasa

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \
    --subject='RE: [PATCH] 2.6.25-rc2-mm1 - fix mcount GPL bogosity.' \

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