begin quoting Chuck Esterbrook as of Wed, Sep 12, 2007 at 04:55:11PM -0700: > On 9/12/07, Christopher Smith <[EMAIL PROTECTED]> wrote: > > Chuck Esterbrook wrote: > > > Let's say I have a script at /usr/bin/foo which is really just a link > > > to /usr/local/blah/bin/foo > > > > > > When I type "foo" at the command prompt (say bash), I would like the > > > foo script to know where it's really homed at. However, "dirname $0" > > > in that script will give "/usr/bin" instead of "/usr/local/blah/bin". > > > > > > Is there a way for a script to find out where it's really located? > > > > > man realpath > > Thanks, but that's C and I'm in bash. I could write up a little > utility, but I poked around more and found "readlink" which does the > trick.
It's C? [curry] ~> which realpath /usr/bin/realpath [curry] ~> uname -a Linux curry 2.6.18-4-686 #1 SMP Wed May 9 23:03:12 UTC 2007 i686 GNU/Linux [curry] ~> Perhaps an apt-get is needed? :) /me looks at the realpath manpage Hm. It says: "Please note that mostly the same functionality is provided by the `-f' option of the readlink(1) command." Different authors. Dmitri or Lars and Robert. -- Perhaps "realpath(1)" should have been specified? Stewart Stremler -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
