From: Tim Bird <tbird@lineo.com>
To: unlisted-recipients:; (no To-header on input)@localhost.localdomain
Cc: linux-kernel@vger.kernel.org
Subject: Re: Input on the Non-GPL Modules
Date: Thu, 18 Oct 2001 13:01:51 -0600 [thread overview]
Message-ID: <3BCF271F.2CDAB9B7@lineo.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0110181113020.9058-100000@wyrm.rakis.net> <20011018183217.A5055@gondor.com> <3bcf0c42.97910140@tony-home> <20011018191539.A5676@gondor.com>
Jan Niehusmann wrote:
>
> On Thu, Oct 18, 2001 at 05:08:13PM +0000, Tony Hoyle wrote:
> > This is still a GPL violation, as the small module couldn't then be
> > linked with the proprietary module. Most companies aren't prepared to
> > get into the legally murky ground that that sort of thing entails.
>
> Why not? It is obviously allowed to write proprietary modules, as long
> as they dont use GPL-only interfaces.
This is not true from both the standpoint of what Linus has
said and what copyright law says.
Linus made an exception for proprietary modules, but also
made an exception to the exception in the case of modules
providing "essential" functionality. I don't have his
exact wording, but it was something to the effect that
using dynamic loading purely as a dodge on the GPL was not
kosher.
My belief is that proprietary modules are "allowed" (tolerated
might be a better word), when they meet several criteria
(including but not limited to):
- another module of the same type is proprietary, and:
- it is included in kernel.org source, or
- there is a long-standing precedence for
proprietary modules of this kind
- no portion of the kernel which is statically linked
relies on the loadable module.
- the module does NOT provide an essential facility
of the OS (such as sheduling, baseline memory management,
etc.)
Unfortunately, all of this is fairly nebulous and subjective.
On the second point, copyright law doesn't make the same types
of distinctions on derivative works that programmers appear
prone to make (eg. does it link statically or dynamically?).
Dynamic linking matters a whole lot less for copyright law
than other factors, like whether there are multiple
implementations of the interface available or what the
purpose of the interface is.
Finally, I am NOT a laywer and I'm not Linus. Take what I
say on this list with a grain of salt.
____________________________________________________________
Tim Bird Lineo, Inc.
Senior VP, Research 390 South 400 West
tbird@lineo.com Lindon, UT 84042
next prev parent reply other threads:[~2001-10-18 18:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-18 15:29 Input on the Non-GPL Modules Greg Boyce
2001-10-18 16:00 ` M. R. Brown
2001-10-18 16:32 ` Jan Niehusmann
2001-10-18 17:08 ` Tony Hoyle
2001-10-18 17:15 ` Jan Niehusmann
2001-10-18 19:01 ` Tim Bird [this message]
2001-10-18 19:38 ` Rik van Riel
2001-10-20 22:04 ` Alan Cox
2001-10-20 22:08 ` Ben Greear
2001-10-22 15:19 ` Input on the Non-GPL Modules - legal nonsense Tim Bird
2001-10-22 15:30 ` Ben Greear
2001-10-22 17:04 ` Jan Niehusmann
2001-10-25 6:24 ` David Schwartz
2001-10-26 3:58 ` Rob Landley
2001-10-20 22:20 ` Input on the Non-GPL Modules Anton Altaparmakov
2001-10-21 14:28 ` Alan Cox
2001-10-20 22:58 ` Craig Milo Rogers
-- strict thread matches above, loose matches on Subject: below --
2001-10-18 18:52 Mike Borrelli
2001-10-18 19:09 ` Matti Aarnio
2001-10-18 18:55 Borrelli, Michael J
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=3BCF271F.2CDAB9B7@lineo.com \
--to=tbird@lineo.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