All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert L. Harris" <Robert.L.Harris@rdlg.net>
To: Andre Tomt <lkml@tomt.net>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: lilo and system maps?
Date: Thu, 4 Dec 2003 13:15:04 -0500	[thread overview]
Message-ID: <20031204181504.GG16568@rdlg.net> (raw)
In-Reply-To: <1070561388.15415.233.camel@slurv.pasop.tomt.net>

[-- Attachment #1: Type: text/plain, Size: 2089 bytes --]


Thus spake Andre Tomt (lkml@tomt.net):

> On Thu, 2003-12-04 at 18:53, Robert L. Harris wrote:
> > I'm messing around on one of my dev machines which has 4 possible
> > kernels installed.  2.4, 2.4-stable, 2.6, 2.6-stable (stable is the last
> > known good kernel).  I currently have my System.map files laid out as:
> > 
> > /boot/System.map-2.6.0-test11-bk2
> > /boot/System.map-2.6.0-test10-bk4
> > etc.
> ^^^
> 
> > This way when I install a new kernel I can copy the System.map to
> > /boot/System.map-2.6 instead of keeping up with all the version numbers?
> > lilo doesn't seem to like the map= arguements.  Does the kernel need the
> > System.map in a single place, can it figure out where it's at for a
> > multiple config?
> 
> Just stick with the System.map-$(uname -r) variant and it will just work
> automaticly. map= in lilo is not for System.map's.
> 

Upon reading the man page on lilo.conf again I realized that was the
wrong map, but was hoping there was some notation that'd allow for maps
other than "/boot/System.map" for the multiple kernels.

Ok, I've tried rdev and file, is there a "cleaner" way of getting a
kernel version other than:

{0}:/usr/share/doc/lire>strings /boot/vmlinuz-2.6 | grep -i 2.[46] | head
2.6.0-test11-bk2 (root@wally) #3 SMP Thu Dec 4 12:41:42 EST 2003
M2#6gbQ+
{2 6B
.2'4]
AG2{6
b2)42
2y6&LD
2U6;
214<|7
2"6:

Yes it's functional, I can live with it, just wondering if theres a
"better" way for when I'm updating servers at work and have no idea what
kernels are in /boot on the machine (some have been up longer than the
year+ I've been here).




:wq!
---------------------------------------------------------------------------
Robert L. Harris                     | GPG Key ID: E344DA3B
                                         @ x-hkp://pgp.mit.edu
DISCLAIMER:
      These are MY OPINIONS ALONE.  I speak for no-one else.

Life is not a destination, it's a journey.
  Microsoft produces 15 car pileups on the highway.
    Don't stop traffic to stand and gawk at the tragedy.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-12-04 18:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-04 17:53 lilo and system maps? Robert L. Harris
2003-12-04 18:09 ` Andre Tomt
2003-12-04 18:15   ` Robert L. Harris [this message]
2003-12-04 18:41     ` Maciej Zenczykowski
2003-12-04 18:45       ` Robert L. Harris
2003-12-04 18:25 ` Maciej Zenczykowski

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=20031204181504.GG16568@rdlg.net \
    --to=robert.l.harris@rdlg.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@tomt.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.