On Mon, Jun 9, 2008 at 12:39 PM, sham pavman <shampavman.cg at gmail.com> wrote: > Hi, > From what i understand your trying to find out the path for > any command? If i am right then, you could use this > bash-3.2# type pkgrm > pkgrm is /usr/sbin/pkgrm > The advantage of using type is that it give a description of what sort of a > command you are using > > bash-3.2# type echo > echo is a shell builtin > > Alternatively a descriptive one would be the "find" (man find should be a > good starting point) > bash-3.2# find / -name ls -print > /export/downloads/coreutils-6.4/src/ls > /export/downloads/coreutils-6.4/tests/ls > /usr/bin/amd64/ls > /usr/bin/ls > > Regards > Shampavman >
Yup, that was one of the issues. What actually happened was that 'pkgrm' is not along the default path. I was not sure, if it was installed at all, at that stage. Even the usual `which program-name' did not work. My usual linux habit was to use 'locate' rather than any other means, so I installed it, and things worked the known linux way. I can find almost anything now, not only binaries. Yes, 'find' would work, but then, it would be quite verbose and slow. Frankly, I was not conversant with "type" command. Thanks for this input ... well, you learn something new every day ;-) Bish
