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 From: "Mark Paulus" To: "cygwin AT cygwin DOT com" Date: Sat, 17 Nov 2001 15:53:53 -0700 Reply-To: "Mark Paulus" X-Mailer: PMMail 2000 Professional (2.10.2010) For Windows 2000 (5.1.2600) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Who "fixed" md5sum?? Message-Id: Hi, I have a question about md5sum. It seems like in one of the not too distant releases of textutils, the md5sum program altered it's behaviour. Before the change, it would act like the debian/linux variety, in that if you would do an md5sum < you would get a result, and that would be all, e.g.: This is the result from my debian box..... mgpaulus AT testbox1:/smbapps/cygwin.pkg$ md5sum < setup.exe d91a97dcd67b7cb9c6aaa408cf431b01 Here's the same result, except from my cygwin environment: $ md5sum < setup.exe d91a97dcd67b7cb9c6aaa408cf431b01 *- My problem is the little '*-' at the end... I have several unix ported scripts that run md5sum, and expect only the significant md5sum digits, and the trailing stuff is causing all the scripts to break. Would it be possible to get either 1) a rational for adding the trailing stuff, and making it act differently than it's un*x cousin; and/or 2) an ability to turn that "feature" off, if everyone else absolutely requires it?? Thanks.... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/