From: Keith Owens <kaos@ocs.com.au>
To: linux-kernel@vger.kernel.org
Subject: Re: MODULE_LICENSE and EXPORT_SYMBOL_GPL
Date: Sat, 20 Oct 2001 16:38:25 +1000 [thread overview]
Message-ID: <28610.1003559905@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Fri, 19 Oct 2001 13:07:37 MST." <Pine.LNX.4.40.0110191257070.9276-100000@dlang.diginsite.com>
On Fri, 19 Oct 2001 13:07:37 -0700 (PDT),
David Lang <david.lang@digitalinsight.com> wrote:
>the problem posted is that a BSD no adv licence is GPL compatable and
>source may be available and therefor BSD no adv modules should not taint
>the kernel, on the other hand it's possible to have a BSD no adv licensed
>module that the source is not available for and therefor it should taint
>the kernel.
Do not cc: me on this thread.
Check module.h and insmod.c before making statements like that. The
BSD no advert license is not considered GPL compatible in the kernel.
Only Dual BSD/GPL is non-tainting, because the code is also available
under the GPL. Anybody taking advantage of the BSD no adv license to
create a binary only module will be tainted.
That causes a problem for some modules in the kernel tree that have the
BSD no advert license. Ideally these should be changed to dual BSD/GPL
but that may not be possible. Since their source code is always
available, we might change them to
"BSD without advertisement clause, source is in the kernel tree"
and add that string to the non-tainting list. BSD no advert code that
is not in the kernel tree can either switch to dual BSD/GPL or be
tainted, at the choice of the supplier.
The affected code in the kernel tree is
drivers/net/bsd_comp.c
drivers/net/pcmcia/wavelan_cs.c
drivers/net/ppp_deflate.c
drivers/net/slhc.c
drivers/net/strip.c
drivers/scsi/advansys.c
drivers/scsi/dpt_i2o.c
drivers/scsi/pci2000.c
drivers/scsi/pci2220i.c
drivers/scsi/u14-34f.c
fs/nls/nls_cp1251.c
fs/nls/nls_cp1255.c
fs/nls/nls_cp437.c
fs/nls/nls_cp737.c
fs/nls/nls_cp775.c
fs/nls/nls_cp850.c
fs/nls/nls_cp852.c
fs/nls/nls_cp855.c
fs/nls/nls_cp857.c
fs/nls/nls_cp860.c
fs/nls/nls_cp861.c
fs/nls/nls_cp862.c
fs/nls/nls_cp863.c
fs/nls/nls_cp864.c
fs/nls/nls_cp865.c
fs/nls/nls_cp866.c
fs/nls/nls_cp869.c
fs/nls/nls_cp874.c
net/ipv4/netfilter/ipchains_core.c
next prev parent reply other threads:[~2001-10-20 6:38 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-18 16:43 Roy Murphy
2001-10-18 15:49 ` Arjan van de Ven
2001-10-18 18:42 ` Tim Bird
2001-10-19 15:38 ` Taral
2001-10-18 16:07 ` Jan-Benedict Glaw
2001-10-18 22:38 ` David Lang
2001-10-19 0:46 ` John Alvord
2001-10-18 23:57 ` David Lang
2001-10-19 12:44 ` Reid Hekman
2001-10-19 20:07 ` David Lang
2001-10-20 0:00 ` Reid Hekman
2001-10-20 6:38 ` Keith Owens [this message]
2001-10-21 15:06 ` Alan Cox
2001-10-21 15:47 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2001-10-19 18:03 Roy Murphy
2001-10-18 16:05 Roy Murphy
2001-10-18 15:17 ` Arjan van de Ven
2001-10-19 15:30 ` Taral
2001-10-21 15:22 ` Alan Cox
2001-10-21 20:16 ` Taral
2001-10-19 17:06 ` David Woodhouse
2001-10-18 3:23 Keith Owens
2001-10-18 4:03 ` Alexander Viro
2001-10-19 7:16 ` Kai Henningsen
2001-10-19 8:26 ` Nils Philippsen
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=28610.1003559905@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--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
Powered by JetHome