> > On 12/20/05, G.W. Haywood <[EMAIL PROTECTED]> wrote: > > Hi there, > > > > No point in changing directory unless the value of your PATH variable > > starts with a dot. Did you use DOS once? :) > > > > Under Linux, you don't necessarily get what you think you get when you > > change directory and run a binary like that. DOS (and for all I know, > > Windoze too) will first look in the current directory for an executable > > but Linux won't, unless it's been told to. My guess is that it hasn't > > in this case. To be sure which binary you'll be running (unless you're > > sure which binary you'll be running:) you need to give the full path. > > Ged is correct. > > Type > > # which clamscan > > at your shell prompt and it will tell you where in your $PATH it is > finding the executable.
In this case it is not very important as it was still in his path after he'd issued the cd command. Understanding one's path is a good point, but this isn't the best example with which to make it. The real point of education is that these duplicate files can and do exist and that a good clean uninstall is needed for a good clean install. dp _______________________________________________ http://lurker.clamav.net/list/clamav-users.html
