You should search your tutorials for the PATH environment variable.

In an over-simplified nutshell, when you type a command in your shell,
it checks a number of different locations for the place to find the
command you're trying to execute.  Some of those locations are every
directory specified in your PATH variable.  My PATH is:
/bin:/usr/bin:/usr/local/bin:/sbin:/usr/sbin

This means that when I type 'ls', the shell looks for an executable
named 'ls' in each of those directories (actually, it probably stops
right after /bin/ls, since that's the correct one.)

If the shell does not find a valid executable in the path, it will say
that there is no such file or directory.  In this case, you would try
specifying the full path by typing /bin/ls, or /home/user/scriptname.
'.' and '..' have special meanings--current directory and
next-directory-up, specifically--so if your current working directory
is /home/user, typing ./scriptname will be largely equivalent to
typing /home/user/scriptname.  ../scriptname would be largely
equivalent to /home/scriptname.  This is why some people suggested
trying ./scriptname in other e-mails in this thread.

The '.' notation for the current working directory enables you to add
the current directory you happen to be in as part of your path (thus
making it searched when executing a command), however this has serious
security implciations, so if you think that it's something you really
want to do, you'll have to find out from someone else how to do it.

erik
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"