From: Robert Love <rml@tech9.net>
To: David Schwartz <davids@webmaster.com>
Cc: jalvo@mbay.net, linux-kernel@vger.kernel.org
Subject: Re: Tainted Modules Help Notices
Date: 11 Oct 2001 21:32:24 -0400 [thread overview]
Message-ID: <1002850347.872.95.camel@phantasy> (raw)
In-Reply-To: <20011012011217.AAA27996@shell.webmaster.com@whenever>
In-Reply-To: <20011012011217.AAA27996@shell.webmaster.com@whenever>
On Thu, 2001-10-11 at 21:12, David Schwartz wrote:
> Perhaps the best solution is to develop a 'kernel module license' that
> simply requires that the source code be made available to anyone who wishes
> to debug for the purpose of debugging. Complying with the terms of the
> 'kernel module license' would give you module that don't taint the kernel.
But if we couldn't release the (fixed) source, then what is the point?
If it is not open source, why should Alan or I or anyone care to debug
it?
What we want is for users to not have a tainted kernel, so we can debug
the problem and release the results. We are interested in fixing our (=
the open source community's) problems, not others.
Robert Love
next prev parent reply other threads:[~2001-10-12 1:32 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-10 8:06 Tainted Modules Help Notices Morgan Collins [Ax0n]
2001-10-10 8:20 ` David Woodhouse
2001-10-10 8:24 ` Morgan Collins [Ax0n]
2001-10-10 8:31 ` David Woodhouse
2001-10-10 13:50 ` Keith Owens
2001-10-10 13:59 ` Alexander Viro
2001-10-10 14:01 ` Keith Owens
2001-10-10 17:30 ` Alan Cox
2001-10-10 18:18 ` David Woodhouse
2001-10-10 20:06 ` Concerned Programmer
2001-10-10 20:28 ` Morgan Collins [Ax0n]
2001-10-10 21:28 ` Keith Owens
2001-10-10 22:03 ` Anthony DeRobertis
2001-10-11 7:27 ` David Woodhouse
2001-10-10 21:17 ` Alan Cox
2001-10-10 23:02 ` Juan Quintela
2001-10-10 23:28 ` Andreas Dilger
2001-10-10 22:29 ` Rob Landley
2001-10-11 2:48 ` 2.4.11 UDF Morgan Collins [Ax0n]
2001-10-11 3:26 ` Craig Whitmore
2001-10-11 8:50 ` Tainted Modules Help Notices Andreas Ferber
2001-10-11 9:25 ` Alan Cox
2001-10-11 9:35 ` Henning P. Schmiedehausen
2001-10-11 9:41 ` Pekka Pietikäinen
2001-10-11 9:48 ` Syed Mohammad Talha
2001-10-11 10:09 ` Concerned Programmer
2001-10-11 10:37 ` Alan Cox
2001-10-11 22:42 ` David Schwartz
2001-10-11 23:40 ` John Alvord
2001-10-12 1:12 ` David Schwartz
2001-10-12 1:32 ` Robert Love [this message]
2001-10-11 12:10 ` James Sutherland
2001-10-10 14:13 ` David Woodhouse
2001-10-10 14:18 ` Alexander Viro
2001-10-10 13:10 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2001-10-10 14:06 Bonds, Deanna
2001-10-10 14:24 ` Arjan van de Ven
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=1002850347.872.95.camel@phantasy \
--to=rml@tech9.net \
--cc=davids@webmaster.com \
--cc=jalvo@mbay.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