public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: Horst von Brand <vonbrand@quelen.inf.utfsm.cl>
Cc: Scott Mansfield <thephantom@mac.com>,
	Bryan Henderson <hbryan@us.ibm.com>,
	Ben Slusky <sluskyb@paranoiacs.org>,
	"Robert W. Fuller" <garbageout@sbcglobal.net>,
	linux-fsdevel@vger.kernel.org,
	LKML Kernel <linux-kernel@vger.kernel.org>,
	Kyle Moffett <mrmacman_g4@mac.com>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: blatant GPL violation of ext2 and reiserfs filesystem drivers
Date: Sat, 24 Dec 2005 03:25:40 +0000	[thread overview]
Message-ID: <20051224032540.GA3698@mail.shareable.org> (raw)
In-Reply-To: <200512240148.jBO1mlqx022718@quelen.inf.utfsm.cl>

Horst von Brand wrote:
> > >>Developer replies that the source code will be provided
> > >>only to paying customers:
> 
> > > Not really.  Developer does make the bizarre statement that "paid
> > > customers" are entitled to source code,
> 
> Read the GPL: You get the binary, you are entitled to the source. You have
> no binary, wellll...
> 
> Sure, you can get the binary (legally!) from somebody else, and then you
> are entitled to source.

If in the last paragraph mean "then you are entitled to the source
[from Developer]", then that is not correct.

You are entitled to the source from the person who gave you the
binary.  You are also only entitled to it in ways enumerated by the
GPL - i.e. at the same time as you receive the binary, or if the
person giving the binary does not provide the source at the same time,
in the form of a 3 year written offer to provide it later from that
person.

If you receive a binary from an intermediate 3rd party, you have no
entitlement to get the source from _their_ supplier.  Only from the
3rd party.

If the 3rd party don't supply you with source, even if _they_ can't
because they don't have it, then _they_ are in breach of the GPL when
they give you the binary.

Of course, the upstream Developer could give you the source anyway.
But they aren't required to do that, if they aren't providing the binary.

All that said, isn't this thread a result of the upstream Developer
(i.e. not a 3rd party) providing binaries for free, and then not
providing source to the people who get those free binaries, despite
saying they will?  That is not on.

-- Jamie

  parent reply	other threads:[~2005-12-24  3:26 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-22 16:08 blatant GPL violation of ext2 and reiserfs filesystem drivers Robert W. Fuller
2005-12-22 18:01 ` Kyle Moffett
2005-12-22 20:27   ` Steven Rostedt
2005-12-22 23:12     ` Jeff V. Merkey
2005-12-23  2:56       ` Chris Wedgwood
2005-12-23  3:15         ` Diego Calleja
2005-12-23  3:28           ` Chris Wedgwood
2005-12-23  3:38             ` Steven Rostedt
2005-12-23  3:49               ` Matthew Wilcox
2005-12-23  4:25               ` Jamie Lokier
2005-12-23  3:30           ` Adrian Bunk
2005-12-23 15:35     ` Ben Slusky
2005-12-23 19:34       ` Bryan Henderson
2005-12-23 20:16         ` Scott Mansfield
2005-12-23 22:00           ` Bryan Henderson
2005-12-24  1:48           ` Horst von Brand
2005-12-24  2:41             ` Peter Williams
2005-12-24  3:25             ` Jamie Lokier [this message]
2006-01-04 11:09       ` Harald Welte
2006-01-04 11:54         ` Jamie Lokier
2006-01-04 13:18           ` Harald Welte
2006-01-04 13:46             ` Matthew Wilcox
2006-01-04 17:46               ` Harald Welte
2006-01-04 23:03               ` Gene Heskett
2006-01-04 22:43                 ` Jeff V. Merkey
2006-01-04 14:16             ` Jamie Lokier
2006-01-04 14:45               ` Matthew Wilcox
2006-01-04 15:57                 ` Jamie Lokier
2006-01-04 17:42                 ` Harald Welte
2006-01-05 17:52                 ` Bryan Henderson

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=20051224032540.GA3698@mail.shareable.org \
    --to=jamie@shareable.org \
    --cc=garbageout@sbcglobal.net \
    --cc=hbryan@us.ibm.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mrmacman_g4@mac.com \
    --cc=rostedt@goodmis.org \
    --cc=sluskyb@paranoiacs.org \
    --cc=thephantom@mac.com \
    --cc=vonbrand@quelen.inf.utfsm.cl \
    /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