Dear W. Limmer,

I can reproduce the output you sent.

I examined the md5sum documentation, and it is indeed incomplete.  "For 
each file, `md5sum' outputs the MD5 checksum, a flag indicating binary or 
text input file, and the filename. " 

It seems clear that this whole backslashing thing is done in order to 
handle the case of a filename that contains a newline (since the format 
uses newlines as terminators), and once that's in place, to handle the 
case of a filename that contains the string "\n".  (I looked in the source 
code, src/md5sum.c, to check.)

maintainer(s): Does it make sense for one of us to add documentation on 
the file format output by md5sum to the information on the texinfo page?

--Steve 






"W. L." <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
10/07/2003 04:26 PM
 
        To:     [EMAIL PROTECTED]
        cc: 
        Subject:        md5sum: Output format error on files with 
backslash in their names


Dear Team,

using md5sum on files with a backslash in their filenames 
gives an error in the output file format: A waste backslash
is output at the beginning of the line.

Also the backslashes themselves are quoted: Bug or feature?

Please check following example:

> md5sum ../div/�ble\ Filenamen/*
\45bb8963e53c01e2fd6f926bc15f0553  ../div/�ble Filenamen/with\nLinefeed
\d41d8cd98f00b204e9800998ecf8427e  ../div/�ble Filenamen/with \\ Backslash
\d41d8cd98f00b204e9800998ecf8427e  ../div/�ble Filenamen/with \\\\ 
Backslashes
a6a218b4d55f251551f21ac351bded8e  ../div/�ble Filenamen/���?
...

Best regards,
W. Limmer



_______________________________________________
Bug-coreutils mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-coreutils




_______________________________________________
Bug-coreutils mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-coreutils

Reply via email to