> Possibly the shell is expanding wild cards, but md5sum is only picking up
> the first one for some reason, like lazy programmers. If so, then the
> problem lies with the md5sum maintainers, not Tom. All he does, by and
> large, is package the programs.
Not exactly.
The shell expands the wildcards.
I wrote the md5sum in question, and I am the maintainer of it. In this
case, it is NOT just a packaged GNU md5sum or whatever is common.
md5 is not picking up more than the first one, because I made a design
decision that users of tomsrtbt could do:
for X in *;do md5sum $X;done
Maybe someday I'll fix it. Here is the entire program:
#!/bin/sh
[ $# -gt 0 ] && exec 0<$1
tomshexd -mn
So, you see, it is actually just a convenience to allow executing the new
md5sum capability of tomshexd in a sort of normal way, but, tomshexd is
strictly stdin/stdout. FYI, tomshexd can produce md5sums *in addition* to
whatever other output it is called on to create.
It wasn't exactly lazyness that caused me to omit multipe md5sums in one
invokation. I'll put it on the list to do something with maybe someday as
an extremely low priority.
-Tom
