docs/84265: chmod(1) manpage omits implication of setting w on directory

[Giorgos Keramidas]

The following reply was made to PR docs/84265; it has been noted by GNATS.

From: Giorgos Keramidas <keramida at freebsd.org>
To: "Gary W. Swearingen" <garys at opusnet.com>
Cc: bug-followup at freebsd.org
Subject: Re: docs/84265: chmod(1) manpage omits implication of setting w on directory
Date: Mon, 1 Aug 2005 11:59:35 +0300

 On 2005-07-31 14:25, "Gary W. Swearingen" <garys at opusnet.com> wrote:
 >Giorgos Keramidas <keramida at freebsd.org> writes:
 >> I'm not sure if I am happy when features of programs are documented as
 >> the behavior of the file/directory creation code.
 >
 > I wasn't sure, either. But users with a different concept of "created"
 > than a Unix programmer will cry "FALSE" when they read your ``Files
 > created in a directory will be assigned the group ID of the
 > directory''.
 
 Ah, I see.  Good point.
 
 > If you want your sentence, it should at least have another saying
 > something like: "This rule has exceptions." or "Some software will
 > appear to violate this convention".
 
 How about a note that...
 
 	There are exceptions, since some programs by design (or because
 	it was requested with a special command-line option) need to
 	create the files and then modify their owner and/or permissions
 	for various reasons.  Such exceptions include:
 
 	*	The cp(1) utility when the -p option is used.
 
 	*	The mv(1) utility.
 
 	*	Archiving tools, like cpio(1) or tar(1).
 
 	*	Backup tools, like restore(8)
 
 Does that look ok?
 
 > I've probably said enough; do as you wish.
 
 Ehm.  No, please keep saying.  Your comments have been extremely useful
 as a means to improve the manpages so far :-)