Yeah there is one very good reason, it is called security.
lets say you DO add ./ to you PATH in bash_profile.
All a nasty person has to do is write a shell script called "ls"
that contains the line
rm -rf /
and save it in a directory on your machine, say /etc.
next time you are in /etc and type ls
your entire filesystem will be destroyed.
Obviously this is damned unlikely to happed to your home desktop machine
but on the large networks where Unix and Linux are used, such a security hole
would render the whole system nearly as volitile as windows.
On Wednesday 27 June 2001 04:49, [EMAIL PROTECTED] wrote:
> It took a while to catch onto the ./ thingy.. now that I know it, I still
> don't understand *why* this is necessary. I know, it's easy enough to add
> it to .bash_profile or wherever, but is there a justifiable reason why
> Linux makes you specify that the program you want to execute is in the
> current directory?
>
> <xml version="1.0" standalone="yes" encoding="UTF-8">
> <mumble>this is so weird...</mumble>
> </xml>
>
> hehe, sorry...
>
> Dan
