lkml.org 
[lkml]   [2005]   [Apr]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: GPL violation by CorAccess?
From
Date
On Tue, 2005-04-19 at 17:37 -0600, Chris Friesen wrote:
> Richard B. Johnson wrote:
>
> > No. Accompany it with a written offer to __provide__ the source
> > code for any GPL stuff they used (like the kernel or drivers).
> > Anything at the application-level is NOT covered by the GPL.

That depends on the software used there.

> > They do not have to give away their trade-secrets.

Unless they coded them into GPL software ...

> GPL'd applications would still be covered by the GPL, no?

Good question: Strictly speaking if you omit the GPL in the delivered
ssoftware/product/whatever, you violated the GPL yourself and - thus -
loose all rights which are "given" to you through the GPL.

> If I buy their product, I should be able to ask them for the source to
> all GPL'd entities that are present in the system, including the kernel,
> drivers, and all GPL'd userspace apps.

ACK.

> Any *new* apps that they wrote they would of course be free to keep private.

As long as they do not statically link against LGPL (or GPL) code and as
long as they do not link dynamically agaist GPL code. And there are
probably more rules .....

Bernd
--
Firmix Software GmbH http://www.firmix.at/
mobil: +43 664 4416156 fax: +43 1 7890849-55
Embedded Linux Development and Services



-
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-04-20 09:36    [W:0.060 / U:0.832 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site