This is an old revision of the document!
I'm not sure how one first gets exposed to path variables, only that it can be confusing at first glance. This document tries to remedy that without going into the history of everything.
What you need to know:
There are various directories that follow this pattern [not limited to]:
bin: binaries (actual commands you execute: e.g.
include: source code
share: other, usually documentation
man: manual pages
The directories can exist inside of any directory path. There are the usual ones you may have seen already:
Ever wonder what happens when you type in a command (
ssh) into the terminal and somehow your shell knows to launch that program.
Assuming the command is not a shell command, the shell will check the appropriate variable which includes search locations to launch the program you wish to execute.
In our example,
ssh is located in
/usr/bin on my machine.
We can find out where it by using the command
which which (hehe!) will traverse our search paths to find the executable we are looking for.
user@linux1:~$ which ssh /usr/bin/ssh
Generally your search path for binaries will look something like the below.
We can see what is in our path variable by using the command
echo to check the contents of the variable that contains our search paths. This variable is called
user@linux1:~$ echo $PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
When a search occurs it will take the left most path, search that directory, then proceed to the next path to its right IF and ONLY IF it does not find what it is looking for in the directory it is currently searching.
Fore example: Lets take a look at the executable
/usr/local/bin is first in the search path so we'll see the version of
pip installed by CS Techstaff.
user@linux1:~$ which pip /usr/local/bin/pip
There also exists and pip executable in
/usr/bin/pip but as discussed above the shell will use the binary first in the search path.