--On Wednesday, April 3, 2002 5:50 PM -0700 Julian M Catchen
<[EMAIL PROTECTED]> wrote:
> I have run across this problem and it was caused by the different line
> endings in Linux/Windows files. Windows files end their lines with a
> CRLF sequence ("\r\n"), while Linux only uses LF ("\n"). So, when the
> md5sum is reading the md5 file with the checksums in it, the extra "\r"
> makes it think there is another non-existance file listed.
Yes, generally it is DOS line endings that cause md5sum to read filenames
incorrectly.
The easiest way I've found to deal with it is to use the "flip" utility.
Info is available at <http://ccrma-www.stanford.edu/~craig/utility/flip/>
or if you use Debian Linux, try "sudo apt-get install flip". After that
you can do "flip -u *.txt *.md5" where necessary to Unixify your text files.
Alternatively if you use ncftp you can issue this command to let NcFTP know
that MD5 files are text, so that it will give you UNIX type files
automatically:
"set auto-ascii
|.txt|.asc|.html|.htm|.css|.xml|.ini|.sh|.pl|.hqx|.cfg|.c|.h|.cpp|.hpp|.bat
|.m3u|.pls|.md5|"
(be sure to remove the linebreak if you're copying and pasting)
cheers,
Mike
_______________________________________________
etree.org etree mailing list <[EMAIL PROTECTED]>
http://mail.etree.org/mailman/listinfo/etree
Need help? Ask <[EMAIL PROTECTED]>
