![]() Registered Member ![]()
|
Downloaded/installed the ktorrent 2.0.3 i586 rpm for Suse 10.1 from the download page on this site. After 8 hours of download time for the Suse 10.2 i386 Beta2 DVD iso the calculated checksum did not compare with the published one. This is the first time I have used a bittorrent client AND the VERY FIRST time I have ever gotten a bad checksum after downloading an iso file. The bittorrent file was downloaded from mirrors.kernel.org. What gives? Any ideas out there?
|
![]() Registered Member ![]()
|
|
![]() Registered Member ![]()
|
Thanks for your input Ivan. Ran the integrity check and there were no errors - all 16,319 chunks were good. Any other suggestions? I am NOT about to do another download based on what I have seen so far. BTW, is 8 hours normal for a 4GB bittorrent download? I could have downloaded the iso file (had there been one) directly in about 1.5 hours from the ftp site at mirrors.kernel.org.
|
![]() Registered Member ![]()
|
Ivan, please forgive my ignorance (I had said this was my FIRST bittorrent download). The published md5sum was for the torrent file - NOT the iso file. There was no published md5sum for the iso. Do I just assume it is good because I ran the integrity check? I have nothing else to compare to.
|
![]() Registered Member ![]()
|
That really depends on the health of the swarm, but GNU/Linux iso's generally are pretty fast i'd say.
I'd say yes you could assume it's ok, an extra check outside KTorrent of course wouldn't do any harm, but if there isn't any i personally just stick to the hash verification. (after some heavy duty searching and a surrender of source ![]() |
![]() Registered Member ![]()
|
Registered users: Bing [Bot], Evergrowing, Google [Bot]