Scripts exist that may call one of the multi-binary entry points
with argument 0 set to some other value than the name of the entry
point.

One example is the Open vSwitch testsuite which makes use of
/bin/true as an argument to the bash builtin `exec` to check
whether it supports the '-a' argument [0].

In this situation coreutils will print usage on standard output,
which makes unnecessary noise.

Printing usage on standard error, which is customary for other
tools, allows the script to succeed.

0: https://github.com/openvswitch/ovs/blob/28064e9fa50d/tests/ovs-macros.at#L199
Signed-off-by: Frode Nordahl <[email protected]>

At present, the `cat` command unexpectedly prints an error message
when it receives a broken pipe error.

As an example, there are many workflows that make use of `cat` and
`head` together to process only part of the data.  The `head`
command will stop reading after a configured number of bytes or
lines, subsequently exposing `cat` to a broken pipe condition.

Said workflows may fail when they unexpectedly get error messages
in their output.

Suppress broken pipe errors.

Signed-off-by: Frode Nordahl <[email protected]>