All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David Schwartz" <davids@webmaster.com>
To: "Sam Hocevar" <sam@zoy.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: possible GPL violation by Free
Date: Sun, 10 Oct 2004 14:55:36 -0700	[thread overview]
Message-ID: <MDEHLPKNGKAHNMBLJOLKCEFAOOAA.davids@webmaster.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0410101246000.28406-100000@chimarrao.boston.redhat.com>


> On Sun, 10 Oct 2004, Sam Hocevar wrote:

> > > This leaves Free with 2 options:

> >    I know the GPL and I know they don't appear to be doing any of these
> > two things. However it might be hidden in some obscure agreement between
> > Free and the user, renounced upon in such an agreement (which would
> > violate the GPL, like QuakeLives did) or indeed not be there at all. And
> > the only people who can verify this are the Freebox users.

> Even if the Freebox users were to renounce their own
> rights under the GPL, I do not see how they could
> renounce OUR rights for us ...

	The GPL doesn't give any rights to anyone but the people the software is
distributed to. Though the agreement must be enforceable by any third party,
that third party must actually be a recipient of the agreement, either
directly or indirectly.

	So in other words, if you make a custom binary of the Linux kernel and
distribute it to me, then you have to give me an agreement that any third
party can enforce to get the source code. But I don't have to give that
agreement to any third parties if I don't want to.

	The rationale behind this requirement in the GPL is that without it,
redistribution would be difficult. Since the GPL allows the recipients of
the code to further distribute it, they must be also able to distribute the
right to the source code.

	The GPL does not permit you to impose any other restrictions. So you can't
use this as a loophole to escape the requirement of distributing the source
code. A simple way to understand it is this -- wherever the executable can
go, so too must the source go. Wherever the executable can go, so too must
the right to redistribute the executable (and therefore, so to must go the
ability to get the source).

	If you lawfully obtained the executable to anything derived from GPL'd
code, you should be able to obtain the source code. If not, you might or
might not be able to. If you have the executable, and didn't steal it or
something, you should also have either the source code or the right to
easily obtain the source code.

	DS



  reply	other threads:[~2004-10-10 21:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-09 17:58 possible GPL violation by Free Yoshinori K. Okuji
2004-10-09 18:48 ` Jon Masters
2004-10-10  9:12 ` Sam Hocevar
2004-10-10 15:34   ` Rik van Riel
2004-10-10 16:23     ` Sam Hocevar
2004-10-10 16:46       ` Rik van Riel
2004-10-10 21:55         ` David Schwartz [this message]
2004-10-10 10:28 ` Willy Tarreau
2004-10-11  0:59   ` Eric Rannaud
2004-10-11  2:06     ` David Schwartz
2004-10-11  2:24       ` Måns Rullgård
2004-10-11  7:14     ` Colin Leroy
2004-10-11 13:45       ` Eric Rannaud
2004-10-10 19:40 ` Helge Hafting
2004-10-11  0:06 ` Moritz Muehlenhoff
2004-10-11  7:12 Matthieu Castet
2004-10-11 19:39 Glennie Vignarajah
2004-10-11 20:05 ` David Schwartz
2004-11-01 21:33 Pierre

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=MDEHLPKNGKAHNMBLJOLKCEFAOOAA.davids@webmaster.com \
    --to=davids@webmaster.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@zoy.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.