From: Chris Friesen <chris.friesen@genband.com>
To: Jon Mason <jdmason@kudzu.us>
Cc: Andy Grover <agrover@redhat.com>,
"Nicholas A. Bellinger" <nab@linux-iscsi.org>,
target-devel <target-devel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Marc Fleischmann <mwf@risingtidesystems.com>,
Nicholas Bellinger <nab@risingtidesystems.com>
Subject: Re: scsi target, likely GPL violation
Date: Wed, 07 Nov 2012 19:57:14 -0600 [thread overview]
Message-ID: <509B117A.6070708@genband.com> (raw)
In-Reply-To: <CAPoiz9wzx_NmuA1ty-U28MGiYr7XKCbDn_e0ZLmz=pNDCqwqFw@mail.gmail.com>
On 11/07/2012 07:02 PM, Jon Mason wrote:
> I'm not a lawyer, nor do I play one on TV, but if
> I understand the GPL correctly, RTS only needs to provide the relevant
> source to their customers upon request.
Not quite.
Assuming the GPL applies, and that they have modified the code, then
they must either:
1) include the source with the distributed binary
or
2) include with the binary an offer to provide the source to *any* third
party
Chris
next prev parent reply other threads:[~2012-11-08 1:58 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-07 16:50 scsi target, likely GPL violation Andy Grover
2012-11-08 1:02 ` Jon Mason
2012-11-08 1:57 ` Chris Friesen [this message]
2012-11-08 16:57 ` Andy Grover
2012-11-08 20:05 ` Nicholas A. Bellinger
2012-11-08 20:22 ` Dave Airlie
2012-11-08 21:22 ` Andy Grover
2012-11-09 2:08 ` Nicholas A. Bellinger
2012-11-09 11:03 ` Alan Cox
2012-11-09 19:52 ` Andy Grover
2012-11-09 20:26 ` Alan Cox
2012-11-11 22:13 ` Lawrence Rosen
2012-11-11 22:41 ` Julian Calaby
2012-11-11 23:03 ` Dave Airlie
2012-11-12 14:21 ` Bradley M. Kuhn
2012-11-15 18:21 ` Andy Grover
2012-11-09 23:16 ` Andy Grover
2012-11-10 23:32 ` Bradley M. Kuhn
2012-11-08 16:57 ` Andy Grover
2012-11-11 9:34 ` James Bottomley
2012-11-11 13:05 ` Theodore Ts'o
2012-11-11 15:15 ` Bradley M. Kuhn
2012-11-11 18:22 ` James Bottomley
2012-11-11 18:32 ` Alan Cox
2012-11-14 2:32 ` James Bottomley
2012-11-12 14:08 ` Theodore Ts'o
2012-11-12 14:15 ` Alan Cox
2012-11-12 0:39 ` Douglas Gilbert
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=509B117A.6070708@genband.com \
--to=chris.friesen@genband.com \
--cc=agrover@redhat.com \
--cc=jdmason@kudzu.us \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mwf@risingtidesystems.com \
--cc=nab@linux-iscsi.org \
--cc=nab@risingtidesystems.com \
--cc=target-devel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).