PDA

View Full Version : Superuser(root) privileges in classic.....


MMM
02-10-2002, 01:48 PM
I have encountered this dialog when I launch classic.

"YOU HAVE ATTEMPTED TO LAUNCH CLASSIC WITHOUT SUPERUSER(ROOT) PRIVILEGES. ENSURE THAT TRUBLUENVIRONMENT IS SETUID AND OWNED BY ROOT. OR REINSTALL MAC OSX."


The Admin aspects of OSX have me a bit perplexed at the moment, but i'm gaining on it. Any thoughts for this newbie is much appreciated.

thanks,

MMM

mervTormel
02-10-2002, 05:23 PM
show us your TruBlueEnvironment file in a terminal shell window...


% ls -l /System/Library/CoreServices/Classic\ Startup.app/Contents/Resources/TruBlueEnvironment
-rwsr-xr-x 1 root wheel 466k Dec 20 18:37 /System/Library/CoreServices/Classic Startup.app/Contents/Resou
rces/TruBlueEnvironment*

see the permissions mask -rwsr-xr-x ?

that s means that SetUID permission is set for this executable.

if your's is not, then we could try to fix it, but let's see first

MMM
02-10-2002, 08:31 PM
Merv,

ls -l /System/Library/CoreServices/Classic\ Startup.app/Contents/Resources/TruBlueEnvironment
-rwxrwxrwx 1 root admin 476800 Feb 8 11:50 /System/Library/CoreServices/Classic Startup.app/Contents/Resources/TruBlueEnvironment

This is what i got when I look at TruBlueEnvironment in the terminal. looks different to me! Your thoughts?

MMM

mervTormel
02-10-2002, 08:55 PM
have you been experimenting with chmod and chown? if you have, and other files are permissions/owner whacked, this could cause more problems elsewhere.

to begin the fix up for TruBlueEnvironment, try...

% sudo chmod u=rwsx,go=rx \
/System/Library/CoreServices/Classic\ Startup.app/Contents/Resources/TruBlueEnvironment

then check that it looks like it should. we won't worry about the group owner now.

note: sudo will ask for your username's password

MMM
02-10-2002, 09:28 PM
Sorry, sudo must be setuid root.

this is the eply when i input your command line.

no, i have not experimented with any terminal actions at all.

thanks,

MMM

mervTormel
02-10-2002, 09:50 PM
not to sound accusatory, but it would be nice to know how this happened...

have you logged in as root, and subsequently changed permissions for any top level directories (folders) from the get info window?

it appears that your installation has had some fundamental permission masks changed that has hobbled it.

anyhow, i replied to your private msg, and basically asked you "how fond are you of your current installation?" how painful is it to reinstall OSX?

i'm afraid the exchange for fixing this up would become tedious quickly and is fraught with perilous unknowns.