sudo must be setuid root

Untitled

Untitled

Untitled
After a total system crash due to an attempted switch back to mac OS 9.2.2 to scan something (points to another member in family and notes the program can be run through classic mode) , I had to install Mac OS 10.0, then update back to 10.1 and then finally to 10.1.2. bla...

The next thing I attempt to do is show how the progam can be run through the classic mode and discover someone else in the family attempted to solve this problem by setting the privledges to read/write for everyone in the group. bla...

What do I do next? I attempt to enter the next commands to fix the issue
------
sudo chmod 4755 "/System/Library/CoreServices/Classic Startup.app/Contents/Resources/TruBlueEnvironment"
sudo chown root:wheel /System/Library/CoreServices/Classic\ Startup.app/Contents/Resources/TruBlueEnvironment
-----
if I enter ethire of these commands, I get the reply from the terminal
Sorry, sudo must be setuid root.

How can I fix this setuid issue and if anyone knows, how can I stop these total system crashes!

By the way, I later found if you use a full install cd for mac os 9, (no you can't use the one that comes with the the 10.1 update) you can prevent doing this entire installation as I did.

Yes, I did have a bad day.
 
Thanks testuser, that got me a little farther however now when I try to run sudo I get the message
sudo: /etc/sudoers is mode 0664, should be 0440
and of coarse I'm stuck again. What should I do now?

My dad was the person responsible for changing all the permissions. He logged on as root and I assume he clicked on the hard drive and clicked the button that changes all the permissions for the folders inside the volume.
Sounds like a good time to accidently change the root password, eh?

Anyhow, I did reinstall an update of X.1.2 and It seems that a good deal of the permissions were corrected, however I'm still having this one problem.
 
I just used the chmod command and things seemed to work aok however I was not able to fix the classic startup issue.
After a quick decision to reinstall mac os x to correct these permissions, I learned the installation did NOTHING! now I can't use itunes, classic applications or save files to certain locations on my hard drive!!!

I have no idea what to do now because I do not know what the permissions were for the folders to start with because someone made them all the same!!!

I think I am going to have to move all my files back to os 9, delete all the files I know are related to os X and restart from scratch unless someone else has a better idea.
 
I tried re-installing os 10.0 again and then updated for now to 10.1
I also deleted the users and created new ones
In the end, I'm at where I started agian. I am also getting a new error when I use the terminal. It just pops up every now and being a inexperienced unix user, I have no idea what it means.
--------------------------
[localhost:~] main% /etc/mail/sendmail.cf: line 81: fileclass: cannot open /etc/mail/local-host-names: Group writable directory
/etc/mail/sendmail.cf: line 81: fileclass: cannot open /etc/mail/local-host-names: Group writable directory

--------------------------
main is my user name. I have administrative privledges.

testuser I did see your comment about netinfo but I have not altered or attempted to alter anything in Netinfo other than to turn on the root user.
 
When I say I am back to where I started, I mean't the classic environment is not working as well as a few other applications. Sorry for the lack of info in my last post.
I found another new problem too. It appears Stuffit Expander is having troubles writing files to the desktop.

When I used my mac os 9.1 cd to attempt a re-install, after starting up it said my hard drive was unreadable! not a plus... Thankfully I can still boot up and use my HD in OS 10 however a re-install of os 9 is out of the question.

As for sendmail, I'm not sure how it got turned on but the sudo commands did help thanks <B>testuser</B>.

Is there anything else I can do before I am forced to do a clean install?
 
I tried the fsck -y however my hard drive was spiffy to begin with. It would have been great if that was my only problem.
Unfortuanately, in the end I decided to reformat my hard drive and delete M$ word as well.
In the end, everything is back to normal! Except for my root password. This password for some reason was changed and "accidenaly" forgot, oops! :D ;)
 
You must log in or register to reply here.
Back
Top