setting errno and then not exiting isn't safe

doing a chmod on a directory causing a cycle is probably the
right thing to do

check for fts_read error

do some more error checking on the octal value

POSIX 1003.2B/D9 symbolic links

handle all of the 'weird' strings
check only the first two chars, so that long perm specs (e.g. "-xr") are OK.
From: "Chris G. Demetriou" <cgd@postgres.Berkeley.EDU>

handle first argument of -r,o=rw, for example

4.4BSD snapshot (revision 8.1); add 1993 to copyright

don't set FTS_NOSTAT, because don't want to "chmod" symbolic links
From: Theo Deraadt <deraadt@sun-lamp.cs.berkeley.edu>

use err(3) functions, minor cleanups

Added -Hh options.

fts_statb -> fts_statp

don't permit illegal file modes; lots of minor ANSI/cleanup

fts(3) now sets errno correctly, FTS_DNX no longer exists

-f is longer documented; left for compatibility

put in rest of fts(3) error returns

new fts routine names

FTS_MULTIPLE is gone

new copyright notice

new structure names for fts

string.h is ANSI C include file

parenthetical mistake

new version of get/setmode

fix errno for ANSI variable scopign

from scratch, using fts(3) and setmode(3) and the POSIX man page