From: brian@worldcontrol.com
To: linux-kernel@vger.kernel.org
Subject: loading ./cryptfs.o will taint the kernel
Date: Sat, 9 Mar 2002 14:13:41 -0800 [thread overview]
Message-ID: <20020309221341.GA2533@top.worldcontrol.com> (raw)
loading ./cryptfs.o will taint the kernel: non-GPL license - LGPL
I have long thought that I understood the reasoning behind "taint" and
binary drivers.
However, cryptfs is available with complete source code, so I presume
the "undebug-able" argument doesn't apply.
So what is the big deal?
--
Brian Litzinger <brian@worldcontrol.com>
Copyright (c) 2002 By Brian Litzinger, All Rights Reserved
next reply other threads:[~2002-03-09 22:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-09 22:13 brian [this message]
2002-03-09 22:38 ` Alan Cox
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=20020309221341.GA2533@top.worldcontrol.com \
--to=brian@worldcontrol.com \
--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®