> Thanks all for the tip! One question though, most other executable files
> don't need to use the ./ header to run an executable or am I wrong on this
> also and still thinking in M$FT mode?
The difference here is that DOS (or Windows for that matter) includes the
present working directory in the paths that get searched for commands. Linux
doesn't do this, but you have a few options.
1) Edit the file .bash_profile in your home directory to include directories
in your search path.
2) Copy, move, or symbolic link your new executable into a directory that is
already in your search path.
3) Preface the command with ./ anytime you want to execute something from the
present working directory.
4) Use the absolute path to your executable. ie:
By "most other executables" I am guessing that you mean those that your system
installed as part of your distribution. Things like ls & df are found in /bin,
while gcc & the like are found in /usr/bin. Take a peek at that .bash_profile
and I think you'll find that /bin & /usr/bin are already part of your search
path, which is why you don't need to preface them with ./ or any such thing.
I like to create a bin in my home directory for simple scripts or executables
I've created or installed just to try out.
Hope this helps.
-- Mike Selders, Network Administrator
Clark & Thompson Online Services, Inc.