Bruce Evans ccee498fca Backed out previous commit. chown(8) doesn't follow symlinks by ... default, at least in BSD. This used to be automatic, because chown(2) didn't follow symlinks. When chown(2) was changed to follow symlinks in BSD4.4, chown(8) was changed to not follow symlinks by default. The previous commit broke this. The first victim was bsd.prog.mk, which uses a plain chown in an attempt to change the ownership of the symlinks to `dm' in /usr/games. This fails when it is done before dm is installed, or messes up the ownership of dm if dm is installed. Unfixed problems: 1. When lchown(2) was implemented, chown(8) wasn't changed to implement the historical behaviour of changing ownership of symlinks. I'm not sure if it should have been. The -HLP options give more complete control, but they unfortunately don't apply unless the -R option is specified (a problem shared with other commands, e.g., cp; I guess we're supposed to use -R even for non-recursive traversals). 2. If we implement the historical behaviour, then -h would become a no-op and should be left undocumented. 3. The man page suggests that without option -h, all symlinks (to files specified in the command line?) are followed. It's not clear what "the file" is. These bugs were introduced when -h was documented. 4. The correct interaction of -h with the other flags is not clear.		1998-05-03 04:17:48 +00:00
..
chgrp.1	Cosmetic in man page. Sync usage() with man page.	1997-09-04 11:55:45 +00:00
chown.8	Cosmetic in man page. Sync usage() with man page.	1997-09-04 11:55:45 +00:00
chown.c	Backed out previous commit. chown(8) doesn't follow symlinks by	1998-05-03 04:17:48 +00:00
Makefile