On Thursday 23 October 2003 08:47 am, HaywireMac wrote:
> On Thu, 23 Oct 2003 08:31:46 -0500
>
> Tom Brinkman <[EMAIL PROTECTED]> uttered:
> > I did a fresh install of 9.2 a few days ago. Utterly
> > boring, absolutely no problems or issues.
>
> Good to hear, Tom. I hope you didn't take me the wrong way with
> the CD issue thang, but I don't usually like my hardware bein'
> called junk, knowwhatimsayin'?
No, unless you made it yourself. 'Junk' is no reflection on you
other than your choice to buy it, and then only if the info was
available at the time to avoid it. Bottom line is, due to hardware
manufacturer's close cooperation with M$, the continuing
degradation of hardware quality over the years (also due a lot to
M$ influence, ie, win-hardware), customer demand for cheaper
hardware, users willingness to accept hardware that needs closed
source proprietary drivers to function ....finding suitable
hardware for use with Linux is going to continue to be a major
problem, and often trial'n error.
> BTW, I'm still not finding that "blacklist" on kernel.org... ;-)
http://www.google.com/search?q=linux%20hardware%20blacklist&ie=UTF-8&oe=UTF-8
Should get ya started.
Most distro's also use blacklists. When a particular hardware
item, or combination is seen, things like DMA for drives is
disabled, acpi=ht, noapic, work arounds in the various init files,
etc., are used. Not foolproof, but at least an attempt to
accommodate all the various hardware combos out there. Problem is a
lot like Winsux viruses tho. Nothing can be done until after the
problem has already surfaced and it's too late.
If more people were willing to d/l and install the cooker betas
and RC's, then more hardware problems could be solved. Too many
wait till the last RC, and then it's way too late. Most are afraid
of betas, but the truth is there is no such thing as a 'final'
version of Linux (or any OS). Linux has been a work in progress
ever since Linus released his first kernel. Same holds true for GNU
software. And specially in regards to hardware, they're chasing a
moving target.
BTW, it'll be very interesting to see how a CD can break a
CDrom. My initial impression is that it's the CDrom drives or it's
firmwares fault. I suspect the drive's firmware got corrupted by
somethin it wasn't able or designed to handle. In that case the
drive should have some kind of self protection, and refuse to read
the CD. But it does remind me of something I vaguely remember, copy
protected CD's breaking computer systems some time ago. Even sloppy
hardware Windoze boxes.
--
Tom Brinkman Corpus Christi, Texas
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
