From owner-freebsd-doc@FreeBSD.ORG Sun Jul 31 15:30:25 2005 Return-Path: X-Original-To: freebsd-doc@hub.freebsd.org 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 16AED16A41F for ; Sun, 31 Jul 2005 15:30:25 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA07543D49 for ; Sun, 31 Jul 2005 15:30:24 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j6VFUO19042585 for ; Sun, 31 Jul 2005 15:30:24 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j6VFUOS9042583; Sun, 31 Jul 2005 15:30:24 GMT (envelope-from gnats) Date: Sun, 31 Jul 2005 15:30:24 GMT Message-Id: <200507311530.j6VFUOS9042583@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org From: garys@opusnet.com (Gary W. Swearingen) Cc: Subject: Re: docs/84268: chmod(1) manpage's BUGS entry is either wrong or too cryptic X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Gary W. Swearingen" List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Jul 2005 15:30:25 -0000 The following reply was made to PR docs/84268; it has been noted by GNATS. From: garys@opusnet.com (Gary W. Swearingen) To: Ceri Davies Cc: FreeBSD-gnats-submit@FreeBSD.org Subject: Re: docs/84268: chmod(1) manpage's BUGS entry is either wrong or too cryptic Date: Sun, 31 Jul 2005 08:27:19 -0700 Ceri Davies writes: > Failing that, it means 'S' and 'T'. Then the BUG entry doesn't say what it means and will waste people's time trying to figure out what it does mean. I still think the BUGS section should be removed. Or I can make a new patch with: There is no "perm" option which sets the sticky bit and also unsets the execute/search bit, and vice-versa, depending upon the "op" value. The same applies to each of the setuid and setgid bits. There once was a man from Nantucket... I sure don't see that as a BUG; just a (good) design decision.