Re: New error with backslashes in filenames

2007-10-14 Thread Dal
Hi, this is probably not a error. You can see it in md5sum.c in coreutils (I have 5.97): == md5sum.c == 638 /* Output a leading backslash if the file name contains 639 a newline or backslash. */ 640 if (strchr (file, '\n') || strchr (file, '\\')) 641

New error with backslashes in filenames

2007-10-14 Thread Marty
I get the following new error on my recently upgraded Etch system: $ touch "test\file" $ md5sum "test\file" \d41d8cd98f00b204e9800998ecf8427e test\\file Note the leading backslash. This is some thing I haven't seen before, and it breaks some of my maintenance scripts which don't have control