Re: Windows and DLLs

[David Jeske <jeske home chat net>]

On Wed, Oct 07, 1998 at 08:00:10PM -0400, John Kodis wrote:
> > > $ ls -l /proc/self/exe
> > > lrwx------   1 kodis  kodis   0 Oct  4 19:13 /proc/self/exe-> /bin/ls*
> > 
> > I looked into this a bit more carefully, and at least on my system,
> > this is not a 'standard' symbolic link, in that it gives back the
> > inode number, not the string 'path'. This makes it difficult to get
> > the full path of the executable back. For example, on my system:
> > 
> > Linux mozart 2.0.31 #1 Sun Nov 9 21:45:23 EST 1997 i586 unknown
> > 
> > [jeske@mozart self]$ /bin/ls -l /proc/self/exe
> > lrwx------   1 jeske jeske  64 Oct  6 23:45 /proc/self/exe -> [0801]:18385
> > 
> > According to the man page, this is exactly what it is supposed to give
> > back:
> 
> Yes, it seems that this is a fairly recent change in behavior.  I'd
> guess that it came about as a result of the change to dentry based fs
> code that went into the kernel around version 2.1.70 or so.  Too bad.
> Using `readlink("/proc/self/exe", buf, sizeof(buf))' is certainly a
> convenient mechanism when it's available.

Perhaps we can get someone to put in another proc entry with the old
behavior, or perhaps just a /proc/self/exe_path with the path to the
exe as a string.

-- 
David Jeske (N9LCA) + http://www.chat.net/~jeske/ + jeske@chat.net