Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com X-Server-Uuid: 7edb479a-fd89-11d2-9a77-0090273cd58c Message-ID: <03781128C7B74B4DBC27C55859C9D7380126879A@es06snlnt> From: "Arms, Mike" To: "'cygwin AT cygwin DOT com'" Subject: 1.3.2: Bug in md5sum.exe with binary files Date: Tue, 5 Jun 2001 18:20:19 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) X-Filter-Version: 1.3 (sass165) X-WSS-ID: 1703A8CE504505-01-01 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Using the latest (as of 2001/06/05) update of Cygwin, running 'md5sum -c md5.sum' produces mostly failed checksums when checking against binary files. However, when running 'md5sum *', the checksums produced are identical to those in the md5.sum file except that each file has an asterisk '*' prepended to it. When the md5.sum file is editted to add an asterisk before each filename, 'md5sum -c md5.sum' produces all 'OK' results. This looks to be an error when md5sum is checking (-c option) binary files. This occurs irregardless of whether or not the CYGWIN environment variable is set in cygwin.bat to binmode. Note: the '-b' option cannot be used with the '-c' option. My specific test case was with the Cygwin-XFree86 files for download. There is an md5.sum file there which works fine when I run a Perl based MD5 checker. And like I said, you can add an '*' before each file in that md5.sum and then the cygwin 'md5sum -c md5.sum' command works fine. ftp://ftp.sunsite.utk.edu/pub/cygwin/xfree/xc-4-binaries/4.1.0/ -- Mike Arms marms AT sandia DOT gov -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple