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? Thanks in advance, Sean. Sean Page Network Analyst, Internet Services Information Technology Services Edmonton Public Schools Phone: (780) 429-8206 http://its.epsb.ca <http://its.epsb.ca>
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 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20030908/c843f023/attachment.bin
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?From the chflags manpage: 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) Ceri -- User: DO YOU ACCEPT JESUS CHRIST AS YOUR PERSONAL LORD AND SAVIOR? Iniaes: Sure, I can accept all forms of payment. -- www.chatterboxchallenge.com -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20030908/e3e0000b/attachment.bin
Alas, 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: Ceri Davies [mailto:setantae@submonkey.net]
Sent: September 8, 2003 11:48 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?
>From the chflags manpage:
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)
Ceri
--
User: DO YOU ACCEPT JESUS CHRIST AS YOUR PERSONAL LORD AND SAVIOR?
Iniaes: Sure, I can accept all forms of payment.
-- www.chatterboxchallenge.com
Ahhh, right you are. Regrettably, you caught me skimming the material a little too quickly. Guess I should have finished my coffee first [insert sheepish grin here] :-) Sorry to have wasted the bandwidth folks. Sean. -----Original Message----- From: Ceri Davies [mailto:setantae@submonkey.net] Sent: September 8, 2003 12:23 PM To: Sean Page Cc: stable@freebsd.org Subject: Re: No nonodump... On Mon, Sep 08, 2003 at 12:08:43PM -0600, Sean Page wrote:> Alas, 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-useronly)> uchg set the user immutable flag (owner or super-user only) > uunlnk set the user undeletable flag (owner or super-useronly)> 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.Without wishing to sound like an asshole, did you read the PR that you posted a reference to? Specifically the part where it says the manpage should say "use dump to clear the nodump flag".> At any rate, 'chflags dump' did indeed remove the flag in question. > Thanks for the suggestions.No problem. Ceri -- User: DO YOU ACCEPT JESUS CHRIST AS YOUR PERSONAL LORD AND SAVIOR? Iniaes: Sure, I can accept all forms of payment. -- www.chatterboxchallenge.com
Sean Page wrote:> Ahhh, right you are. Regrettably, you caught me skimming the material a > little too quickly. Guess I should have finished my coffee first [insert > sheepish grin here] :-)See my sig. In any case, one might have wished for orthogonality in the command line options/flags, or a fix in the man page. ;-)> Sorry to have wasted the bandwidth folks.Not at all, it was more entertaining than most threads. -- "Well," Brahma said, "even after ten thousand explanations, a fool is no wiser, but an intelligent man requires only two thousand five hundred." - The Mahabharata
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