From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: markh@compro.net
Cc: Erik Mouw <erik@harddisk-recovery.com>,
dmarkh@cfl.rr.com, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Another kernel releated GPL ?
Date: Thu, 26 Oct 2006 17:17:14 +0100 [thread overview]
Message-ID: <1161879434.12781.61.camel@localhost.localdomain> (raw)
In-Reply-To: <4540CDFE.4000003@compro.net>
Ar Iau, 2006-10-26 am 11:02 -0400, ysgrifennodd Mark Hounschell:
> > In the usual case it doesn't matter, much stuff is GPL anyway, and for
> > the usual system calls/C library stuff not only is the law probably
> > fairly well established but there is an explicit statement with the
> > kernel that we don't want to claim such rights for a normal system call
> > which would guide a Judge if a case ever came up.
> >
> >
>
> That's sort of what I was in search of. Where is this "explicit statement" found
> BTW.
COPYING file in the top directory of the kernel.
NOTE! This copyright does *not* cover user programs that use kernel
services by normal system calls - this is merely considered normal use
of the kernel, and does *not* fall under the heading of "derived work".
Also note that the GPL below is copyrighted by the Free Software
Foundation, but the instance of code that it refers to (the Linux
kernel) is copyrighted by me and others who actually wrote it.
Also note that the only valid version of the GPL as far as the kernel
is concerned is _this_ particular version of the license (ie v2, not
v2.2 or v3.x or whatever), unless explicitly otherwise stated.
Linus Torvalds
next prev parent reply other threads:[~2006-10-26 16:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-26 9:45 Another kernel releated GPL ? Mark Hounschell
2006-10-26 11:12 ` Alan Cox
2006-10-26 11:28 ` Mark Hounschell
2006-10-26 11:48 ` Alan Cox
2006-10-26 11:54 ` Pekka Enberg
2006-10-26 12:10 ` Erik Mouw
2006-10-26 13:11 ` Mark Hounschell
2006-10-26 14:21 ` Alan Cox
2006-10-26 15:02 ` Mark Hounschell
2006-10-26 16:17 ` Alan Cox [this message]
2006-10-26 16:24 ` Vadim Lobanov
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=1161879434.12781.61.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=dmarkh@cfl.rr.com \
--cc=erik@harddisk-recovery.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markh@compro.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.