Finding where an executable was run

[aglew at urbsdc.Urbana.Gould.COM]

>	"This would make lots of application programs easier to
>	install; you just copy it into somewhere on your PATH and it
>	will run."
>
>If an application uses this scheme to find its associated files, some
>useful Unix idioms cease to work.  For example, say that "rn" lives in
>/usr/news, but I don't want /usr/news in my PATH (too many nasty
>commands are also there).  At present I can put a link to /usr/news/rn
>in a directory that is in my path (e.g., my local bin).  With the
>proposed scheme, that would cause rn to look in my_local_bin/lib/* for
>its data files instead of in /usr/news/lib/*.
>
>  -=- Andrew Klossner   (decvax!tektronix!tekecs!andrew)       [UUCP]

Easy enough to do a readlink(), if you have used a symlink to place
the command on your path.