From: Patrick McFarland <diablod3@gmail.com>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Anonymous User <anonymouslinuxuser@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: GPL Violation?
Date: Thu, 17 Aug 2006 05:36:43 -0400 [thread overview]
Message-ID: <200608170536.44733.diablod3@gmail.com> (raw)
In-Reply-To: <44E429B3.7030607@s5r6.in-berlin.de>
On Thursday 17 August 2006 04:32, Stefan Richter wrote:
> Patrick McFarland wrote:
> > They don't have to release source code for any module you wrote from
> > scratch themselves, but said modules cannot say they are GPL (ie, they
> > have to poison the kernel).
> >
> > Also, said kernel modules have to be real modules and not statically
> > linked into the kernel, and said modules have to have the compiled
> > component objects (ie, *.o) available so people can relink them into new
> > modules to work with new kernels.
>
> I never heard that static vs. dynamic linking mattered WRT licensing, at
> least if the unmodified GPL is involved.
AFAICT you can't link GPL to non-GPL code and ship the product without heading
deep into grey area territory. Both the GPL and LGPL has specific wording for
certain cases (such as allowing LGPL (possibly GPL too?) to link to closed
source system libraries and the reverse as well), but its really icky to link
GPL to closed source code in any form.
> If a driver author doesn't want
> to publish under the terms of GPL, an implementation in userspace may
> make it possible to avoid linking with GPL code.
But doesn't that force the GPL code to rely on closed source code, and not
function properly without it? I remember a part in the GPL about not allowing
that, but I can't seem to find it atm.
> Here are a few pointers to the opinion of FSF as published in their FAQ.
> (I doubt that the organization FSF is among the copyright holders of
> Linux, but the FSF is copyright holder of the GPL and authors of GPL run
> FSF. Therefore the FSF's statements are certainly relevant for you to
> consider.)
Now thats pretty useful information. I think everyone should bookmark those
and file those away for later, I sure am. Thanks for finding those.
--
Patrick McFarland || www.AdTerrasPerAspera.com
"Computer games don't affect kids; I mean if Pac-Man affected us as kids,
we'd all be running around in darkened rooms, munching magic pills and
listening to repetitive electronic music." -- Kristian Wilson, Nintendo,
Inc, 1989
next prev parent reply other threads:[~2006-08-17 9:35 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-17 5:48 GPL Violation? Anonymous User
2006-08-17 6:14 ` Arjan van de Ven
2006-08-17 9:38 ` Ben B
2006-08-17 12:02 ` linux-os (Dick Johnson)
2006-08-17 16:11 ` Stefan Richter
2006-08-17 19:21 ` James Courtier-Dutton
2006-08-17 23:26 ` Ian Stirling
[not found] ` <20060817193540.dc819396.seanlkml@sympatico.ca>
2006-08-17 23:35 ` Sean
2006-08-18 0:32 ` Alan Cox
2006-08-18 7:23 ` Xavier Bestel
2006-08-18 12:23 ` Ian Stirling
2006-08-18 9:04 ` Helge Hafting
2006-08-17 6:42 ` Patrick McFarland
2006-08-17 6:54 ` Arjan van de Ven
2006-08-17 7:32 ` Patrick McFarland
2006-08-17 8:02 ` Adrian Bunk
2006-08-17 9:03 ` Patrick McFarland
2006-08-18 17:56 ` Adrian Bunk
2006-08-17 12:39 ` Grzegorz Kulewski
2006-08-17 13:41 ` Alan Cox
2006-08-17 13:31 ` Grzegorz Kulewski
2006-08-17 15:52 ` Theodore Tso
2006-08-18 2:03 ` Chase Venters
2006-08-17 8:32 ` Stefan Richter
2006-08-17 9:36 ` Patrick McFarland [this message]
2006-08-17 11:25 ` Alan Cox
2006-08-17 11:48 ` Neil Brown
2006-08-17 9:37 ` David Woodhouse
2006-08-17 23:45 ` Ian Stirling
2006-08-18 8:28 ` David Woodhouse
2006-08-18 12:52 ` Ian Stirling
2006-08-18 8:53 ` Bernd Petrovitsch
2006-08-18 9:04 ` David Woodhouse
2006-08-18 9:15 ` Bernd Petrovitsch
2006-08-20 22:05 ` Andrea Arcangeli
2006-08-20 22:20 ` Arjan van de Ven
2006-08-18 9:51 ` David Schwartz
2006-08-18 16:52 ` Alan Cox
2006-08-18 22:42 ` David Schwartz
2006-08-19 10:48 ` David Greaves
2006-08-19 16:29 ` Patrick McFarland
2006-08-19 17:28 ` David Greaves
2006-08-19 11:30 ` Helge Hafting
2006-08-19 15:44 ` Michael Buesch
2006-08-19 23:01 ` David Schwartz
2006-08-20 3:20 ` Chase Venters
2006-08-21 7:58 ` Helge Hafting
2006-08-21 11:27 ` Stefan Richter
2006-08-21 13:06 ` Alan Cox
2006-08-21 14:59 ` Horst H. von Brand
2006-08-17 9:30 ` Alan Cox
2006-08-17 9:29 ` Patrick McFarland
2006-08-17 14:52 ` Helge Hafting
2006-08-17 14:58 ` Anonymous User
2006-08-17 15:52 ` Stefan Richter
2006-08-17 16:19 ` Michiel de Boer
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=200608170536.44733.diablod3@gmail.com \
--to=diablod3@gmail.com \
--cc=anonymouslinuxuser@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
/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