One way to speed up the interaction time of
a shell (that does not hash its commands)
that you may overlook is to modify your path.
The order of the directories in your path
should rely on the number of commands you use
most. So /usr/bin or /bin would probably be first.
Very large directorys that are mounted over
the network should be later in the list. If
there are some directories in your path you only
use for one or two commands consider making an
alias or shell script (if your shell doesn't
support aliases) which calls the program with its
full path name.
Watch out when sourcing files, especially when
your root. It could modify your path and make
you run something detrimental to your system.
Getting into the habit of using full pathnames
is the key here.
This tip generously supported by: kevin@ti.com NOTE: All tips provided are USE AT YOUR OWN RISK. Tips are submitted
by various unix admins around the globe. UGU suggest you read and
test each tip in a non-volitile environment before placing into
production.