From: Chris Friesen <cfriesen@nortel.com>
To: linux-os@analogic.com
Cc: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>,
Karel Kulhavy <clock@twibright.com>,
linux-kernel@vger.kernel.org
Subject: Re: GPL violation by CorAccess?
Date: Tue, 19 Apr 2005 17:37:04 -0600 [thread overview]
Message-ID: <42659620.5050002@nortel.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0504191741190.19956@chaos.analogic.com>
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.
> They do not have to give away their trade-secrets.
GPL'd applications would still be covered by the GPL, no?
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.
Any *new* apps that they wrote they would of course be free to keep private.
next prev parent reply other threads:[~2005-04-19 23:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-19 17:57 GPL violation by CorAccess? 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 [this message]
2005-04-20 0:26 ` Richard B. Johnson
2005-04-20 7:30 ` Bernd Petrovitsch
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=42659620.5050002@nortel.com \
--to=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