linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "James Buchanan" <jamesbuch@iprimus.com.au>
To: "jeff millar" <wa1hco@adelphia.net>,
	"Christoph Hellwig" <hch@infradead.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Monta Vista software license terms
Date: Thu, 6 Feb 2003 13:19:19 +1100	[thread overview]
Message-ID: <001b01c2cd86$27db7240$59951ad3@windows> (raw)
In-Reply-To: 01c601c2cd7c$be4002a0$6a01a8c0@wa1hco

>     1. Can MontaVista add separate terms to their purchase agreement
that
> forbid/discourage/impede publishing the source?

They can change their licence agreement, but this relates to the
entire licence (e.g. switch from GPL to proprietary licence, but only
if they authored the GPL'd code.)  I am not sure of the difference
between purchase agreement and licence.  Retrospectively
adding/amending an existing licence when it has already been issued
with customers is another thing - it probably depends on what a court
is willing to allow.  As far as I know, there is little to go on when
trying to figure out if something is legal or within their rights or
not as far as software licences go.

One thing is for sure.  The law provides for copyright protection and
no more.  If something is outside the scope of copyright protection
*and there is no contract* (and a licence is *not* a contract) then
those licence agreements are not enforcable at law.  This is why
Microsoft's licences are not enforcable in a court of law (at least in
Australia anyway, I am not sure if they have been tested in court in
America.)

>     2. What if MV mixes GPL and proprietary code in the directories
to make
> it difficult to post the GPL portion?

Then they must honour the GPL licence terms with respect to the GPL'd
code, and it is their responsibility to comply with this.

--
James


----- Original Message -----
From: "jeff millar" <wa1hco@adelphia.net>
To: "Christoph Hellwig" <hch@infradead.org>
Cc: <linux-kernel@vger.kernel.org>
Sent: Thursday, February 06, 2003 12:11 PM
Subject: Re: Monta Vista software license terms


> So...could some kind soul with the source simply post it somewhere?
> MontaVista doesn't have to provide it on their site.  But they can't
prevent
> anyone with a copy from posting it. I've got some hardware from an
old
> project running hardhat linux and would like to upgrade.
>
> They used to post it and it helped. I had a "frank exchange of
views" with
> the MontaVista marketing folks about their change in policy a while
back.
>
> Some questions about posting the source, though...
>     1. Can MontaVista add separate terms to their purchase agreement
that
> forbid/discourage/impede publishing the source?
>     2. What if MV mixes GPL and proprietary code in the directories
to make
> it difficult to post the GPL portion?
>
> jeff
>
> > >     dj> I'm told that the preview kits do include kernel source,
> > >     dj> although I haven't checked for myself in a couple of
months.
> > >
> > So that you got the binaries now could you check where their
written offer
> > is and post it to lkml?  Afterwards anyone on this list could ask
them
> > for their source (and at least I want to).
> >
> > Btw, what do people think of a regular list where anyone who got
such
> > an offer can post it so anyone else can get source aswell?
>
> -
> To unsubscribe from this list: send the line "unsubscribe
linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


  reply	other threads:[~2003-02-06  2:11 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
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 [this message]
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
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='001b01c2cd86$27db7240$59951ad3@windows' \
    --to=jamesbuch@iprimus.com.au \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wa1hco@adelphia.net \
    /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).