From owner-freebsd-bugs  Fri Jan 10  1:30: 5 2003
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id A46ED37B401
	for <freebsd-bugs@hub.freebsd.org>; Fri, 10 Jan 2003 01:30:04 -0800 (PST)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 5B0EE43F1E
	for <freebsd-bugs@hub.freebsd.org>; Fri, 10 Jan 2003 01:30:04 -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 h0A9U4NS036114
	for <freebsd-bugs@freefall.freebsd.org>; Fri, 10 Jan 2003 01:30:04 -0800 (PST)
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.12.6/8.12.6/Submit) id h0A9U4G0036113;
	Fri, 10 Jan 2003 01:30:04 -0800 (PST)
Date: Fri, 10 Jan 2003 01:30:04 -0800 (PST)
Message-Id: <200301100930.h0A9U4G0036113@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.org
Cc: 
From: Bruce Evans <bde@zeta.org.au>
Subject: Re: i386/46912: chflags nonodump fails
Reply-To: Bruce Evans <bde@zeta.org.au>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-bugs.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-bugs>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-bugs>
X-Loop: FreeBSD.org

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

From: Bruce Evans <bde@zeta.org.au>
To: dave@syix.com
Cc: FreeBSD-gnats-submit@FreeBSD.ORG
Subject: Re: i386/46912: chflags nonodump fails
Date: Fri, 10 Jan 2003 20:27:57 +1100 (EST)

 On Thu, 9 Jan 2003 dave@syix.com wrote:
 
 > >Description:
 > chflags nonodump filename/foldername fails
 >
 > >How-To-Repeat:
 > chflags nodump a folder/file and then try to un-nodump it
 
 This is only a documentation bug.  Use "chflags dump ..." to clear the
 nodump flag, not "chflags nonodump ..." like the man page says.
 
 The NODUMP flag is the only negative-logic flag, so it is the only one
 with this problem.  The nosunlink and nouunlink flags, which should
 have negative logic, are handled bogusly using positive logic.  This
 results in them being displayed backwards ([su]unlnk is displayed when
 the no[su]unlink flag is set).
 
 Bruce
 

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message