L.V.Gandhi forced the electrons to say:
> However the output of $ldd 'which balsa' gave
> ~$ ldd 'which balsa'
> ldd: ./which balsa: No such file or directory
What Thaths wanted was the o/p of ldd `which balsa`, not the one you
typed in. The quotes are backticks (shift+~ on my comp). This runs the
command in between, and passes the o/p as commandline arguments to ldd.
The way you did it, it combined the words which and balsa, and passed
them as a single argument to ldd. ldd was looking for a file, whose name
was composed of 2 words, separated by a space (Think of My Documents :-).
Read the bash man page for details on how various quote characters work
in bash.
Thaths, let us decide on the current bash method of $(...) instead of
backticks? Apart from misunderstanding problems, they say this usage
nests better.
Binand
--
The prompt for all occasions:
export PS1="F:\$(pwd | tr '/[a-z]' '\134\134[A-Z]')> "
--------------- Binand Raj S. ([EMAIL PROTECTED])
----------------------------------------------
Find out more about this and other Linux India
mailing lists at http://lists.linux-india.org/
