From owner-freebsd-doc Fri Jan 24 19:30: 9 2003 Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 87AC337B401 for ; Fri, 24 Jan 2003 19:30:07 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3159A43EB2 for ; Fri, 24 Jan 2003 19:30:07 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.6/8.12.6) with ESMTP id h0P3U3NS010715 for ; Fri, 24 Jan 2003 19:30:03 -0800 (PST) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.6/8.12.6/Submit) id h0P3U3YZ010714; Fri, 24 Jan 2003 19:30:03 -0800 (PST) Date: Fri, 24 Jan 2003 19:30:03 -0800 (PST) Message-Id: <200301250330.h0P3U3YZ010714@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org Cc: From: swear@attbi.com (Gary W. Swearingen) Subject: Re: docs/46415: Proposed change in man-page wording for "chown" Reply-To: swear@attbi.com (Gary W. Swearingen) Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR docs/46415; it has been noted by GNATS. From: swear@attbi.com (Gary W. Swearingen) To: Giorgos Keramidas Cc: bug-followup@freebsd.org, System Administrator Subject: Re: docs/46415: Proposed change in man-page wording for "chown" Date: 24 Jan 2003 19:19:08 -0800 Giorgos Keramidas writes: > Change the user ID and/or the group ID for the file hierarchies rooted > in the files instead of just the files themselves. I guess it'll do. It sure is geeky. "Hierarchies rooted in files"? I'm not sure that it's even explained in intro Unix books that "files" can mean "directories" or what "rooted" means. But I guess newbies can learn to decypher geek-speak the same way we did -- the hard way. > +Be careful when you use wildcard patterns that include a dot > +.Ql \&. > +character, since when expanded by your shell it might result in > +.Nm > +changing files outside of the current directory. It probably needs to mention the culprit, ".." as it's not obvious why a dot needs care. "*dog.cat" needs no care, but "dog/../../cat" does. (The latter's need for care can probably go without saying with or without a "*".) How about: Beware of unintentionally operating on the ".." hard link when using wildcards which start with a dot (e.g., ".*") . Also: In your sentence, I think you ought to paren the dot character and move it after "character", or just remove the word "dot". P.S. Here's a little log of a test I just ran. I guess I don't know what we're trying to document, now. It didn't pick up the ".." link. ???? $ chown -R root:wheel .* chown: .*: No such file or directory To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message