On Wed, May 08, 2002 at 12:41:28AM -0400, Andy Saxena wrote:
> On Mon, May 06, 2002 at 12:40:26AM -0700, Vineet Kumar wrote:
[snip]
> > It is on some levels; the symlink is dereferenced to get to the actual
> > code of the executable. A program can tell how it was called by looking
> > at argv[0], though. You should get the same result if you copy (instead
> > of symlinking) to a different name and running the copy. With the
> > symlink, the execution is identical, but the environment (containing the
> > command line) is different.
> >
Could OP explain how the "environment" is different? "argv[0]" is
not the environment and shouldn't effect execution unless the program
takes explicit actions based on the name it was invoked with (usually
a bad idea).
> Very interesting. Perhaps you could also tell me a way to look up the
> original symlink entry?
$ ls -l /usr/bin/x-terminal-emulator
lrwxrwxrwx 1 root root 37 Oct 1 2000
/usr/bin/x-terminal-emulator -> /etc/alternatives/x-terminal-emulator
$ ls -l /etc/alternatives/x-terminal-emulator
lrwxrwxrwx 1 root root 31 Apr 14 12:24
/etc/alternatives/x-terminal-emulator -> /usr/bin/gnome-terminal.wrapper
Aha, a shell script! Dang, keep meaning to change that alternative to
xterm...
> Also, how would i get a symlink to point to "xterm -mutt"? The man page
> is quite pathetic in its documentation.
You can't. You probably want a small shell script or alias. But I
don't recall a -mutt option for xterm ;-) (maybe "xterm -e mutt"?)
--
Eric G. Miller <egm2@jps.net>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
