lkml.org 
[lkml]   [2003]   [Feb]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: Monta Vista software license terms
On Tue, 11 Feb 2003 08:42:26 +0100, Horst von Brand wrote:

>>On Mon, 10 Feb 2003 11:42:45 -0600, Oliver Xymoron wrote:

>>>I certainly agree, but the problem is the NDA puts the shoe on the
>>>other foot and now it's the customer that has to consult a lawyer
>>>or
>>>risk a nuisance suit before proceeding. So while it may not
>>>forbid, >it
>>>certainly discourages and impedes. Let me point out that I never
>>>saw
>>>the NDA in question but said coworker was sufficiently intimidated
>>>>by
>>>it that he was unwilling to give me a copy of the kernel and gcc
>>>sources because of it.

>> I believe such a provision would, unfortunately, by considered
>>legally enforceable. The rationale would be that the rights you
>>(the
>>recipient of the derived work) have under the GPL would only apply
>>if
>>the distributor were bound by the GPL. The only way the distributor
>>
>>could be bound by the GPL was if he or she did something that he
>>didn't have the right to do without the GPL to give him or her such
>>a
>>right.

>The GPL gives me the right to distribute modified versions _only if
>I
>comply with the GPL_. And GPL forbids further restrictions when
>distributing.

I realize that. But that has nothing to do with what I said, which
analyzes only those rights you have without agreeing to the GPL by
virtue of the fact that you possess the work and were not subject to
any restrictions in the process of acquiring and using it.

>If your bizarre interpretation was right, no software licence at all
>would
>have any validity. In particular, I'd be more than very surprised if
>the
>GPL was so sloppily written. It was written with the input of
>eminent lawyers, after all.

Your generalization doesn't apply because of several major
differences between most software licenses and the GPL:

1) Most software licenses do not grant everyone the right to use the
work covered.

2) Most software licenses do not grant anyone the right to create
derived works.

3) Most software licenses require your assent before you can use the
covered work, in fact, most require your assent before you have the
right to possess the covered work.

However, one sticky point is that the GPL talks about 'modifying' a
work. You can create derived works without modifying the original
work and the GPL is unclear in this respect. However, I would argue
that linking to a library file is using it and including a header
file in your C code is using it. After all, there is nothing else you
can do with such files.

DS


-
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/

\
 
 \ /
  Last update: 2005-03-22 13:33    [W:0.111 / U:0.248 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site