From: "Concerned Programmer" <tkhoadfdsaf@hotmail.com>
To: "David Woodhouse" <dwmw2@infradead.org>,
"Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: "Alexander Viro" <viro@math.psu.edu>,
"Keith Owens" <kaos@ocs.com.au>,
"Morgan Collins [Ax0n]" <sirmorcant@morcant.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: Tainted Modules Help Notices
Date: Wed, 10 Oct 2001 16:06:42 -0400 [thread overview]
Message-ID: <OE64YU5ts1Tjkw1BzCf0000708c@hotmail.com> (raw)
In-Reply-To: <E15rNBu-0008To-00@the-village.bc.nu> <4058.1002737910@redhat.com>
I was under the same impression about the module licensing tagging. I
had read that it was suppose to be for maintainability (.i.e. source
available so kernel gods can debug) and not to enforce ideological
conformity. Now I read that anything not licensed under the GPL, including
BSD or simply public domain source code, will taint my kernel and modprobe
complains about non-GPL stuff including parport_pc which apparently did not
have a license. Should I expect a Linux kernel KGB to show up next?
Furthermore I have to agree with the previous poster. Any module could
easily lie to MODULE_LICENSE about its licensing terms and that would not
make it's source automatically "free" and GPLable so I am now wondering if
this tainting mechanism is of any use at all.
Just out of curiosity do all of these license tags in the modules take
up any permanent kernel memory, especially in a heavily modularize system?
> I believe that statement is as true as the assertion that nobody, even in
> the Free World, can write GPL'd code which use the algorithms covered by
> the patent.
>
> Either way, I didn't think that a political stance against patents was the
> point of the kernel tainting code - I thought it was about
maintainability.
>
> > The problem we have is that "BSD without advertisment" can be claimed
> > by almost any binary only module whose author doesnt include source or
> > let it out fo their company ever
>
> GPL can also be claimed by a module whose author doesn't publish either
the
> source or the binary, or who charges lots and lots of money for shipping
the
> binary and ships the source with it with a 'request' that the recipient
> doesn't then give it away for free.
>
> But if we're not going to allow BSD-licensed modules to be loaded without
> tainting the kernel, we shouldn't mark any of the code distributed with
the
> kernel as BSD-licensed - we should make it all "Dual BSD/GPL" instead.
>
> It might also be useful to have a 'Dual GPL/Other' option, for covering
the
> other randomly dual-licensed code (like JFFS2).
next prev parent reply other threads:[~2001-10-10 20:08 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-10 8:06 Morgan Collins [Ax0n]
2001-10-10 8:20 ` David Woodhouse
2001-10-10 8:24 ` Morgan Collins [Ax0n]
2001-10-10 8:31 ` David Woodhouse
2001-10-10 13:50 ` Keith Owens
2001-10-10 13:59 ` Alexander Viro
2001-10-10 14:01 ` Keith Owens
2001-10-10 17:30 ` Alan Cox
2001-10-10 18:18 ` David Woodhouse
2001-10-10 20:06 ` Concerned Programmer [this message]
2001-10-10 20:28 ` Morgan Collins [Ax0n]
2001-10-10 21:28 ` Keith Owens
2001-10-10 22:03 ` Anthony DeRobertis
2001-10-11 7:27 ` David Woodhouse
2001-10-10 21:17 ` Alan Cox
2001-10-10 23:02 ` Juan Quintela
2001-10-10 23:28 ` Andreas Dilger
2001-10-10 22:29 ` Rob Landley
2001-10-11 2:48 ` 2.4.11 UDF Morgan Collins [Ax0n]
2001-10-11 3:26 ` Craig Whitmore
2001-10-11 8:50 ` Tainted Modules Help Notices Andreas Ferber
2001-10-11 9:25 ` Alan Cox
2001-10-11 9:35 ` Henning P. Schmiedehausen
2001-10-11 9:41 ` Pekka Pietikäinen
2001-10-11 9:48 ` Syed Mohammad Talha
2001-10-11 10:09 ` Concerned Programmer
2001-10-11 10:37 ` Alan Cox
2001-10-11 22:42 ` David Schwartz
2001-10-11 23:40 ` John Alvord
2001-10-12 1:12 ` David Schwartz
2001-10-12 1:32 ` Robert Love
2001-10-11 12:10 ` James Sutherland
2001-10-10 14:13 ` David Woodhouse
2001-10-10 14:18 ` Alexander Viro
2001-10-10 13:10 ` Alan Cox
2001-10-10 14:06 Bonds, Deanna
2001-10-10 14:24 ` Arjan van de Ven
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=OE64YU5ts1Tjkw1BzCf0000708c@hotmail.com \
--to=tkhoadfdsaf@hotmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dwmw2@infradead.org \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=sirmorcant@morcant.org \
--cc=viro@math.psu.edu \
/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
all inboxes | Powered by JetHome®