From: Jan Niehusmann <jan@gondor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Input on the Non-GPL Modules
Date: Thu, 18 Oct 2001 18:32:17 +0200 [thread overview]
Message-ID: <20011018183217.A5055@gondor.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0110181113020.9058-100000@wyrm.rakis.net>
In-Reply-To: <Pine.LNX.4.21.0110181113020.9058-100000@wyrm.rakis.net>
On Thu, Oct 18, 2001 at 11:29:57AM -0400, Greg Boyce wrote:
> However, with the addition of GPL only symbols, you add motivation for
> conning. Not by end users, but by the developers of binary only
> modules. If they export the GPL license symbol, they gain access to
> kernel symbols that they may want to use. Since no code is actually being
> stolen, would this kind of trick actually cause a licensing violation?
What about a different way of circumventing the GPL only symbols?
What prevents the author of a non-GPL module who needs access to a
GPL-only symbol from writing a small GPLed module which imports the
GPL-only symbol (this is allowed, because the small module is GPL),
and exports a basically identical symbol without the GPL-only
restriction?
Then he could use this new symbol from his non-GPL module.
Jan
next prev parent reply other threads:[~2001-10-18 16:32 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 [this message]
2001-10-18 17:08 ` Tony Hoyle
2001-10-18 17:15 ` Jan Niehusmann
2001-10-18 19:01 ` Tim Bird
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=20011018183217.A5055@gondor.com \
--to=jan@gondor.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