Re: system.map

[Daniel Phillips <phillips@bonn-fries.net>]

On January 2, 2002 08:39 pm, Tony Hoyle wrote:
> Timothy Covell wrote:
> > 	Of course, you can copy over the new System.map
> > file to /boot,  but their is no (easy) way of having more than
> > one active version via "lilo" or "grub".   And that could be 
> > considered a deficiency of the Linux OS.
> 
> ????  Just call it System.map-2.2.17, System.map-2.5.1, etc.  Sounds
> pretty 'easy' to me.

It is if you know the magic incantation for System.map.

> 'make install' does all this for you, btw.

I've never been sure what 'make install' does, or what it might do in the 
future.  I've always just installed according to the README.  After doing 
this by hand way too many times, and having ferretted out the truth about 
System.map, I wrote the following bash script:

   here=`pwd`
   kernel=`basename $here`
   make modules_install >/dev/null
   cp arch/i386/boot/bzImage /boot/bzImage-$kernel
   cp System.map /boot/System.map-$kernel
   cp .config /boot/config-$kernel
   lilo

I put it in /usr/src and use it as follows:

  cd /usr/src/linux-xx.xx.xx
  sudo ../install

This does everything you need, with the exception of editing lilo.conf.  Note 
that the name of the top level directory is the name of the install, so you 
would probably not want to do 'cd /usr/src/linux' where linux is a symlink.

This is x86-specific, obviously.

--
Daniel