lkml.org 
[lkml]   [2001]   [Jun]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Controversy over dynamic linking -- how to end the panic
On Thu, Jun 21, 2001 at 11:39:13AM -0700, Jeff Golds wrote:
> "Eric S. Raymond" wrote:
> > ------------------------------------------------------------------------
> > The GPL license reproduced below is copyrighted by the Free Software
> > Foundation, but the Linux kernel is copyrighted by me and others who
> > actually wrote it.
> >
> > The GPL license requires that derivative works of the Linux kernel
> > also fall under GPL terms, including the requirement to disclose
> > source. The meaning of "derivative work" has been well established
> > for traditional media, and those precedents can be applied to
> > inclusion of source code in a straightforward way. But as of
> > mid-2001, neither case nor statute law has yet settled under what
> > circumstances *binary* linkage of code to a kernel makes that code a
> > derivative work of the kernel.
> >
> > To calm down the lawyers, I as the principal kernel maintainer and
> > anthology copyright holder on the code am therefore adding the
> > following interpretations to the kernel license:
> >
> > 1. Userland programs which request kernel services via normal system
> > calls *are not* to be considered derivative works of the kernel.
> >
> > 2. A driver or other kernel component which is statically linked to
> > the kernel *is* to be considered a derivative work.
> >
> > 3. A kernel module loaded at runtime, after kernel build, *is not*
> > to be considered a derivative work.
> >
> > These terms are to be considered part of the kernel license, applying
> > to all code included in the kernel distribution. They define your
> > rights to use the code in *this* distribution, however any future court
> > may rule on the underlying legal question and regardless of how the
> > license or interpretations attached to future distributions may change.
>
> I disagree with 2. Consider the following:
>
> - GPL library foo is used by application bar. bar must be GPL because
> foo is. I agree with this.
> - Non-GPL library foo is used by GPL application bar. foo does NOT
> become GPL just because bar is, even if bar statically linked foo in.
>
> The kernel is the equivalent of an application. If someone needs to
> statically link in a driver, which is the equivalent of a library, I
> don't see how that should make the driver GPL.
>
>
> -Jeff
>
> P.S. I don't claim to be a lawyer, this is just my opinion.

http://www.gnu.org/copyleft/gpl-faq.html#WritingFSWithNFLibs offers some
insight on linking free software with non-free libraries.

However, I'm not sure I agree with your interpretation of the relationship
between kernel and driver.

The kernel is fully functional (excluding use of the hardware for which
the driver provides an interface) without the driver code - however, the
driver requires the kernel to be usable. Still using your analogy, it would
seem the driver is the application, and the kernel is the library.
The facilities that the driver provides to the kernel don't seem to be
much more than callbacks used in traditional library schemes to implement
application specific behavior as part of a larger library framework.

My 2c.

-Jeff

--
Jeff Mahoney
jeffm@suse.com
jeffm@csh.rit.edu
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 12:55    [W:0.103 / U:0.068 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site