Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: drow@mvista.com, kevinb@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: linux-proc readlink patch
Date: Thu, 10 Jan 2002 09:32:00 -0000	[thread overview]
Message-ID: <3C3DCF0B.6207@redhat.com> (raw)
In-Reply-To: <200201101556.JAA08179@duracef.shout.net>

Michael Elizabeth Chastain wrote:
> 
> Daniel Jacobowitz writes:
> > The link was 'magic' - its text was something along the lines of a
> > device and inode number, I believe.  It's not worth worrying about
> > unless someone actually reports it broken, I think.
> 
> I'm getting a nostalgia rush.
> 
> My recollection is the same as Daniel's.  /proc/$pid/exe has been a
> symlink for a long time, since 1996 or so.  And it's been usable all
> that time if you just open up the file and use it.
> 
> The original name was indeed "device:inode" which was unusable.  I don't
> know when the transitition to a real file name took place.  The last
> two stable versions of the kernel (2.2 and 2.4) have real file names
> instead of "device:inode" and I feel comfortable relying on a feature
> that is in the past two major versions.

Whew!  Thank you, Mr. History Buff!  ;-)


  reply	other threads:[~2002-01-10 17:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-10  7:56 Michael Elizabeth Chastain
2002-01-10  9:32 ` Michael Snyder [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-01-09 12:15 Daniel Jacobowitz
2002-01-09 12:51 ` Andrew Cagney
2002-01-09 14:24 ` Michael Snyder
2002-01-09 15:09   ` Daniel Jacobowitz
2002-01-09 15:40     ` Kevin Buettner
2002-01-09 15:45       ` Daniel Jacobowitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3C3DCF0B.6207@redhat.com \
    --to=msnyder@redhat.com \
    --cc=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kevinb@redhat.com \
    --cc=mec@shout.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox