Make test more verbose to see commands and error messages in output.
This makes it easier to debug if something fails. Add some ${SUDO}
in a way that this tests runs as root or regular user with and
without SUDO set.

Make use of the existing bsd.regress.mk logic to flag root only targets,
allowing the actual tests to become less repetitive.

ok bluhm@

Add a regress test for the chflags problem analogous to the chmod bug
found by Christopher Wellons (see chmod.c r1.41).

Add tests for chmod's interaction with symlinks: missing tests for -h and
add tests for the regression introduced in chmod.c r1.33 that transferred
the permissions from the link to the target file in some circumstances.
There are no tests for chflags since I couldn't come up with testcases
without undesirable side-effects like breaking make clean.

Four of these tests fail and will be fixed in the upcoming r1.40 to chmod.

Prompted by a bug report from Christopher Wellons

First stab at regression test for chmod (and chflags, chgrp and chown
which are the same binary). This is supposed to exercise all syscalls
paths through those tools and not a comprehensive regression test.

Add a regress test for the chflags problem analogous to the chmod bug
found by Christopher Wellons (see chmod.c r1.41).

Add tests for chmod's interaction with symlinks: missing tests for -h and
add tests for the regression introduced in chmod.c r1.33 that transferred
the permissions from the link to the target file in some circumstances.
There are no tests for chflags since I couldn't come up with testcases
without undesirable side-effects like breaking make clean.

Four of these tests fail and will be fixed in the upcoming r1.40 to chmod.

Prompted by a bug report from Christopher Wellons

First stab at regression test for chmod (and chflags, chgrp and chown
which are the same binary). This is supposed to exercise all syscalls
paths through those tools and not a comprehensive regression test.