you might need to be root (I'm not sure about the privilege system on OS/X), but the only other reason you might have got a tcp socket binding error is because another copy of adb was already running.
you are not experiencing anything which is unique - folks new to using command line are always mystified how things work until they find out about:
- what the "cd", "pwd", and "ls" commands do,
- what the PATH variable is all about,
- how to distinguish shorthand program and file names from relative or absolute file names.
See this link for example.
When using the command line, you start a program by typing it's name, and then adding to that (typed command name) a list of "arguments" which are passed to that program as soon as it starts up, e.g.
myprogram -edit myfile
you can either specify the exact location of the program you want to run and the exact location of any file names you use, for instance:
/myprogs/are/installed/here/myprogram -edit /home/user/job7/myfile
OR, you can specify things relative to your current directory:
/myprogs/are/installed/here/myprogram -edit ./job7/myfile
(In the above example, it is presumed that the current working directory is /home/user)
In addition, you can try to let the command interpreter (terminal) find programs for you:
myprogram -edit ./job7/myfile
In this very last case, the directory "/myprogs/are/installed/here" would have to be listed in what is called a "PATH" variable - it is just a list of locations where the command interpreter (terminal) looks for programs to match the "short" or abbreviated names you type in for programs (as in the last example above).
A simple alternative to mucking around with the PATH variable is to simply "cd" (Change Directories) so that your "pwd" (print Working Directory) is the location of the program you want to run:
cd /myprogs/are/installed/here/
./myprogram -edit /home/user/job7/myfile
(the leading "." character tells the command interpreter (terminal) to look in the current directory for the program "myprogram".
So, for instance, if you wanted to use ADB without worrying about PATH, or having to type in big long (complete) file pathnames, you would "cd" to the tools folder containing the adb program and then run adb with the shorthand notation
./adb kill-server
./adb shell
Hope that helps. Do a little search on "basics of using a command line" for OS/X and you'll probably see how it goes rather quickly. To get around with a command line, you really only need to know the "cd", "pwd", and "ls" commands.
