public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: Tom Holroyd <tomh@po.crl.go.jp>
Cc: marcelo@conectiva.com.br,
	kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Extraversion in System.map?
Date: 08 Apr 2002 02:15:20 -0400	[thread overview]
Message-ID: <1018246521.1534.145.camel@phantasy> (raw)
In-Reply-To: <Pine.LNX.4.44.0204081502180.548-100000@holly.crl.go.jp>

On Mon, 2002-04-08 at 02:07, Tom Holroyd wrote:

> As part of my penance for using the wrong System.map file in the
> readprofile data I sent out, I have prepared a patch to readprofile
> that makes it check the version of the file against the kernel.
> 
> Much to my dismay, the extraversion code ('-pre6' for example) does
> not appear to be anywhere in System.map.  Or am I wrong?  If not, why
> not, and can this be fixed?  After all, symbols can and do change
> between -pre versions.

Eh, no kernel version is associated with System.map.  It has no embedded
information, what-so-ever, aside from the symbols.

Do what everyone else does and name your System.map appropriately, i.e.
System.map-2.5.8-pre2 and then on boot symlink System.map to
System.map-`uname -r`.  Most (all?) distributions do this for you
already.

You can also pass readprofile the -m flag to specify the map file to
use.  A little script that does "readprofile -m System.map-`uname -r`"
would work fine.

	Robert Love


  reply	other threads:[~2002-04-08  6:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020405060509.GB30807@holomorphy.com>
2002-04-08  6:07 ` Extraversion in System.map? Tom Holroyd
2002-04-08  6:15   ` Robert Love [this message]
2002-04-08  9:41     ` Miquel van Smoorenburg
2002-04-08  6:18   ` Keith Owens
2002-04-08  6:29     ` Tom Holroyd
2002-04-08  6:36       ` Keith Owens

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=1018246521.1534.145.camel@phantasy \
    --to=rml@tech9.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=tomh@po.crl.go.jp \
    /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