Bryan J Smith wrote:
On Wed, 2009-11-18 at 11:18 -0500, Chris Lumens wrote:
Problem is that media check does actually catch problems, and not
running it means we're going to get a lot more bugs about completely
random i/o errors caused by bad media. I'd be really opposed to
disabling it by default.
I have to second this. For noobs, I like the media test default ...
period. I would argue that 9 out of 10 install issues at InstallFests
have been errors in the media, disc incompatibility between the drive
firmware that recorded it from the drive reading it, etc...
I've long tracked (nearly 15 years now) the quirks and differences
between Matsushita, Pioneer and Sony/Philips firmware. It's bad
enough in the differences between -R technologies, but it gets worse
when you start looking at non-"record-like" technologies like -RW, +RW
and +R (which is really +RW). I even half-seriously call Sony/Philips
CD-RW "CAV" re-write as CD+RW for many reasons (including what it does
to a CD-RW "CLV" disc when someone doesn't check).
Even if a disc is recorded and tested in one drive and works in other
drives of the same firmware, there can be differences in another. Even
LG's SuperMulti firmware based on multiple licenses, which does
everything and could be considered one of the most universally
compatible, can result in discs that some drives and their firmwares
just don't like.
If you're an expert, you use a network install anyway. I have a PCMCIA
card I throw into my T60 as eth1 that brings up a DHCP and services TFTP
and Apache only when it exists, precisely for network booting all sorts
of releases.
Could get rid of media tests completely by using network based
installers, like boot.kernel.org ;-)
- John 'Warthog9' Hawley
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
