From owner-freebsd-stable@FreeBSD.ORG Tue Sep 9 10:46:56 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 107A416A4BF for ; Tue, 9 Sep 2003 10:46:56 -0700 (PDT) Received: from epsb.ca (relay.epsb.ca [198.161.119.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D48F43FF3 for ; Tue, 9 Sep 2003 10:46:55 -0700 (PDT) (envelope-from Sean.Page@epsb.ca) Received: from exchange05.epsb.edmonton.ab.ca (exchange05.epsb.ca [10.0.5.14]) by epsb.ca (8.11.3/8.11.3) with ESMTP id h89HkDv39909; Tue, 9 Sep 2003 11:46:13 -0600 (MDT) (envelope-from Sean.Page@epsb.ca) Received: by exchange05.epsb.ca with Internet Mail Service (5.5.2653.19) id ; Tue, 9 Sep 2003 11:44:19 -0600 Message-ID: From: Sean Page To: "'Matthew Seaman'" Date: Mon, 8 Sep 2003 10:52:04 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain cc: stable@freebsd.org Subject: RE: No nonodump... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Sep 2003 17:46:56 -0000 Hrm, strange. My man page for chflags is as follows: The flags are specified as an octal number or a comma separated list of keywords. The following keywords are currently defined: arch set the archived flag (super-user only) opaque set the opaque flag (owner or super-user only) nodump set the nodump flag (owner or super-user only) sappnd set the system append-only flag (super-user only) schg set the system immutable flag (super-user only) sunlnk set the system undeletable flag (super-user only) uappnd set the user append-only flag (owner or super-user only) uchg set the user immutable flag (owner or super-user only) uunlnk set the user undeletable flag (owner or super-user only) archived, sappend, schange, simmutable, uappend, uchange, uimmutable, sunlink, uunlink aliases for the above Putting the letters ``no'' before an option causes the flag to be turned off. For example: nouchg the immutable bit should be cleared A little misleading I would say. At any rate, 'chflags dump' did indeed remove the flag in question. Thanks for the suggestions. Sean. -----Original Message----- From: Matthew Seaman [mailto:m.seaman@infracaninophile.co.uk] Sent: September 8, 2003 10:22 AM To: Sean Page Cc: stable@freebsd.org Subject: Re: No nonodump... On Mon, Sep 08, 2003 at 09:57:24AM -0600, Sean Page wrote: > I'm not sure where else to ask about this, so please excuse me if this > is the wrong forum. In trying to remove a 'nodump' flag on a directory > with the 'chflags' command I have noticed that the 'nonodump' flag > does not function. I see an open PR for the problem: o [2003/01/09] > i386/46912 johan chflags nonodump fails I was wondering when this > might be dealt with? Else is there another way to remove the flag? As the chflags(1) man page states, the opposite of 'nodump' is 'dump': Putting the letters ``no'' before or removing the letters ``no'' from a keyword causes the flag to be cleared. For example: nouchg clear the user immutable flag (owner or super-user only) dump clear the nodump flag (owner or super-user only) Or, if you want to clear all flags from a file you can: % chflags 0 file Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK