On Thu, Aug 02, 2001 at 08:50:08AM -0500, Kathy Bieltz <[EMAIL PROTECTED]> wrote:
| Dale,
| You don't have the current directory "."
| defined in your PATH.
| Typing '.\' in front of an executable
| tells the system to look in the current
| directory for the executable.
[...]
| If you want to add the current directory
| to you path then do the following:
| PATH=.:$PATH
| export PATH
Please don't.
Firstly, putting the ucrrent dir in is generally considered a security
flaw; it leaves you open to accidentally running someone elses command
just be standing in the wrong directory, and that may to anything. It
doesn't even need to be malicious, just bad luck with names will do.
Secondly, if you must put . in your PATH, put it at the END! That way
you won't hang yourself with an unfortunately named local script ("test"
is the classic example).
Thirdly, _don't_ do this in your .bashrc, do it in your .bash_profile.
Better practice is, when you're satisfied that the script does what you
want (after some testing as "./backup") ,_then_ move the script into
a well defined place, like $HOME/bin, and have $HOME/bin in your $PATH,
typically at the front. This keeps a distinction between ``'real" commands
you've written and installed in $HOME/bin'' and ``random scripty things
I'm testing'', which you don't want to interfere with the normal running
of other things (which will also be using your PATH to find stuff).
Cheers,
--
Cameron Simpson, DoD#743 [EMAIL PROTECTED] http://www.zip.com.au/~cs/
The thought of suicide is a comforting one, for with it has come a calm
passage through many a bad night. - Fred Nieztsche
_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list
