From: Shawn Starr <spstarr@sh0n.net>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Binary drivers and GPL
Date: Sun, 5 Jan 2003 02:47:57 -0500 [thread overview]
Message-ID: <200301050247.57845.spstarr@sh0n.net> (raw)
Enough is enough! I'm SO tired of hearing this over and over now. But since
it's raging on I might as well throw some coal into the fire a little ;-)
As much as I would love to see a ban on binary drivers to protect the kernel,
this issue isn't going away. Not only that but I'd love to see a module
blacklist in which a non-tainted kernel refuses to load binary drivers that
are not GPL.
We have to make sure that we restrict binary drivers as much as possible
because other companies may decide that they don't need to release their
specs/sources anymore because binary drivers become the norm and because
their competition is also not releasing their specs/code. This I fear is the
danger if we go down this road. We can't allow companies to dictate
indirectly how a kernel will function.
Shawn.
next reply other threads:[~2003-01-05 7:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-05 7:47 Shawn Starr [this message]
[not found] <Pine.LNX.4.10.10301042352540.421-100000@master.linux-ide.org>
2003-01-05 8:01 ` Binary drivers and GPL Shawn Starr
2003-01-05 8:25 ` Andre Hedrick
2003-01-05 9:09 ` Shawn Starr
2003-01-05 9:33 ` Andre Hedrick
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=200301050247.57845.spstarr@sh0n.net \
--to=spstarr@sh0n.net \
--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