From: Jon Masters <jonathan@jonmasters.org>
To: Pavel Roskin <proski@gnu.org>
Cc: Valdis.Kletnieks@vt.edu, linux-kernel@vger.kernel.org,
Rusty Russell <rusty@rustcorp.com.au>,
Giridhar Pemmasani <pgiri@yahoo.com>
Subject: Re: ndiswrapper and GPL-only symbols redux
Date: Tue, 29 Jan 2008 19:25:29 -0500 [thread overview]
Message-ID: <1201652729.2271.95.camel@perihelion> (raw)
In-Reply-To: <1201648883.18773.95.camel@dv>
On Tue, 2008-01-29 at 18:21 -0500, Pavel Roskin wrote:
> Of course, ndiswrapper could taint itself as a module, but it would be a
> purely symbolic act, since the module would be loaded already, and the
> GPL-only symbols resolved.
I think that might be an acceptable alternative to the current explicit
matching on "ndiswrapper" in the kernel. Something should say "hey, the
kernel is tainted, and I'm the reason why", not just set a global taint.
Note: personal opinion aside, I actually wasn't trying to start a huge
copyright debate here. I just thought the taint flag logic was wrong (if
we're going to match on specific modules, we should mark them) - an
alternative would be a new type of taint flag?
Jon.
next prev parent reply other threads:[~2008-01-30 0:26 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-29 21:22 ndiswrapper and GPL-only symbols redux Pavel Roskin
2008-01-29 22:27 ` Valdis.Kletnieks
2008-01-29 22:35 ` Giridhar Pemmasani
2008-01-29 23:21 ` Pavel Roskin
2008-01-30 0:25 ` Jon Masters [this message]
2008-01-29 22:45 ` Alan Cox
2008-01-29 23:56 ` Pavel Roskin
2008-01-30 3:24 ` Andi Kleen
2008-01-30 5:07 ` Jon Masters
2008-01-30 5:26 ` Pavel Roskin
2008-01-30 6:03 ` Andi Kleen
2008-01-30 6:12 ` Pavel Roskin
2008-01-29 22:57 ` Adrian Bunk
2008-01-29 23:04 ` Alan Cox
2008-01-29 23:06 ` Jan Engelhardt
2008-01-29 23:25 ` Måns Rullgård
2008-01-30 0:35 ` Adrian Bunk
2008-01-30 0:46 ` Måns Rullgård
2008-01-30 1:44 ` Daniel Hazelton
2008-01-30 7:38 ` Geert Uytterhoeven
2008-01-30 8:45 ` Måns Rullgård
2008-01-30 21:00 ` David Schwartz
2008-01-29 23:44 ` Pavel Roskin
2008-01-30 0:25 ` Adrian Bunk
2008-01-30 2:02 ` Pavel Roskin
2008-01-30 11:24 ` Rusty Russell
2008-01-30 17:54 ` Adrian Bunk
2008-01-30 18:15 ` Lennart Sorensen
2008-01-30 18:45 ` Adrian Bunk
2008-01-30 19:43 ` Lennart Sorensen
2008-01-30 20:26 ` Valdis.Kletnieks
2008-01-30 21:09 ` Adrian Bunk
[not found] ` <E1JKJvh-0006P8-Pi@fencepost.gnu.org>
2008-02-01 5:08 ` Pavel Roskin
2008-02-06 10:50 ` Adrian Bunk
2008-02-06 11:11 ` Xavier Bestel
2008-02-06 11:38 ` David Schwartz
2008-02-06 15:10 ` Theodore Tso
2008-01-30 0:48 ` Giridhar Pemmasani
2008-01-30 17:54 ` Adrian Bunk
2008-01-30 18:26 ` Chris Friesen
2008-01-30 18:54 ` Adrian Bunk
2008-01-30 19:36 ` Lee Revell
2008-01-30 20:28 ` Adrian Bunk
2008-01-31 1:00 ` Michael Gerdau
2008-02-05 13:00 ` Adrian Bunk
2008-02-04 12:42 ` Alan Cox
2008-02-04 13:56 ` Adrian Bunk
2008-01-31 3:25 ` David Newall
2008-01-31 15:20 ` Chris Friesen
2008-01-30 0:20 ` Jon Masters
2008-01-30 0:35 ` Jan Engelhardt
2008-01-30 0:48 ` Jon Masters
2008-01-30 1:33 ` Pavel Roskin
2008-01-30 1:48 ` Pavel Roskin
2008-01-30 2:08 ` Jan Engelhardt
2008-01-30 5:04 ` Jon Masters
2008-01-30 5:38 ` Zan Lynx
2008-01-30 7:40 ` Geert Uytterhoeven
2008-01-30 8:54 ` Måns Rullgård
2008-01-30 20:50 ` 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=1201652729.2271.95.camel@perihelion \
--to=jonathan@jonmasters.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=pgiri@yahoo.com \
--cc=proski@gnu.org \
--cc=rusty@rustcorp.com.au \
/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