I have another idea: I tried to run 'md5sum -c md5sum.txt' from a d-i shell (last time, when checking the CD, I did it using the GNU md5sum, on my main computer). Here is what I got:
/cdrom # md5sum -c md5sum.txt md5sum: -c: No such file or directory c53f3ea0710b9e77049e9187af77baac md5sum.txt /cdrom # I suppose the BusyBox md5sum included on the d-i CD is buggy. It doesn't explain why my MMX computer can't read libc-udeb, but it maybe explains why integrity test fails. Nicolas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
