mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bernd Petrovitsch <bernd@firmix.at>
To: Chris Friesen <cfriesen@nortel.com>
Cc: linux-os@analogic.com,
	Lennart Sorensen <lsorense@csclub.uwaterloo.ca>,
	Karel Kulhavy <clock@twibright.com>,
	linux-kernel@vger.kernel.org
Subject: Re: GPL violation by CorAccess?
Date: Wed, 20 Apr 2005 09:30:08 +0200	[thread overview]
Message-ID: <1113982209.3803.7.camel@gimli.at.home> (raw)
In-Reply-To: <42659620.5050002@nortel.com>

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




  parent reply	other threads:[~2005-04-20  7:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-19 17:57 Karel Kulhavy
2005-04-19 18:25 ` Lennart Sorensen
2005-04-19 18:32   ` Charles Cazabon
2005-04-19 18:59     ` Chris Friesen
2005-04-19 19:19   ` Richard B. Johnson
2005-04-19 19:59     ` Chris Friesen
2005-04-19 21:44       ` Richard B. Johnson
2005-04-19 23:37         ` Chris Friesen
2005-04-20  0:26           ` Richard B. Johnson
2005-04-20  7:30           ` Bernd Petrovitsch [this message]
2005-04-20 12:49             ` Steven Rostedt
2005-04-20 12:57               ` Arjan van de Ven
2005-04-20 13:07                 ` Steven Rostedt
2005-04-20 13:36                   ` Michael Poole
2005-04-20 13:37                   ` Arjan van de Ven
2005-04-20 17:18   ` Pavel Machek

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=1113982209.3803.7.camel@gimli.at.home \
    --to=bernd@firmix.at \
    --cc=cfriesen@nortel.com \
    --cc=clock@twibright.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.com \
    --cc=lsorense@csclub.uwaterloo.ca \
    /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

all inboxes | Powered by JetHome®