From: "Christopher Friesen" <cfriesen@nortelnetworks.com>
To: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Fasttrak100 questions...
Date: Thu, 30 Nov 2000 13:09:37 -0500 [thread overview]
Message-ID: <3A2697E1.B41C448@nortelnetworks.com> (raw)
In-Reply-To: <8voa7g$d1r$1@forge.tanstaafl.de> <Pine.LNX.4.21.0011291152500.5109-100000@sol.compendium-tech.com> <20001129210830.J17523@forge.tanstaafl.de> <20001129165236.A9536@vger.timpanogas.org> <3A266EE7.4C734350@nortelnetworks.com> <20001130114349.A12564@vger.timpanogas.org>
"Jeff V. Merkey" wrote:
>
> On Thu, Nov 30, 2000 at 10:14:47AM -0500, Christopher Friesen wrote:
> > I think you should re-read the GPL. You only have to provide source to
> > people to whome you have distributed your new binaries, and you only
> > have to provide that source if you are asked for it. If you have some
> > code that you have written that is based on GPL'd code, and you are the
> > only person that ever runs the binaries, then there is no obligation for
> > you to make your code available to anybody.
>
> Depends on what terms the code is provided under. Using GPL code in a
> for profit enterprise and distributing it to customers does require
> that the changes be provided upon request. I have read the GPL, and
> I've had a lot of lawyers around here read and analyze it too.
>
> :-)
Well of course this is the case. I specifically said that I am the only
one that ever ran the binaries. Once you start distributing it to other
people, then they can request the source additions/modifications and you
are obligated to provide it.
Theoretically you could use software based on GPL'd code all throughout
a for-profit corporation and make boatloads of money using that
software. As long as you don't distribute it to customers outside the
company, and as long as none of the employees using it ask for the
source and distribute it outside the company, nobody outside that
corporation has any right to the source even though it is being used for
profit.
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-30 20:06 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-24 22:46 Fasttrak100 questions James Lamanna
2000-11-25 1:35 ` Andre Hedrick
2000-11-25 12:10 ` Henning P. Schmiedehausen
2000-11-25 17:20 ` Andre Hedrick
2000-11-25 17:22 ` Andre Hedrick
2000-11-29 19:53 ` Dr. Kelsey Hudson
2000-11-29 20:08 ` Henning P . Schmiedehausen
2000-11-29 21:11 ` Andre Hedrick
2000-11-29 22:12 ` Stop your abusive language! (Re: Fasttrak100 questions...) Dominik Kubla
2000-11-29 23:52 ` Fasttrak100 questions Jeff V. Merkey
2000-11-30 15:14 ` Christopher Friesen
2000-11-30 18:43 ` Jeff V. Merkey
2000-11-30 18:09 ` Christopher Friesen [this message]
2000-11-30 20:10 ` Jeff V. Merkey
2000-12-02 3:44 ` Peter Samuelson
2000-12-03 22:54 ` Pavel Machek
2000-12-05 4:10 ` Peter Samuelson
2000-11-29 20:42 ` Alan Cox
2000-11-29 21:05 ` Andre Hedrick
2000-11-29 21:10 ` James A Sutherland
2000-11-29 21:18 ` Alan Cox
2000-11-29 21:30 ` Andre Hedrick
2000-12-02 16:50 ` Pavel Machek
2000-12-02 17:18 ` Alan Cox
2000-12-02 23:46 ` Theodore Y. Ts'o
2000-12-03 1:21 ` Jeff V. Merkey
2000-12-03 1:31 ` Jeff V. Merkey
2000-12-03 3:42 ` Theodore Y. Ts'o
2000-12-03 5:11 ` Jeff V. Merkey
2000-12-05 7:07 ` Brian F. G. Bidulock
2000-12-05 8:25 ` Jeff V. Merkey
-- strict thread matches above, loose matches on Subject: below --
2000-12-03 16:41 Wayne.Brown
2000-12-03 17:49 ` Pavel Machek
2000-12-03 18:45 ` Alan Cox
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=3A2697E1.B41C448@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=jmerkey@vger.timpanogas.org \
--cc=linux-kernel@vger.kernel.org \
/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