Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

The setuid bit and Classic startup problems Classic
Apple's kbase document 106639 lists a easy sounding fix to the Classic startup halt that ends with the message "You are running Classic without superuser (root privileges). Ensure that TruBluEnvironment is setuid and owned by root, or reinstall your Mac OS X System Software."

Unfortunately it didn't work for me, and it took forever digging up a fix in an unrelated article. The problem wasn't ownership, it was the setuid bit. In the Terminal, type:
 % cd /System/Library/CoreServices/Classic
Then go inside the ClassicStartup.app:
 % cd "Classic Startup.app"/Contents/MacOS
and type % sudo chmod ug+s *then type
 % chown root *
And your Classic should work again.
    •    
  • Currently 0.00 / 5
  • 1
  • 2
  • 3
  • 4
  • 5
  (0 votes cast)
 
[7,410 views]  

The setuid bit and Classic startup problems | 23 comments | Create New Account
Click here to return to the 'The setuid bit and Classic startup problems' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Is this tip possibly only for 10.1 and above...?
Authored by: Ray Tracer on Apr 29, '02 10:47:44AM

I'm still on 10.0.4 and there is no such directory (/System/Library/CoreServices/Classic) - the stumbling block is that last bit....Classic is not a directory within CoreServices.

I am, however, getting that very same error message. Any ideas how to fix that in 10.0.4?

Thanks!



[ Reply to This | # ]
Is this tip possibly only for 10.1 and above...?
Authored by: Anonymous on Apr 29, '02 07:20:18PM
Check this article.



[ Reply to This | # ]

Is this tip possibly only for 10.1 and above...?
Authored by: WillyT on Apr 29, '02 07:43:56PM

My system is different. I have an empty Classic folder in /System/Library/ and Classic Startup.app is in /System/Library/CoreServices/

Anyway you should be able to find Classic Startup somewhere in this area. Look using Sherlock or the finder or just cd and ls till you find it.

Running 10.1.4 upgraded continuously since 10.0 with only 2 reinstalls (one on advice of Apple person who couldn't help me, second for hardware upgrade) I highly recommend upgrading to 10.1 and doing the software updates to 10.1.4. You will get a more responsive system.

To use the terminal you must be resourceful. Blindly typeing following someones slightly hazy recollections will get you in trouble (especially with sudo).



[ Reply to This | # ]
Please help me quick!! Please Please Please!!
Authored by: blizzard on May 03, '02 01:08:31AM

Please help me, I'm having this problem too. I'm running system 10.1.4. Classic has worked fine since I installed it months ago. But then it just stopped working, I don't know what I did to it, but I want it back really bad! It says "You do not have sufficient permissions to run Classic from /Volumes/21GB/System Foler. Please correct permissions and restart Classic." I also don't have a Classic directory in the CoreSystem directory. Please help me, my email address is: freefast247@hotmail.com



[ Reply to This | # ]
Use BatChmod
Authored by: Anonymous on Apr 29, '02 07:39:09PM
With BatChmod you can do it without the Terminal. Target Classic Startup app with it and set owner to root with R,W and X boxes checked; set group to wheel with R and X checked; and everyone's R and X also checked. Dont forget the checkbox that "Apply ownership and privileges" to "Enclosed files and folders".

[ Reply to This | # ]
Use BatChmod?
Authored by: WillyT on Apr 29, '02 08:05:08PM

How do you setuid. Don't see it in the docs. Can't find it in the help file either.



[ Reply to This | # ]
BatChmod doesn't always work
Authored by: AMacAddict on May 03, '02 12:16:45PM

I tried this, but BatChmod wouldn't work for me. Only the terminal commands worked



[ Reply to This | # ]
How do you lose a suid bit?
Authored by: a1291762 on Apr 29, '02 08:52:28PM

I hate to say it, but how on earth do you "lose" a SetUID bit?

The only thing I can think of is that you have Restored an OS X partition from a backup that didn't save permissions.



[ Reply to This | # ]
The Apple KB article is right!
Authored by: Anonymous on Apr 30, '02 08:09:22PM

The "easy sounding fix" in the Apple Knowledge Base article you refer to clearly asks you to ensure that TruBluEnvironment is both "setuid" and "owned" by root. Why then do you state that this didn't work for you and that it "took forever digging up a fix in an unrelated article", only to come to the conclusion that the problem was nothing to do with ownership but that "it was the setuid bit", when the Apple KB article told you that in the first place?

In fact, why is this even a hint!?



[ Reply to This | # ]
Duh
Authored by: AMacAddict on May 03, '02 12:40:13PM

Please note that although the KB article points out the cause of the problems, the "simple" fix listed there most certainly does not always work, if at all. It's just a few clicks in the finder. It DOES NOT explain what the setuid bit is, how the steps listed are supposed to create a fix, nor does it give an alternative if, in my case and many others, this fix does not work.

It seems like it should be obvious I tried these steps, multiple times, the end result being NO FIX. The UNIX side of X can be very complicated, and is something the average Mac user has never encountered. It is my personal opinion that situations like this should never happen. It is Apple's claim that OS X is still as easy as it ever was, with the power of UNIX hiding underneath for those that want to utilize it. When I have users calling me and asking questions like why they don't own the folders and documents on their hard drive, and therefore cannot trash or delete things on what they see as THEIR COMPUTER, Apple has not delivered on that claim. I have fourteen years of Mac hardware and software support. I worked support at Motorola, and was manager of Citibank's technical support, taking care of all Macs by myself, plus doing PC calls. If I have to take a whole day figuring out a problem like this, what chance does my sister or my dad have fixing these types of problems?

I'm pretty sure this site is meant to help other people. If one other person avoids re-installing all of OS X using this hint, then it has served its purpose.

Did you even HAVE this problem? Did the KBase fix work for you?



[ Reply to This | # ]
Eh!?
Authored by: Anonymous on Jun 13, '02 04:43:04AM

OK, that KB article is full of rubbish, but the error message tells you what to you so why do you even need to consult the KB article?

"Ensure that TruBluEnvironment is setuid and owned by root."



[ Reply to This | # ]
Please Help me Quick!! Please Please Please!!
Authored by: blizzard on May 03, '02 08:30:06AM

Please help me, I'm having this problem too. I'm running system 10.1.4. Classic has worked fine since I installed it months ago. But then it just stopped working, I don't know what I did to it, but I want it back really bad! It says "You do not have sufficient permissions to run Classic from /Volumes/21GB/System Foler. Please correct permissions and restart Classic." I also don't have a Classic directory in the CoreSystem directory. Please help me, my email address is: freefast247@hotmail.com



[ Reply to This | # ]
Try this.
Authored by: serversurfer on May 03, '02 03:22:00PM
I wrote a little script to find your Classic Startup and make required mods. It's called FixClassic.zsh and you can grab it here. Then, in the Terminal cd to your download directory and type
./FixClassic.zsh
The script will ask you for a sudo (administrator) password. After that you should be good to go! If you have any problems with this, drop me an e-mail and I can write you a script that's slower, but more accurate. (It would use find rather that locate.) Hope this helps.

[ Reply to This | # ]
Try this.
Authored by: SaintStryfe on May 10, '02 10:20:07PM

Mmm.. I'm getitng "./FixClassic.zsh: Permission Denied" on a graphite iBook I'm working on. Any ideas?

-Stryfe



[ Reply to This | # ]
Hmmm...
Authored by: serversurfer on May 11, '02 06:05:52PM
A lot of people seem to be having trouble with ./ lately. (Bug in a recent system update?? Hmm, still works for me, but it have . in my path.) Here's the best work-around I have: cd to the directory where FixClassic.zsh is, then
sudo chmod a+x FixClassic.zsh
sudo cp FixClassic.zsh /usr/local/bin
rehash
FixClassic.zsh
Post back if this still doesn't work so we can come up with a fix that works for everyone.

[ Reply to This | # ]
one problem after another...
Authored by: curtechguy on May 23, '02 04:10:46AM

after entering sudo chmod a+x FixClassic.zsh
I see this,
sudo: /etc/sudoers is mode 0666, should be 0440
Any clues?? I can still only startup classic user root user.



[ Reply to This | # ]
one problem after another...
Authored by: serversurfer on May 26, '02 04:04:06AM
Wow. It sounds like your permissions are screwed up all over the place. Did you try to change things so you had read-write privs for everything? Don't fight the system, man. The default permissions are set that way for a reason. If you can't modify a file, you really need to think twice about whether or not you should. Also, recursive chmod's are generally a Bad Idea. If you need to modify an unwritable file, it is usually best to use sudo to modify it and just leave the perms alone. (the superuser, su, can do whatever they like)

This "fix" for this problem is, assuming you have enabled the root account:
you% su

Password: [enter your root password]
root# chmod 0440 /etc/sudoers
root# exit
you%
This will repair the sudoers file so you can use the sudo command and follow the steps in the above post. However, it sounds to me like your system is fscked. (No, I'm not talking about the fsck command.) I would strongly recommend that you re-install. If you can't do a clean install, at least re-install the latest system CD you have over the top of your current install and go through the updates to 10.1.4 again. This should fix all/most of your permission problems, including Classic. Good luck.

[ Reply to This | # ]
It's finally fixed!
Authored by: freudella on Jun 03, '02 04:04:41PM

\0\05{\0\0\0\0\0\0\0\0he post...I had exactly the same problems/error messages after I followed the instructions here (http://www.osxfaq.com/Tutorials/Root_User_Creation/index.ws) for setting myself up as superuser. I'm not badmouthing those instructions, however! I'm grateful for all the info, instructions, fixes that everyone contributes. Guess I should learn more about unix commands...



[ Reply to This | # ]
Try this.
Authored by: weeeze on May 24, '02 12:30:33PM

Tried your fix and anons' neither worked. But there is a nother factor. I'm an Idiot and have no Unix experience. What do you mean by "in the Terminal cd to your download directory"? Also do I have to be in root? My original problem was tring to drop a file on my HD from a .dmg. I had read only priviliges. So I read Poge's manual and opened root changed all files to read and write. When I closed root I couldn't run Classic. Also My Epson C80 no longer works in X 10.1.4



[ Reply to This | # ]
Try this.
Authored by: weeeze on May 25, '02 03:13:34PM

This is what worked for me. After opening the root account.
dl
http://homepage.mac.com/lprall/.cv/lprall/Public/chkstuff117a.sit-binhex.hqx
comes w/ instructions even an idiot (read me) can follow.



[ Reply to This | # ]
Stupid me
Authored by: serversurfer on May 26, '02 04:29:52AM

I didn't realize this was you, wheeeze.



[ Reply to This | # ]
Stupid me
Authored by: weeeze on May 27, '02 01:46:59PM

I'm weeze. just joined last week to fix the privilages problem
which I did. thank to all.



[ Reply to This | # ]
Try this.
Authored by: serversurfer on May 26, '02 04:27:40AM
Sorry, cd is a shell (Terminal) command to set the currentdirectory. Here's how you use it.

Assuming you downloaded the file to your Desktop (the default location for downloads) in the Terminal you would type:
you% cd /Users/you/Desktop
(you% is the shell prompt. Don't type that.) This will set the current directory (the directory with the "focus") to be your Desktop. All the commands executed after the cd command look for their targets in your Desktop until a new cd is issued. Also, since your Desktop is located in your home directory, you can use a UNIX shortcut to refer to it. The ~ character located just above the [TAB] key is UNIX for "/Users/you". That means,
you% cd ~/Desktop
has the same meaning as the above command.

If this doesn't help and neither does the tutorial, email me and we'll see what we can come up with. (I'll need to know the errors you are getting. Just copy and paste your Terminal session in to the email so I can read it.)

[ Reply to This | # ]