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


Hmmm... | 23 comments | Create New Account
Click here to return to the 'Hmmm...' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
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 | # ]