A whole bunch of people contributed the following ....
> > > The behavior of Mandrake 7.0's chown is clearly wrong; does anybody know
> > > why it happens?
> >
> > I don't think it's wrong. How would you like to have a user write a
> > setuid script and then make you the owner?
I would have to agree .. I would not want other users of the system
passing ownership of who-knows-what to me.
> That's *exactly* what *he* should be able to. So long as *I* can't me
> me the owner of "his* files, I don't see the problem.
Unless 'he' writes a damaging little script and says 'I' own it.
> You should be able to do what you want with your own files, including
> giving them to somebody else, without having to run to the sysadmin to
> do it. IMHO.
I would think that this is what 'group' was designed for
> And on HP-UX I could chown to "nobody", who is definately not in my
> "r+d" group, so that's not it.
FreeBSD 3.0 - not do-able as normal user unless you are chown'ing to the
group nobody
> Does anybody happen to have a FreeBSD duel boot? I'm curious about how
> it works there.
I also work on a FreeBSD box, you can change group but not owner, which
makes sense. Users can create files which are owned by them, they grant
permissions on those files (via chown & chmod) for others who may need
to use or access to the files based on 'group'.
Marcel
