From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: davids@webmaster.com (David Schwartz)
Cc: justin@soze.net (Justin Guyett), linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.9-ac6
Date: Wed, 5 Sep 2001 12:55:51 +0100 (BST) [thread overview]
Message-ID: <E15ebHb-0005ew-00@the-village.bc.nu> (raw)
In-Reply-To: <NOEJJDACGOHCKNCOGFOMGECJDLAA.davids@webmaster.com> from "David Schwartz" at Sep 05, 2001 02:53:24 AM
> I hope I'm not overreacting. It just seems that tainting based upon
> licensing doesn't do what's really wanted, which is to make sure that the
> user has the source and those who wish to debug can also get the source. The
> first part of that is really easy to check directly (and you catch stupidity
> due to mismatched versions, SMP versus UP, and so on). I think it makes
> sense to 'force' the user to replicate the bug after having cleanly compiled
> the module. This ensures that at least he has the source.
The goal is very simple. It is to make the information available. What
people choose to do with that information and such bug reports is up to
them. Similarly the policy is in user space modutils.
Unfortunately I get so many bug reports caused by the nvidia modules and
people lying when asked if they have them loaded that some kind of action
has to occur, otherwise I'm going to have to stop reading bug reports from
anyone I don't know personally.
I am not prepared to be an unpaid Nvidia support goon.
Alan
next prev parent reply other threads:[~2001-09-05 11:51 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-03 1:50 Alan Cox
2001-09-03 2:51 ` Keith Owens
2001-09-03 3:08 ` Dave Jones
2001-09-03 13:05 ` Andrea Arcangeli
2001-09-03 13:21 ` Alan Cox
2001-09-05 1:51 ` Keith Owens
2001-09-05 3:30 ` David Schwartz
2001-09-05 3:50 ` Keith Owens
2001-09-05 5:16 ` David Schwartz
2001-09-05 5:39 ` Alan Shutko
2001-09-05 18:46 ` David Schwartz
2001-09-05 5:52 ` H. Peter Anvin
2001-09-05 5:56 ` Aaron Lehmann
2001-09-05 7:03 ` David Schwartz
2001-09-05 7:09 ` David Schwartz
2001-09-05 9:50 ` Alex Bligh - linux-kernel
2001-09-05 9:57 ` David Schwartz
2001-09-05 12:50 ` christophe barbé
2001-09-05 13:06 ` Alan Cox
2001-09-05 13:14 ` Alex Bligh - linux-kernel
2001-09-05 13:23 ` christophe barbé
2001-09-05 14:05 ` Henning P. Schmiedehausen
2001-09-05 7:18 ` Aaron Lehmann
2001-09-05 7:19 ` David Schwartz
2001-09-05 9:41 ` Justin Guyett
2001-09-05 9:53 ` David Schwartz
2001-09-05 10:21 ` Justin Guyett
2001-09-05 11:55 ` Alan Cox [this message]
2001-09-05 18:46 ` David Schwartz
2001-09-05 18:54 ` Alan Cox
2001-09-05 22:09 ` Linux 2.4.9-ac6 (really about tainting) David Schwartz
2001-09-05 12:07 ` Linux 2.4.9-ac6 Alan Cox
2001-09-05 12:16 ` Arjan van de Ven
2001-09-05 12:23 ` Jan-Benedict Glaw
2001-09-05 14:36 Thomas Foerster
2001-09-06 19:23 ` Camiel Vanderhoeven
2001-09-06 20:14 ` 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=E15ebHb-0005ew-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=davids@webmaster.com \
--cc=justin@soze.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
all inboxes | Powered by JetHome®