Bugs in sed and uudecode? md5sum too?

["GregMo" <cygwin at wyldryde dot net>]

If you will, have a look at these two commands performed on both a cygwin
install and a redhat install, on the exact same file
(http://216.40.230.24/part.1)

####  CygWin
[GregMo@picard: ~/.brag/all-servers/unfinished/1082426201]$ cat part.1
|sed -e {/^$/d} |uudecode

[GregMo@picard: ~/.brag/all-servers/unfinished/1082426201]$ md5sum part.1
915e506f04e8618aff6ab0e9f37a80d9 *part.1


####  RedHat
[wamphyre@axihost: ~/tmp]$ cat part.1 |sed -e {/^$/d} |uudecode
sed: -e expression #1, char 7: Extra characters after command
uudecode: stdin: No `begin' line

[wamphyre@axihost: ~/tmp]$ md5sum part.1
915e506f04e8618aff6ab0e9f37a80d9  part.1

The project here is porting a script used daily on redhat to cygwin.  It
turns out there are quite a few glitches, and this is the biggest so far, so
thought we'd report it.  The two problems here are both with error
reporting.  You'll note that sed on a linux machine returns an error when
this command is tried, whereas cygwin doesn't.  With sed being issued before
uudecode, on the linux machine, uudecode isn't getting the output so it
returns no begin line.  When the output is piped directly to uudecode on
linux an error is returned about the 'end' line, or lack thereof, but no
error on cygwin.  This is nightmarish for debugging.

Additionally, have a look at the md5sum output from cygwin.  I happen to
know that an '*' before a file name in a checksum doesn't hinder using those
sums on other systems, but that doesn't make it not a bug, does it?  <g>

Cheers,
Greg


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.659 / Virus Database: 423 - Release Date: 4/15/2004


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/