--UPT3ojh+0CqEDtpF
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Frederick Bruckman wrote:
> On Fri, 9 Jan 2004, Rishabh Kumar Goel wrote:
> > To what setting should these flags be then set to?
=20
> So try something like this:
=20
>     chflags -R nouchg,noschg /lost+found
>     rm -r lost+found

In this case you'll need also "nosappnd,nouappnd".

BTW, where are these flags properly documented? I mean, I can guess
what their effect is but especially "opaque" isn't quite explained and
even if you use google the results are rather poor. Also, e.g., I first
thought that 'schg' means that the only the system (I read that as
super-user) may change the file or directory. Of course, that's not the
case but IMHO the very short descriptions in chflags(1) might allow such an
interpretation.
I think that's a little unfortunate because these flags complement the
unix file permissions pretty well e.g., a file can be owned by a=20
regular user but he isn't able to change it.

--=20
Christian

--UPT3ojh+0CqEDtpF
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (NetBSD)

iD8DBQE//xMK0KQix3oyIMcRAkGpAJ9DuBenn0Jumxifjf64QJTBXPqn+wCfRKI/
FIsNAhs7tDSYe5yFWt9INgs=
=M+aq
-----END PGP SIGNATURE-----

--UPT3ojh+0CqEDtpF--