From: Axel Weiss <aweiss@informatik.hu-berlin.de>
To: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: module-licences / tainting the kernel
Date: Sat, 8 May 2004 09:57:57 +0200 [thread overview]
Message-ID: <200405080957.57286.aweiss@informatik.hu-berlin.de> (raw)
Hi all,
from my point of view, the 'tainting-rule' for kernel-modules is too
restrictive, allowing GPL-only modules to not be marked as tainting the
kernel.
Would it be possible to let e.g. LPGL-licenced kernel-modules be loaded
legally?
I do not at all want to hide my source code in any way, but under some
circumstances, the pure GPL is too restrictive, and would reduce interest in
open-source projects significantly.
Opinions?
Regards,
Axel
next reply other threads:[~2004-05-08 7:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-08 7:57 Axel Weiss [this message]
2004-05-08 8:03 ` Arjan van de Ven
2004-05-08 9:14 ` Måns Rullgård
2004-05-08 10:24 ` Axel Weiß
2004-05-08 10:29 ` Michael Buesch
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=200405080957.57286.aweiss@informatik.hu-berlin.de \
--to=aweiss@informatik.hu-berlin.de \
--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
all inboxes | Powered by JetHome®