From: Daniel Jacobowitz <dan@debian.org>
To: Nilmoni Deb <ndeb@ece.cmu.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Monta Vista software license terms
Date: Wed, 5 Feb 2003 12:16:13 -0500 [thread overview]
Message-ID: <20030205171613.GB14909@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.3.96L.1030205115551.1886A-100000@ndeb.net>
[Ooh, another CMU person. Hi.]
Disclaimer: this is not legal advice, and I do not speak for my
employer. I'm also not responsible for policies, so please don't vent
at me or I'll stop trying to be helpful.
On Wed, Feb 05, 2003 at 11:58:23AM +0000, Nilmoni Deb wrote:
>
> This is about Monta Vista Software, a company that develops software for
> embedded platforms, based on the Linux kernel and (possibly) other GPL
> software.
>
> In its official FAQ page, http://www.mvista.com/products/faq.html#q9 , it
> says:
>
> "A: The GNU General Public License (GPL) is very specific about the
> obligations imposed on developers leveraging Open Source. If you
> deploy/redistribute program binaries derived from source code licensed
> under the GPL, you must
>
>
> Supply the source code to derived GPL code or Make an offer (good for 3
> years) to supply the source code
>
> Retain all licensing / header information, copyright notices, etc. in
> those sources
>
> Redistribute the text of the GPL with the binaries and/or source code
>
> Note that your obligation is strictly to the recipients of binaries
> (i.e., your customers). You have no responsibility to the "community" at
> large."
>
>
>
>
>
> Its the last sentence that is of concern. Does this mean no 3rd
> party (who is not a customer) can get the GPL source code part of their
> products ? Seems like a GPL violation of clause 3b in
> http://www.gnu.org/licenses/gpl.html .
I suggest you read clause 3b again:
3. You may copy and distribute the Program (or a work based on it, under Section 2) in object
code or executable form under the terms of Sections 1 and 2 above provided that you also do
one of the following:
* b) Accompany it with a written offer, valid for at least three years, to give any third
party, for a charge no more than your cost of physically performing source distribution,
a complete machine-readable copy of the corresponding source code, to be distributed
under the terms of Sections 1 and 2 above on a medium customarily used for software
interchange; or,
If you don't distribute a binary to someone, then you are under no
obligation to distribute source to them. The GPL's always worked that
way. One can't restrict what one's customers do with the source, but
that doesn't oblige one to give it away.
> In addition:
>
> 1. There is no linux kernel source in ftp://ftp.mvista.com/
Nor any reason it should be there.
> 2. The download page http://www.mvista.com/previewkit/index.html does not
> claim to offer any source code at all.
I'm told that the preview kits do include kernel source, although I
haven't checked for myself in a couple of months.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-02-05 17:06 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-05 11:58 Monta Vista software license terms Nilmoni Deb
2003-02-05 17:04 ` Disconnect
2003-02-05 17:25 ` Christoph Hellwig
2003-02-05 17:10 ` Robert Love
2003-02-05 17:18 ` Nilmoni Deb
2003-02-05 17:23 ` Robert Love
2003-02-05 17:36 ` andrea.glorioso
2003-02-05 17:57 ` Nicolas Pitre
2003-02-05 18:13 ` andrea.glorioso
2003-02-05 18:15 ` Christoph Hellwig
2003-02-05 18:24 ` Steven Dake
2003-02-05 18:28 ` Christoph Hellwig
2003-02-05 19:41 ` Alan Cox
2003-02-05 18:47 ` Christoph Hellwig
2003-02-05 18:52 ` Steven Dake
2003-02-05 18:31 ` Nicolas Pitre
2003-02-05 18:34 ` Christoph Hellwig
2003-02-05 18:41 ` Nicolas Pitre
2003-02-05 18:42 ` Christoph Hellwig
2003-02-05 19:00 ` Nicolas Pitre
2003-02-05 18:51 ` Ben Greear
2003-02-05 18:54 ` Dana Lacoste
2003-02-05 18:56 ` Christoph Hellwig
2003-02-05 19:25 ` Hugo Mills
2003-02-06 8:08 ` Andre Hedrick
2003-02-05 18:44 ` Nilmoni Deb
2003-02-05 17:16 ` Daniel Jacobowitz [this message]
2003-02-05 17:38 ` andrea.glorioso
2003-02-05 17:54 ` Christoph Hellwig
2003-02-05 18:04 ` andrea.glorioso
2003-02-06 1:11 ` jeff millar
2003-02-06 2:19 ` James Buchanan
2003-02-06 9:12 ` Andre Hedrick
2003-02-06 14:37 ` Alan Cox
2003-02-06 18:41 ` Valdis.Kletnieks
2003-02-06 19:14 ` Charles Cazabon
2003-02-06 20:36 ` Andre Hedrick
2003-02-10 7:18 ` Oliver Xymoron
2003-02-10 7:24 ` Christoph Hellwig
2003-02-10 13:24 ` Alan Cox
2003-02-10 17:42 ` Oliver Xymoron
2003-02-10 21:33 ` David Schwartz
2003-02-11 7:42 ` Horst von Brand
2003-02-11 19:39 ` David Schwartz
2003-02-11 20:42 ` Horst von Brand
2003-02-11 22:11 ` David Schwartz
2003-02-12 8:00 ` Horst von Brand
2003-02-12 13:26 ` Mark Hounschell
2003-02-12 15:32 ` Chris Friesen
2003-02-12 20:18 ` David Schwartz
2003-02-13 2:21 ` Jamie Lokier
2003-02-13 2:41 ` David Schwartz
2003-02-13 3:01 ` Jamie Lokier
2003-02-12 3:25 ` Derek Fawcus
2003-02-12 4:13 ` David Schwartz
2003-02-05 18:47 ` Nilmoni Deb
2003-02-05 17:17 ` Christoph Hellwig
2003-02-05 18:17 ` Nicolas Pitre
2003-02-05 18:20 ` Christoph Hellwig
2003-02-05 18:33 ` Nicolas Pitre
2003-02-05 18:40 ` Russell King
2003-02-06 11:31 ` Alex Bennee
2003-02-05 17:28 ` Chris Friesen
2003-02-05 17:31 ` Russell King
2003-02-05 19:15 ` Alan Cox
2003-02-05 19:02 ` Nilmoni Deb
2003-02-05 19:12 ` Daniel Jacobowitz
2003-02-05 21:11 ` Nilmoni Deb
2003-02-06 23:06 ` Bill Davidsen
2003-02-06 23:59 ` Nilmoni Deb
2003-02-09 14:52 ` Bill Davidsen
2003-02-09 16:50 ` Nilmoni Deb
-- strict thread matches above, loose matches on Subject: below --
2003-02-06 19:11 Dan Kegel
2003-02-06 20:38 ` Andre Hedrick
2003-02-07 17:28 ` Dan Kegel
2003-02-11 22:27 Larry McVoy
[not found] <20030212201840.AAA15967%shell.webmaster.com@whenever>
2003-02-12 20:46 ` Valdis.Kletnieks
2003-02-12 21:30 ` David Schwartz
2003-02-12 21:41 ` Derek Fawcus
[not found] <20030212213022.AAA17490%shell.webmaster.com@whenever>
2003-02-12 21:43 ` Valdis.Kletnieks
2003-02-12 22:31 ` David Schwartz
2003-02-12 23:04 ` Daniel Forrest
2003-02-12 23:28 ` David Schwartz
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=20030205171613.GB14909@nevyn.them.org \
--to=dan@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ndeb@ece.cmu.edu \
/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