Stoker wrote:
> Just about to burn a new SD card with the CSOS F19 (RELEASE 1) DualLite
> CPU image downloaded via the http://www.communitysqueeze.org/ web page
> and I appear to be getting a mis-match between the MD5 checksum
> calculated by Win32 Disk Imager and the check sum published on the web
> page (I have checked and double checked that I'm looking at the correct
> checksum).
>
> Disk Imager: 74cc01f6ab223440261bc1ba7771b173
> Web page: 096a1410ec7b17ceedc0dc5e0cf8f5b3
>
> Never used MD5 before so I might have done something wrong, but I'd
> expect the two values to be the same, is that correct?
Code:
--------------------
$ md5 CSOS-Wandboard-Dual-F19-R1-20130811-1.img.7z
MD5 (CSOS-Wandboard-Dual-F19-R1-20130811-1.img.7z) =
096a1410ec7b17ceedc0dc5e0cf8f5b3
$ md5 CSOS-Wandboard-Dual-F19-R1-20130811-1.img
MD5 (CSOS-Wandboard-Dual-F19-R1-20130811-1.img) =
74cc01f6ab223440261bc1ba7771b173
--------------------
The good news is that your decompressed image is valid, since it agrees
with the one I calculated above. However, the published MD5 checksum
applies to the .7z compressed image *before* decompression.
----------------------
"Dreamer, easy in the chair that really fits you..."
------------------------------------------------------------------------
dsdreamer's Profile: http://forums.slimdevices.com/member.php?userid=12588
View this thread: http://forums.slimdevices.com/showthread.php?t=99395
_______________________________________________
unix mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/unix
