--=_courier-3818-1056556112-0001-2
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Wed, Jun 25, 2003 at 11:11:51AM -0400, Valdis.Kletnieks@vt.edu scribbled:
[snip]
> > can remove any files created by root whether or not restricted_chown is=
in
> > effect. That might be quite a nightmare for the admins. Or at the very =
least
> > it's inconsistent with other filesystems.
>=20
> Maybe I'm low on caffeine and therefor misreading it, but isn't this just=
an
> example of "file rename/remove requires write permission on the *parent*
> dirctory, since that's what's being changed", which often surprises novic=
e (and
> not-so-novice) sysadmins? See also the reason for the sticky bit on dire=
ctories..
>=20
> In any case, I didn't notice that any behavior (other than the 'chown giv=
eaway')
> was different than other filesystems?
You're right. It must have been me who was low on caffeine. Indeed, the only
problems were the chown giveaway and the quota ownership transfer. Forget
the blurb, sorry
marek
--=_courier-3818-1056556112-0001-2
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE++cPTq3909GIf5uoRArF9AJ9Mr2iSILl5G8OhPNHhLtPcPjkcQQCffQ7t
IaWg4bM5vdyXxBl5VHUaze8=
=AMrJ
-----END PGP SIGNATURE-----
--=_courier-3818-1056556112-0001-2--