First, let's look at one of the simplest examples:
$ md5sum./1/iamcdrom.iso./2/iamcdrom.iso
773682e3494b6155855dd580bef8cb04./1/iamcdrom.iso
34d75a13d98b245c2a32a0bf816abb36./2/iamcdrom.iso
More detailed options are as follows:
$ md5sum--help
usage:md5sum [OPTION] ... [FILE] ...
Print or check MD5 (128-bit) checksums.
With no file, or when file is-, read standard input.
-B,--binary read in binary mode
-C,--check read MD5 sums from the FILEs and check them
-T,--text read in text mode (default)
I still recommend binary binary transmission
Production line of the burning file, due to problems such as large quantities, transmission process can not have any errors.
and are generally binary files. (such as improper setting of FTP tool: such as text format or binary transmission difference)
Of course, you generate the MD5 number, the most important thing is to use the time to verify:
md5sum youfile > Youfile.md5
Md5sum-c YOU.MD5
Give me a chestnut:
echo Hello > Hello.txt
md5sum hello.txt > Hello.md5
Md5sum-c HELLO.MD5
Hello.txt:OK (OK is what we want to see)