Re: BSD Flags further
Re: BSD Flags further
- Subject: Re: BSD Flags further
- From: Michael Smith <email@hidden>
- Date: Wed, 18 Oct 2006 04:01:26 -0700
On Oct 18, 2006, at 12:26 AM, Jeffrey Ellis wrote:
Can someone explain what the actual effect of setting each flag is,
namely:
arch
opaque
nodump
These three have no significant meaning.
sappnd
uappnd
These are the append-only flags. They effectively make it impossible
to change
data within a file.
schg
uchg
These are the immutable flags. They make a file, well, immutable.
sunlink
uunlink
And these are the undeletable flags. They make a file undeletable.
Each of these three pairs comes in two variants; the 'u' version
which permits the
flag to be set and reset by the owner, or root, at runtime, and the
's' version which
can be set at runtime, but cannot be cleared except in single-user mode.
Also, after some are set, I've now found that even sudo'ing "no"
commands in
chflags will not undo the original flag.
-rw-r--r-- 1 jeffrey admin sappnd,arch,opaque 16 17 Oct
22:54
testfile
:~/desktop root# chflags nosappnd testfile
chflags: testfile: Operation not permitted
Is there some other way to un-set these flags?
Not short of booting the machine to single-user mode. The s* flags
are designed
to protect data against someone that has privileged access to the
system; allowing
that user to turn them off would render them useless.
= Mike
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden