> >> Modified Files:
> >> 	ufs_vnops.c 
> >> Log Message:
> >> Move some permission-checking code for file owner/group changes up to
> >> vfs_syscalls.c::change_owner().  Also, always update the inode's change time
> >> if the operation succeeds.
> >
> >The first half of this change (moving the permissions check up to
> >vfs_syscalls.c) make things somewhat inconvenient for third-party
> >filesystems like AFS which have their own permission model.
> 
> Ouch, I didn't realize the implications of this.  I use AFS every day
> on NetBSD; doing this would really screw me (and others).
> 
> Can we please back this change out?

What is it, exactly, that causes you folks to think that this change
will cause problems for file systems like AFS?

The statement that it'll make things "somewhat inconvenient" is nice
and all, but i don't see how the actual set of changes will cause
problems.  (I have some knowledge of AFS internals, but am by no means
an AFS expert...)


cgd