From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Ramakanth Gunuganti <rgunugan@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: GPL issues
Date: Wed, 12 Apr 2006 00:12:19 +0100 [thread overview]
Message-ID: <1144797140.29275.33.camel@localhost.localdomain> (raw)
In-Reply-To: <20060411063127.97362.qmail@web54314.mail.yahoo.com>
On Llu, 2006-04-10 at 23:31 -0700, Ramakanth Gunuganti wrote:
> 1. If an application is built on top of this modified
> kernel, should the application be released under GPL?
> Do system calls provide a bounday for GPL? How does
> this work with LKMs, all the code for LKMs will be
> released but would a userspace application using the
> LKMs choose not to use GPL?
The boundary of the GPL is what is called a "derivative work". This is
the basic concept in law used by copyright and essentially asks "is this
work created in such a way that it is based on the original work in some
meaningful fashion". Its a complex area of law and only a lawyer can
give definitive answers.
The usual case is releasing an application for the Linux OS. It is
unlikely that using system calls could be considered "derivative" and in
case there is doubt the copying file with the Linux kernel specifically
excludes this case because the authors don't want some peculiar legal
interpretation to suddenely try and claim rights on applications running
on Linux.
Your questions really come into the realm of lawyers not programmers
however especially the various fringe areas.
The simple "application for Linux" case is clear. The simple "kernel
modification" case is also clear. In the middle is the vague area that
is for lawyers.
next prev parent reply other threads:[~2006-04-11 23:06 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-11 6:31 GPL issues Ramakanth Gunuganti
2006-04-11 8:42 ` Jesper Juhl
2006-04-11 10:51 ` Martin Mares
2006-04-11 17:46 ` Horst von Brand
2006-04-11 13:49 ` Kyle Moffett
2006-04-11 15:49 ` Ramakanth Gunuganti
2006-04-11 16:07 ` linux-os (Dick Johnson)
2006-04-11 16:29 ` Stefan Smietanowski
2006-04-11 16:13 ` Adrian Bunk
2006-04-11 16:15 ` Kyle Moffett
2006-04-11 16:23 ` Dave Neuer
2006-04-11 18:58 ` Jan Engelhardt
2006-04-14 11:39 ` David Schwartz
2006-04-14 14:54 ` linux-os (Dick Johnson)
2006-04-14 17:50 ` David Weinehall
2006-04-14 18:56 ` David Schwartz
2006-04-15 11:55 ` Alan Cox
2006-04-15 13:04 ` Steven Rostedt
2006-04-15 18:49 ` David Schwartz
2006-04-11 15:49 ` Ramakanth Gunuganti
2006-04-11 23:06 ` David Weinehall
2006-04-12 2:38 ` Joshua Hudson
2006-04-12 3:18 ` Mark Lord
2006-04-12 5:00 ` Kyle Moffett
2006-04-12 5:31 ` Arjan van de Ven
2006-04-12 5:45 ` jdow
2006-04-12 6:01 ` David Weinehall
2006-04-12 6:26 ` jdow
2006-04-12 9:13 ` Stefan Smietanowski
2006-04-12 11:33 ` Olivier Galibert
2006-04-12 14:51 ` Arjan van de Ven
2006-04-13 22:07 ` Mark Lord
2006-04-15 11:14 ` Arjan van de Ven
2006-04-13 22:17 ` Mark Lord
2006-04-15 11:15 ` Arjan van de Ven
2006-04-11 23:12 ` Alan Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-12 7:01 Pramod Srinivasan
2006-04-12 8:16 ` David Weinehall
2006-04-12 9:06 ` Jan Engelhardt
2006-04-12 9:22 ` Stefan Smietanowski
2006-04-12 9:40 ` Martin Mares
2006-04-12 9:28 ` Alan Cox
2006-04-14 11:39 ` David Schwartz
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=1144797140.29275.33.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rgunugan@yahoo.com \
/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.