From: David Riley <oscar@the-rileys.net>
To: David Lang <david.lang@digitalinsight.com>, linux-kernel@vger.kernel.org
Subject: Re: Defective Red Hat Distribution poorly represents Linux
Date: Tue, 21 Nov 2000 16:34:08 -0500 [thread overview]
Message-ID: <3A1AEA47.ECF2D50A@the-rileys.net> (raw)
In-Reply-To: <Pine.LNX.4.21.0011211400380.2031-100000@dlang.diginsite.com>
David Lang wrote:
>
> David, usually when it turns out that Linux finds hardware problems the
> underlying cause is that linux makes more effective use of the component,
> and as such something that was marginal under windows fails under linux as
> the correct timing is used.
This is true. What I suppose would be the solution is that if faulty
hardware is found, a reduction in performance should be made. This is
already the case for things like broken PCI BIOS where one can either
set the initialization to work a different way or try to make the
machine autodetect it. I certainly approve of more effective use of any
given component, but sometimes I think it's better to offer the user a
choice in the case of faulty hardware.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-21 22:04 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-20 13:53 Defective Red Hat Distribution poorly represents Linux Charles Turner, Ph.D.
2000-11-20 14:00 ` Mohammad A. Haque
2000-11-20 14:05 ` Andreas Jaeger
2000-11-20 14:10 ` Tigran Aivazian
2000-11-20 16:13 ` Bernhard Rosenkraenzer
2000-11-20 17:18 ` Tigran Aivazian
2000-11-20 18:19 ` Mohammad A. Haque
2000-11-20 21:11 ` Ben Ford
2000-11-20 18:04 ` Charles Turner, Ph.D.
2000-11-20 18:22 ` John Jasen
2000-11-20 18:44 ` Mohammad A. Haque
2000-11-20 20:32 ` Horst von Brand
2000-11-21 21:08 ` David Riley
2000-11-21 20:43 ` Gérard Roudier
2000-11-21 21:46 ` Bob Lorenzini
2000-11-21 21:50 ` Jeff Epler
2000-11-21 22:27 ` David Riley
2000-11-21 22:31 ` Richard Torkar
2000-11-21 23:17 ` David Riley
2000-11-22 3:28 ` Jeff Epler
2000-11-22 20:35 ` David Riley
2000-11-22 11:02 ` Richard Torkar
2000-11-23 1:40 ` Was:Defective Red Hat Distribution poorly represents Linux, running with failed hardware? Richard.Reynolds
2000-11-21 21:52 ` Defective Red Hat Distribution poorly represents Linux Horst von Brand
2000-11-21 22:04 ` David Lang
2000-11-21 21:34 ` David Riley [this message]
2000-11-21 22:01 ` Horst von Brand
2000-11-21 22:11 ` Dan Hollis
2000-11-21 22:21 ` Gerd Knorr
2000-11-21 22:21 ` David Lang
2000-11-20 21:16 ` Ben Ford
2000-11-21 0:41 ` Fort David
2000-11-20 19:37 ` Mohammad A. Haque
2000-11-20 19:42 ` Andre Hedrick
2000-11-20 19:52 ` Paul Fulghum
2000-11-20 23:01 ` spam
2000-11-20 14:16 ` Gregory Maxwell
2000-11-20 14:50 ` Whiner spams linux-kernel (Re: Defective Red Hat Distribution poorly represents Linux) Jes Sorensen
2000-11-20 15:48 ` Defective Red Hat Distribution poorly represents Linux Bernhard Rosenkraenzer
2000-11-20 17:00 ` Werner Almesberger
2000-11-20 17:31 ` Jeff V. Merkey
2000-11-20 19:33 ` Frank van Maarseveen
2000-11-22 17:26 ` Anthony Liu
2000-11-20 20:15 ` Igmar Palsenberg
2000-11-21 5:53 ` Albert D. Cahalan
2000-11-21 8:16 ` Peter Samuelson
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=3A1AEA47.ECF2D50A@the-rileys.net \
--to=oscar@the-rileys.net \
--cc=david.lang@digitalinsight.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