public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Hocevar <sam@zoy.org>
To: "Yoshinori K. Okuji" <okuji@gnu.org>,
	linux-kernel@vger.kernel.org, videolan@videolan.org
Subject: Re: possible GPL violation by Free
Date: Sun, 10 Oct 2004 18:23:05 +0200	[thread overview]
Message-ID: <20041010162304.GA12933@zoy.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0410101130190.28406-100000@chimarrao.boston.redhat.com>

On Sun, Oct 10, 2004, Rik van Riel wrote:

> >    To carefully verify this, you need to have a Freebox user ask
> > Free for the Linux source code. No one else is entitled to do it.
> 
> This is some serious misinformation, that needs to be corrected.
> 
> Please take a look at your copy of the GPL, in particular section 3.
> It states that the distributor of the software has 3 options, the
> third one only for non-profit distribution, so not applicable here.
> This leaves Free with 2 options:
> 
> 1) distribute the source together with the binaries, which they
>    do not appear to be doing
> 
> 2) distribute the source with an offer, for ANY 3rd party, to
>    get the source code on request (they don't appear to be doing
>    this either)

   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.

> In addition to this, I find the reasoning that "people rent the
> box, so we don't sell the software" to be very suspicious.  Even
> if the boxes are only rented, the software on them is still being
> distributed!

   As stated in my previous email, I agree with you on this. Renting is
distributing.

-- 
Sam.

  reply	other threads:[~2004-10-10 16:23 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 [this message]
2004-10-10 16:46       ` Rik van Riel
2004-10-10 21:55         ` David Schwartz
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
  -- strict thread matches above, loose matches on Subject: below --
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=20041010162304.GA12933@zoy.org \
    --to=sam@zoy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=okuji@gnu.org \
    --cc=videolan@videolan.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