Joe Gidi wrote:
Joe,
I think the MD5 file was out of sync in the past week.
I downloaded the i386 install44.iso a few days ago. I just checked the
file I downloaded, and it does have the "correct" MD5
(f87b839db833380f41f02bd7fffb2d27) according to what you posted.
*But* on the day I downloaded it, I was very sure the MD5 file
on the FTP site was advertising a different hash.
Like you, I thought I had a bad ISO, so I downloaded the ISO file
from a different mirror, but the second ISO file had the same hash as
the first.
So the MD5 file was either "ahead" or "behind." Since the install44.iso
file I downloaded was dated Sep 20, the MD5 file was probably behind.
Or maybe it's just one of those transient things that happen when
FTP sites are being mirrored.
Or maybe you and I are both crazy. :)
Lawrence
| H. Peter Anvin | Re: [RFC 00/15] x86_64: Optimize percpu accesses |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Eric W. Biederman | Remaining straight forward kthread API conversions... |
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
| David Miller | [GIT]: Networking |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Frans Pop | svc: failed to register lockdv1 RPC service (errno 97). |
git: | |
