All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert L. Harris" <Robert.L.Harris@rdlg.net>
To: Maciej Zenczykowski <maze@cela.pl>
Cc: Andre Tomt <lkml@tomt.net>, Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: lilo and system maps?
Date: Thu, 4 Dec 2003 13:45:07 -0500	[thread overview]
Message-ID: <20031204184507.GK16568@rdlg.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0312041935170.26684-100000@gaia.cela.pl>

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

Thus spake Maciej Zenczykowski (maze@cela.pl):

> > 
> > {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
> 
> Of course the correct solution is to have the kernel version in the file 
> name...  and have linux-current or whatever as a symlink.  Besides truth 
> be told the kernel version is far too little to identify a kernel anyway, 
> there's also compilation options - they can change a lot - and all the 
> patches which were/are applied to it.  I keep System.map-`uname -r`,
> vmlinuz-`uname -r`, .config-`uname -r`, descr-`uname -r` in my /boot dirs 
> - the first three come from the kernel and the last is a text file 
> containing notes about what patches were applied (I keep an up to date 
> descr file in each kernel source dir).
> 
> Cheers,
> MaZe.
> 


I'm maintaing machines that pre-exist me and many don't have
vmlinuz-`uname -r` naming and can't quite reboot the machine on
different kernels just to find out what it is.

Did the symlink think but it got ugly after a while when I had 6 kernel,
6 System.map files and a bunch of symlinks.  Once I fully drop the 2.4
on this set of machines I can move back but it was just ugly for a
while.


: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:46 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
2003-12-04 18:41     ` Maciej Zenczykowski
2003-12-04 18:45       ` Robert L. Harris [this message]
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=20031204184507.GK16568@rdlg.net \
    --to=robert.l.harris@rdlg.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@tomt.net \
    --cc=maze@cela.pl \
    /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.