Sean.Page at epsb.ca
Mon Sep 8 13:00:12 PDT 2003
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.
From: Ceri Davies [mailto:setantae at submonkey.net]
Sent: September 8, 2003 12:23 PM
To: Sean Page
Cc: stable at 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-user
> uchg set the user immutable flag (owner or super-user only)
> uunlnk set the user undeletable flag (owner or super-user
> 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
> 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.
User: DO YOU ACCEPT JESUS CHRIST AS YOUR PERSONAL LORD AND SAVIOR?
Iniaes: Sure, I can accept all forms of payment.
More information about the freebsd-stable