Christopher Bort wrote:
The point of my suggestion was to find out if Repair Permissions
would fix the permissions on sudoers w/o having to boot in SUM. I've never
had to do this myself, so I don't know for sure one way or the other. ;-]
Once sudoers perms are fixed, though, it's probably a good idea to run
Repair Permissions in order to fix permissions on as many other
/private/etc/* files as possible that may have been fuxored by your
recursive chmod. I know you said you did this; I'm curious as to how well
it did getting you back to a good state?
I haven't inspected it yet, but I did print out a few pages of output
from the run, so at the very least it believes it fixed a lot of stuff.
BTW, in case you're not aware of it, Repair Permissions is not available
only through the Disk Utility GUI. It can also be run from a shell with
`diskutil repairPermissions`.
Yes, but I didn't expect it to work because I suspected that it would
also call sudoers (and would fail).
The reason I didn't is because I tried fsck and it failed and
because everything else requiring elevated privileges was also
failing.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Fink-users mailing list
Fink-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-users
