Return to BSD News archive
Newsgroups: comp.unix.bsd.freebsd.misc Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!howland.erols.net!news.mathworks.com!EU.net!usenet2.news.uk.psi.net!uknet!usenet1.news.uk.psi.net!uknet!uknet!newsfeed.ed.ac.uk!edcogsci!richard From: richard@cogsci.ed.ac.uk (Richard Tobin) Subject: Re: Why chown(2) is privileged? X-Nntp-Posting-Host: pitcairn Message-ID: <E0vMsx.Bp0@cogsci.ed.ac.uk> Sender: cnews@cogsci.ed.ac.uk (C News Software) Organization: HCRC, University of Edinburgh References: <CANDY.96Oct24222129@xxx.fct.kgc.co.jp> <w7iv7cjv2t.fsf@mud.imperium.net> <847786081.259851@panacea.insight.co.za> Date: Thu, 14 Nov 1996 20:12:32 GMT Lines: 13 In article <847786081.259851@panacea.insight.co.za> tony@panacea.insight.co.za (Tony Harverson) writes: >chmod 4777 my_copy_of_csh >chown root my_copy_of_csh No, this is not the reason. Versions of unix that allow non-root chown clear the setuid bit when they do it. The real reason, as has been said before, is to allow quotas to work. -- Richard -- "Nothing can stop me now... except microscopic germs"