setting errno and then not exiting isn't safe
doing a chmod on a directory causing a cycle is probably theright thing to do
check for fts_read error
better wording
do some more error checking on the octal value
POSIX 1003.2B/D9 symbolic links
handle all of the 'weird' stringscheck only the first two chars, so that long perm specs (e.g. "-xr") are OK.From: "Chris G. Demetriou" <cgd@postgres.Berkeley.EDU>
add 'permcopy' chars to the accepted perm listexplain what they arecorrectly explain the operation of "-x", etc.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
garmmer nits
don't set FTS_NOSTAT, because don't want to "chmod" symbolic linksFrom: Theo Deraadt <deraadt@sun-lamp.cs.berkeley.edu>
4.4BSD snapshot (revision 8.1)
use err(3) functions, minor cleanups
on second thought, make it symlink(7)
add symlin(1)
Added -Hh documentation.
Added -Hh options.
fts_statb -> fts_statp
don't permit illegal file modes; lots of minor ANSI/cleanup
.Os change
add POSIX/IEEE contribution notice
fts(3) now sets errno correctly, FTS_DNX no longer exists
upgrade to new -mdoc macros & rip out -f flag
123