Ken.Fuchs@bench.com <Ken.Fuchs@bench.com> (2009-08-21): > Package: cdrom-checker > Version: 1.15 (lenny) > > Boot method: CD-ROM using Lenny CD1 > Image version: > http://laotzu.acc.umu.se/debian-cd/5.0.2a/i386/iso-cd/debian-502a-i386-C > D-1.iso > Date: 2009-08-21 15:30 UTC > > Machine: Gateway E-4200 > Processor: Pentium II 350MHz > Memory: 128MB > > Comments/Problems: > > MD5 check of the CD appears to abort on detecting the first MD5 > mismatch. > > When the progress meter was at about 78% complete, cdrom-checker > displayed an MD5 error for grub-pc, and I pressed <Enter> key for the > <Continue> prompt. cdrom-checker immediately asked "Check the integrity > of another CD-ROM?" without any mention of the rest of the packages on > the current CD-ROM that have presumably not been checked yet. > > cdrom-checker should verify the MD5 checksum of all packages on the CD, > provide the number of packages with MD5 errors, if any, and at the > user's option list all packages with MD5 checksum errors. > > cdrom-checker could also make at least a terse suggestion about what the > user should do about the MD5 checksum errors it detected. > > Serious failure of cdrom-checker: The user may assume that the one MD5 > checksum error that cdrom-checker reported is the only one on the CD. > The user may rightly or wrongly assume he won't need the package with > the MD5 error and that it is the only package with an MD5 error and > proceed with the installation. Hi, I'm not sure I agree. As far as I can tell, if there's a single error the CD image shouldn't be trusted, period. I'm not sure how it would help to know how badly broken the CD is… Mraw, KiBi.
Attachment:
signature.asc
Description: Digital signature