public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: "Albert D. Cahalan" <acahalan@cs.uml.edu>
Cc: reese@isn.net (Garst R. Reese),
	linux-kernel@vger.kernel.org (linux-kernel)
Subject: Re: small feature request
Date: Thu, 06 Dec 2001 18:33:21 +1100	[thread overview]
Message-ID: <12671.1007624001@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Thu, 06 Dec 2001 01:58:55 CDT." <200112060658.fB66wtp351314@saturn.cs.uml.edu>

On Thu, 6 Dec 2001 01:58:55 -0500 (EST), 
"Albert D. Cahalan" <acahalan@cs.uml.edu> wrote:
>Keith Owens writes:
>> "Garst R. Reese" <reese@isn.net> wrote:
>
>>> Would it possible to put a header on System.map indicating the kernel
>>> version?
>>> Sometimes my little brain forgets what kernel System.old is for.
>>
>> It is on my list for kbuild 2.5, once I start on the new design for
>
>Nooooo!!!!!
>
>Don't break stuff by adding headers. There is already a version
>in the file. It's in decimal, which sucks, but this will find it:
>
>grep ' Version_' System.map
>
>Adding a random 128-bit ID might be nice, as long as it's done
>in the same sort of way and is available via /proc. Something
>like this would do:  kern_128_id_UkZd1JLdOvAsALfFEL1UI

Strange, that is exactly what I was think of, adding symbols containing
information that tie the kernel, modules and System.map together more
reliably than the current "use some random System.map" method.

Do you want those exclamation marks back so they can be recycled?


  reply	other threads:[~2001-12-06  7:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-01  0:23 small feature request Garst R. Reese
2001-12-01  1:51 ` george anzinger
2001-12-01 11:49   ` Thomas Hofer
2001-12-01  3:25 ` Keith Owens
2001-12-01  3:42   ` Garst R. Reese
2001-12-06  6:58   ` Albert D. Cahalan
2001-12-06  7:33     ` Keith Owens [this message]
2001-12-06  8:51     ` Garst R. Reese

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=12671.1007624001@kao2.melbourne.sgi.com \
    --to=kaos@ocs.com.au \
    --cc=acahalan@cs.uml.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reese@isn.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