Paul Derbyshire wrote:
>
> Interesting what you find when you poke randomly in man pages and other
> docs. Or read a random shell script from the system and man everything
> unfamiliar you see in the file that looks like it might be a command or a
> standard file name.
>
> The "which" thing, to find out what exact directory a command on your path
> is in, is a nice example of a very useful and simple utility totally
> lacking in MS-DOS <snip>
Ain't that the truth? <g>
I didn't even know about 'which.' I used " whereis xloadimage " to
find WHERE it was. 'Which' is neat. Will have to add that to my list
of tricks.
I'm an electronic technician (really a systems specialist) by trade -
and I find that the important thing to do in cases like this is WRITE IT
DOWN. I may not use 'which' again for months ... and I'll forget it. I
might only do a re-phasing of the feedlines on an antenna system every
few years. I _will_ forget what I did last time! That's the hardest
part of linux or teching in general: forcing one's self either to
remember (next to impossible for me anymore) or to write it down (type
it out, whatever).
There's probably a console utility for that if I just knew the command.
" remember 'which' need (l)ater -store /dont-forget"
dave w
