--- On Fri, 19/2/10, Prema <[email protected]> wrote: > > > > se...@selvamani-laptop:~$ sudo chmod 777 -R /usr/ > > sudo: must be setuid root > > se...@selvamani-laptop:~$ > > > > If the problem is just that you chowned /usr, try booting > into the recovery > console and type > > chwon root:root /usr/bin/sudo > chmod 4755 /usr/bin/sudo > then.. > > reboot > > This worked for me when I face the same issue..
A bit of explanation: chmod 4xxx will set what is called setuid on execution. That means when the programme is run it will be run as owner of the file, even though started by anybody else. sudo should run as root to do most of function and hence set with setids. A simple chmod xxx will remove any such setid's. I am curious why people want 777 for /usr?. Raman.P blog:http://ramanchennai.wordpress.com/ Your Mail works best with the New Yahoo Optimized IE8. Get it NOW! http://downloads.yahoo.com/in/internetexplorer/ _______________________________________________ ILUGC Mailing List: http://www.ae.iitm.ac.in/mailman/listinfo/ilugc
