From: Bernd Petrovitsch <bernd@firmix.at>
To: jmerkey <jmerkey@utah-nac.org>
Cc: Bernd Eckenfels <ecki@lina.inka.de>, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] DSFS Network Forensic File System for Linux Patches
Date: Thu, 01 Sep 2005 10:28:06 +0200 [thread overview]
Message-ID: <1125563286.28749.22.camel@tara.firmix.at> (raw)
In-Reply-To: <431651BC.9020108@utah-nac.org>
On Wed, 2005-08-31 at 18:56 -0600, jmerkey wrote:
> Bernd Eckenfels wrote:
> >In article <20050901012218.02c79560.diegocg@gmail.com> you wrote:
> >>I mean, nvidia people also use propietary code in the kernel (probably
> >>violating the GPL anyway) and don't do such things.
> >
> >The Linux kernel allows binary drivers, you just have to live with a limited
> >number of exported symbols and that the kernel is tainted. Which basically
> >means nobody sane can help you with corrupted kernel data structures.
[...]
> Thanks for the accurate and reasonable response. I object to the use of
> the word "tainted". This implies the
> binary code is somehow infringing. I would suggest changing the word to
It is infringing the debuggability seriously outside the exclusive club
of people with access to the secret source of these drivers.
So "tainted" pretty much explains quite well the situation as seen from
the kernel side.
> "non-GPL" or "Vendor Supported" since
> this is more accurate. Just a suggestion.
"non-GPL" is clearly wrong. First the kernel source it self stays GPL
independent for whatever legal people write into othre license
agreements, second the license of your source *could be* (in theory) GPL
if the authors wanted it and - in some cases - the source *is* actually
GPL even if the authors doesn't want it.
And "Vendor supported" must be (if you really want to be accurate) "At
best it is vendor supported if the vendor exists at the moment and for
whatever said vendor thinks support is. The contact address for said
vendor is <name>, <street>, <phnoe>, <mobile>, <email>, <homepage>.
Please do not ask the free software community if you have any problem
with the Linux kernel."
So please put this in your proprietory module and print it whenever it
makes sense since the necessary contact data is only known by you.
The point is: There is no such concept as "vendor" as it would or could
be seen in the commercial and/or legal world if you download the kernel
source from kernel.org.
Bernd
--
Firmix Software GmbH http://www.firmix.at/
mobil: +43 664 4416156 fax: +43 1 7890849-55
Embedded Linux Development and Services
next prev parent reply other threads:[~2005-09-01 8:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-31 16:33 Jeff V. Merkey
2005-08-31 18:32 ` Rik van Riel
2005-08-31 17:27 ` Jeff V. Merkey
2005-08-31 18:58 ` Arjan van de Ven
2005-08-31 18:00 ` Jeff V. Merkey
2005-08-31 21:28 ` Valdis.Kletnieks
2005-08-31 20:23 ` Jeff V. Merkey
2005-08-31 20:27 ` Jeff V. Merkey
2005-08-31 23:22 ` Diego Calleja
2005-08-31 22:50 ` jmerkey
2005-09-01 0:36 ` Bernd Eckenfels
2005-09-01 0:33 ` Bernd Eckenfels
2005-09-01 0:56 ` jmerkey
2005-09-01 1:44 ` jmerkey
[not found] ` <67029b1705083120142c0c1dea@mail.gmail.com>
2005-09-01 3:19 ` Zhou Yingchao
2005-09-01 7:12 ` Lincoln Dale
2005-09-01 7:45 ` Vojtech Pavlik
2005-09-01 10:23 ` Alan Cox
2005-09-01 8:28 ` Bernd Petrovitsch [this message]
2005-09-01 10:15 ` Alan Cox
2005-09-03 21:26 ` Bernd Eckenfels
2005-09-04 8:45 ` Alan Cox
2005-09-05 20:19 ` Bernd Eckenfels
2005-08-31 21:49 ` Jose Luis Domingo Lopez
2005-09-01 21:11 ` Alistair John Strachan
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=1125563286.28749.22.camel@tara.firmix.at \
--to=bernd@firmix.at \
--cc=ecki@lina.inka.de \
--cc=jmerkey@utah-nac.org \
--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®