From: "Henning P . Schmiedehausen" <hps@tanstaafl.de>
To: "Dr. Kelsey Hudson" <kernel@blackhole.compendium-tech.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Fasttrak100 questions...
Date: Wed, 29 Nov 2000 21:08:30 +0100 [thread overview]
Message-ID: <20001129210830.J17523@forge.tanstaafl.de> (raw)
In-Reply-To: <8voa7g$d1r$1@forge.tanstaafl.de> <Pine.LNX.4.21.0011291152500.5109-100000@sol.compendium-tech.com>
In-Reply-To: <Pine.LNX.4.21.0011291152500.5109-100000@sol.compendium-tech.com>; from "Dr. Kelsey Hudson" on Wed, Nov 29, 2000 at 11:53:59AM
No.
If I modify the kernel or any other GPL software for my personal use
and give it to no one, I am _not at all_ forced to make it public.
Only if I distribute a compiled kernel or any other program under GPL,
then I must give also the sources on request (!) and may not put any
restrictions on your redistribution of these sources. Only thing that
you must obey is again the GPL.
I use heavily patched kernels with lots of inhouse-stuff on a regular
base for my inhouse use and there is _no_ way for you to even get a
glimpse at it. I don't give this to anyone, it's all just my personal
stuff.
You can't force me to give you a copy of my blafoo driver until I
chose to either release it to the public in which case I must put it
under GPL as it contains GPLed code or distribute a binary version to
a customer, which then in turn has the right to request the source
from me and (after he got it, because I am bound by GPL to give it to
him), distribute it freely as this right is granted to him by GPL.
I am even allowed to erase my sources without making them ever public.
Please read the GPL:
--- cut ---
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running the Program is not restricted, and the output from the Program
--- cut ---
I don't distribute the software. I just run it.
--- cut ---
2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
--- cut ---
I chose not to copy and distribute these modified programs which is
perfectly covered by my license which I got when obtaining the
sources.
Anything else would mean that I can send E-Mail to Linus Torvalds
every five minutes and request a verbatim copy of his current hacking
kernel tree as it is under GPL, which he is the forced to give to me
because of the GPL. This would be utter nonsense.
Regards
Henning
On Wed, Nov 29, 2000 at 11:53:59AM -0800, Dr. Kelsey Hudson wrote:
> On Sat, 25 Nov 2000, Henning P. Schmiedehausen wrote:
>
> > No, it does not. Distributing does. You will never get this right. You
> > can compile into your kernel anything you like as long as you don't
> > give it away.
>
> You are wrong: If you modify the kernel you have to make it available for
> anyone who wishes to use it; that's also in the GPL. You can't add stuff
> to it and then not distribute it, that's in violation.
>
> Kelsey Hudson khudson@ctica.com
> Software Engineer
> Compendium Technologies, Inc (619) 725-0771
> ---------------------------------------------------------------------------
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH hps@intermeta.de
Am Schwabachgrund 22 Fon.: 09131 / 50654-0 info@intermeta.de
D-91054 Buckenhof Fax.: 09131 / 50654-20
-
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-29 20:39 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 [this message]
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
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=20001129210830.J17523@forge.tanstaafl.de \
--to=hps@tanstaafl.de \
--cc=kernel@blackhole.compendium-tech.com \
--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