"Deshazer, Earl (GEAE)" wrote:
> > > With regard to command execution. Unlike the flavors of Unix that I am familiar > with, Unix requires a specification on where the command is thus ./ This has nothing to do with what flavor of UNIX you're running. and everything to do with your PATH environment variable. Where is the script located? If it's in your path it will execute by calling by name. If not you'll nned to qualify the path to the file, or (as in this example) if you're in the same directory, prepend the ./filename. OS X's somewhat un-UNIX-like Directory names, means care must be taken when defining your PATH variable. If you're on a multi-user machine, avoid the temptation of adding a "." to your PATH. One "standard" appraoch is to define a bin directory under your $HOME, then adding $HOME/bin or ~/bin to the end of you PATH.
