I downloaded slackcurrent today, and check it against CHECKSUMS.md5 from another mirror. Some mismatches was found, here is the detail:
md5sum -c CHECKSUMS.md5 2>&1 | grep FAILED
Code:
./kernels/zipslack.s/System.map.gz: FAILED
./kernels/xfs.s/System.map.gz: FAILED
./kernels/speakup.s/System.map.gz: FAILED
./kernels/scsi3.s/System.map.gz: FAILED
./kernels/scsi2.s/System.map.gz: FAILED
./kernels/scsi.s/System.map.gz: FAILED
./kernels/sata.i/System.map.gz: FAILED
./kernels/raid.s/System.map.gz: FAILED
./kernels/pportide.i/System.map.gz: FAILED
./kernels/old_cd.i/System.map.gz: FAILED
./kernels/lowmem.i/System.map.gz: FAILED
./kernels/jfs.s/System.map.gz: FAILED
./kernels/ibmmca.s/System.map.gz: FAILED
./kernels/bareacpi.i/System.map.gz: FAILED
./kernels/bare.i/System.map.gz: FAILED
./kernels/ataraid.i/System.map.gz: FAILED
./kernels/adaptec.s/System.map.gz: FAILED
./extra/source/ham/baken/prototype.map: FAILED
Can anybody confirm this? The problem is I found the CHECKSUMS.md5 files from those two sites are actually identical. Is it just a stale CHECKSUMS.md5 or something bad happen? or just my proxy plays with me? There's no gpg signature for these files so I think CHECKSUMS.md5 is the only way to verify their integrity.
Mirrors sites I used:
http://mirrors.easynews.com/linux/sl...kware-current/
http://mirror.switch.ch/ftp/mirror/s...kware-current/
Checked at:
2005-03-29 9:30 UTC