On Sat, 02 Oct 2004 11:02:12 +1000
Gareth Smith <[EMAIL PROTECTED]> wrote:
> thanks
> it's working
> when I was trying to run it I was typing in the filename instead of
> ./filename
Thats a ****VERY**** common mistake :-).
I'm almost thinking of submitting a patch to bash that given
a command like :
bash $ some_command
and bash can't find some_command, it then looks in the current
directory and if there is a "some_command" there and its and
executable it prints:
-bash: some_command: command not found
maybe you should try "./some_command"
Erik
--
+-----------------------------------------------------------+
Erik de Castro Lopo [EMAIL PROTECTED] (Yes it's valid)
+-----------------------------------------------------------+
"Lumping configuration data, security data, kernel tuning parameters,
etc. into one monstrous fragile binary data structure is really dumb."
- David F. Skoll
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
