Here is something that's happened to me two or three times... I upgrade a program on my system, that was originally a RPM file. I first remove the RPM(s), install the program via ./configure; make; make install. Often, the location of the binary is different, but my system keeps looking for the binary in the old place. For instance, I just upgraded my vim 5.3 to vim 5.5. The 5.3 version was the one that came with redhat, the 5.5 was the upgraded version that I compiled from the source. The RPM had the binary in /usr/bin, where as the new version from the source put the binary in /usr/local/bin. When I type vim at the command prompt, it returns: bash: /usr/bin/vim: No such file or directory. But I can type the absolute path, and get it running. Where and how does it 'remember' where it was? Should it search all the paths in my PATH environment variable for the binary? /usr/local/bin is the 1st on listed, whereas /usr/bin is the 3rd. Thanks for any insight. -Rob. -- ----------------------------------------------------------------- Rob Hudson <[EMAIL PROTECTED]> Web Developer Visit the EUGLUG homepage at http://eugene-linux.cyber-dyne.com -----------------------------------------------------------------
