Re: bin/54726: cksum(1) doesn't inform you of passed checks

[mlelstv%serpens.de@localhost (Michael van Elst)]

The following reply was made to PR bin/54726; it has been noted by GNATS.

From: mlelstv%serpens.de@localhost (Michael van Elst)
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: bin/54726: cksum(1) doesn't inform you of passed checks
Date: Sun, 1 Dec 2019 21:27:13 -0000 (UTC)

 edgar%pettijohn-web.com@localhost (Edgar Pettijohn) writes:
 
 > Then why does it give you human readable text for failed files? Seems 
 > like it should either do both or neither. If neither add a -v flag to 
 > get both.
 
 Apparently failures were considered important and the regular
 successes shouldn't clutter the script output. Most original
 UNIX commands work this way. GNU commands tend to be a bit more
 verbose.
 
 The original tool didn't have the check mode and it still lacks
 such a mode on Linux or other UNIX systems. It was added since the
 Linux md5sum command had something similar.
 
 But md5sum behaves differently, there you normally get OK / FAILED on
 stdout for each file and an additional summary message on stderr
 for failures. You can add a --quiet option to hide the OK output
 but keep the FAILED output.
 
 -- 
 -- 
                                 Michael van Elst
 Internet: mlelstv%serpens.de@localhost
                                 "A potential Snark may lurk in every tree."