Re: MD5 listing format

On Sun 28 Nov 2021 at 23:40:43 (+0100), Thomas Schmitt wrote: > David Wright wrote: > > My solution will be to rename or delete the file, > > after adding code to detect any future occurrences. > > Or you could avoid to show md5sum a file name. > > path=...as.weird.as.is... > md5sum <"$path"

Re: MD5 listing format

Hi, David Wright wrote: > My solution will be to rename or delete the file, > after adding code to detect any future occurrences. Or you could avoid to show md5sum a file name. path=...as.weird.as.is... md5sum <"$path" will yield something like b8ce6ed30aa67e94ad9276c9ac2bbc50 - If you

Re: MD5 listing format

On Sun 28 Nov 2021 at 20:21:15 (+0100), Thomas Schmitt wrote: > David Wright wrote: > > I was taken by surprise by the following output from md5sum: > > \adfc1d2f1b1d6c7fcaa51e857c1a6f68 special/C:\\nppdf32Log\\debuglog.txt > > It's a feature, not a bug. (tm) > > > https://www.gnu.org/softwar

Re: MD5 listing format

Hi, David Wright wrote: > I was taken by surprise by the following output from md5sum: > \adfc1d2f1b1d6c7fcaa51e857c1a6f68 special/C:\\nppdf32Log\\debuglog.txt It's a feature, not a bug. (tm) https://www.gnu.org/software/coreutils/manual/html_node/md5sum-invocation.html "Without --zero, if

Re: MD5 listing format

On Sun, Nov 28, 2021 at 12:57:00PM -0600, David Wright wrote: > I was taken by surprise by the following output from md5sum: > $ echo special/* > special/C:\nppdf32Log\debuglog.txt special/same-contents > $ md5sum special/* > \adfc1d2f1b1d6c7fcaa51e857c1a6f68 special/C:\\nppdf32Log\\debuglog.txt >

MD5 listing format

I was taken by surprise by the following output from md5sum: $ ls -Glg special/ total 8 -rw-r--r-- 1 144 Oct 24 2014 'C:\nppdf32Log\debuglog.txt' -rw-r--r-- 1 144 Oct 24 2014 same-contents $ echo special/* special/C:\nppdf32Log\debuglog.txt special/same-contents $ md5sum special/* \adfc1d2f1b1d