Re: This is why FreeBSD...
  By: Angus Mcleod to Takumi on Sat Aug 14 2004 04:32 am

 >  > If you want someone else to own a file, write it yourself, and get them t
 >  > it.
 > 
 > Doesn't wash.  The entire chown command is useless if you can't actually USE
 > it.  Of you're worried about setuid/setgid then make chown non-functional fo
 > files with setuid/setgid bits set.  Or to be really strict, make it so you c
 > only chown to your own userid (with read perms on the other guys file(s), of
 > course).

You can just grab sudo from Ports and then let particular users be able to use
chown at will... sudo's default password prompt is annoying but you can turn
that off if the security aspect doesn't seem too troubling... then those users
can just make an alias for chown that does a sudo chown and it's not really too
inconveniencing, if at all.

I don't think the inability of non-root to chown makes FreeBSD a
"bullshit OS"
by any means, you're gonna have to make a much stronger case than that ;)  The
restriction on chown is a standard BSD thing, versus anyone-chown'ing being a
System V thing, and POSIX allows either one according to a book I have.
---
 þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net