agetty: add -h and -V options

Signed-off-by: Sami Kerola <kerolasa@iki.fi>
dmesg: fix usage() output consistancy

Possible facilities and levels are meant to be printed to same file as
the rest of the usage output.

Signed-off-by: Sami Kerola <kerolasa@iki.fi>
fsfreeze: tell user when mandatory option is not specified

This commit also removes use of internal magic values by replacing them
with a enum definition.

Signed-off-by: Sami Kerola <kerolasa@iki.fi>
losetup: allow -j option argument to be relative path

Signed-off-by: Sami Kerola <kerolasa@iki.fi>
lscpu: fix error message

Signed-off-by: Sami Kerola <kerolasa@iki.fi>
partx: remove deprecated option from usage()

The fact that -l, --list is deprecated will remain in manual page till
unforeseeable future.  Meanwhile the usage() can be made shorter.

Signed-off-by: Sami Kerola <kerolasa@iki.fi>
setarch: add option to list settable architectures

Signed-off-by: Sami Kerola <kerolasa@iki.fi>
setterm: fix various color option argument lists

The lists did not have correct colors in usage().  Because the usage()
had to be fixed, it is best to make the output easy for translators to
work with.

Signed-off-by: Sami Kerola <kerolasa@iki.fi>
vipw: add usage() function

Signed-off-by: Sami Kerola <kerolasa@iki.fi>
chrt: make command syntax easier to understand in usage()

And mention in manual that the default is referring to the internal
default of this command, not the Linux system default.  Manual page
example also tries to be a little more complete how to use the command.

Signed-off-by: Sami Kerola <kerolasa@iki.fi>
logger: make local sockets to try both stream and datagram

When journald, from systemd, is in use logger gave following error.

$ logger --socket /dev/log test logger: connect /dev/log: Protocol wrong
type for socket

The journald supports only AF_DGRAM, and nothing else.  Support for
AF_STREAM sockets was dropped because it messed up message ordering.

From an users point of view necessity to add --udp (UNIX(TM) Datagram
Protocol?) option when talking to syslog via unix socket felt confusing
and wrong.  The command should know what is the socket type, and silently
use the correct one, unless the type is explicitely defined.

CC: Karel Zak <kzak@redhat.com>
Adviced-by: Lennart Poettering <lennart@poettering.net>
Signed-off-by: Sami Kerola <kerolasa@iki.fi>