From: "Robert L. Harris" <Robert.L.Harris@rdlg.net>
To: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: lilo and system maps?
Date: Thu, 4 Dec 2003 12:53:11 -0500 [thread overview]
Message-ID: <20031204175311.GF16568@rdlg.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1441 bytes --]
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.
Would it be possible, necessary, sane to have a lilo.conf similar to
this:
image=/boot/vmlinuz-2.4
label=current
map=System.map-2.4
read-only
image=/boot/vmlinuz-2.4.stable
label=stable
map=System.map-2.4.stable
read-only
optional
image=/boot/vmlinuz-2.6
label=2.6
map=System.map-2.6
read-only
optional
image=/boot/vmlinuz-2.6.stable
label=2.6-stable
map=System.map-2.6.stable
read-only
optional
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?
Robert
: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 --]
next reply other threads:[~2003-12-04 17:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-04 17:53 Robert L. Harris [this message]
2003-12-04 18:09 ` lilo and system maps? Andre Tomt
2003-12-04 18:15 ` Robert L. Harris
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=20031204175311.GF16568@rdlg.net \
--to=robert.l.harris@rdlg.net \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).