sudo: command not found - Is this normal?

No it is not.

Could be your path is FUBAR. Verify it by seeing if sudo is in /usr/bin, as it should be. If it is, show us what your path is:

echo $PATH
echo $shell

If it's not, then it sounds like you might have installed OS X and not installed BSD Subsystem. Use Pacifist to get that installer of your OS X CDs/DVDs.

 

If your path really looks like this, then it's screwed up. There should not be a comma in the path.

 

Sorry, it was supposed to say should NOT be a comma.

Please verify the output of

echo $PATH

And make sure there's not a comma in there.

Do you have a .login or a .cshrc or a .tcshrc in your home directory?

 

Before you start fiddling with UNIX and the command line, you should familerize yourself with it's workings. Here is a good starting place for a tutorial:

http://osxfaq.com/Tutorials/LearningCenter/index.ws


The home directory is your home folder, where your Documents, Pictures, Music, Movies, etc are. If you have a comma in your path, then that is why sudo doesn't work. Please post the results of:

ls -laF ~

 

FUBAR = Fouled Up Beyond All Recognition

There's also SNAFU = Situation Normal, All Fouled Up

I believe there are alternatives based on another word that also begins with 'F'

 

/bin/ls -laF ~

 

It is most likely in /etc/profile.. Open Terminal and run:

/usr/bin/sudo /usr/bin/open -a TextEdit /etc/profile

Check the PATH variable in it.. For yours, it should read:

/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin

NOT
/bin:/sbin:/usr/bin:/usr/sbin,/urs/local/bin


Then save the file if you had to change it.

 

Nahh, it's all because your $PATH has been messed up. Fast fix from the terminal would be:

set PATH = /bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin

(My tcsh is rusty, you might need to use setenv)

that will fix that specific terminal session so the commands can be found.

Then you need to open the files listed above and fix the path.

 

The usual disclaimer:
Don't use sudo unless you know what you're doing.

I would go educate myself with at least the basics of the command line before using sudo as you can seriously screw up your system that way.

 

Hmm, sounds like you might have a personal file messing it up:

try

/usr/bin/open -a TextEdit ~/.profile

(notice the "." in front of the name there)

And see if there is a line in there that modifies the path. you need to do two things:

1) Change that comma into a colon ":"
2) Change the /urs at the end into a /usr

 

From the directory listing above, it appears there isn't a .profile. There is a .cshrc however, so I'd check there.

/usr/bin/open -a TextEdit ~/.cshrc

 

Told you my tcsh was rusty. I've been a bash person for a long time. (I also apparently don't read very well)

Come to think of it, you should also check /etc/csh.login and /etc/csh.cshrc -- I assume tcsh uses those?

 

There's your problem. It should be:

$PATH:/usr/local/bin

Colon, not comma. Change that and open Terminal and all will be correct. IMO, declaring path is much better to do in a ~/.login. Read that UNIX tutorial.

edIt BEcAUsE I dON'T KnoW wHat

 

Sorry, my fault there..

Edit that file again.

change it to:

set path = ($PATH /usr/local/bin)

Open Terminal. Verify that it's working with:

echo $PATH

It should look like this:

Code:

yellow% echo $PATH
/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin

 

Personally, I would prefer that you take the whole path declaration out of your .cshrc and put it in a .login, thusly:

setenv PATH "/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin"