Warning: /boot/System.map

[gzf at gbr.msd.ray.com (Jerry Feldman {75562})]

Brian Conway wrote:
> 
> After you recompile the kernel, you should take /usr/src/linux/System.map
> and dump it into the directory that the old one had been in (usually /boot).
I keep 3 copies of the kernel and system map. 
When I build a kernel, the steps I use are:
make xconfig (or menuconfig or config).
make dep		#makes dependencies
make clean		#cleans out old .o files
make bzImage		#makes the kernel. 
make modules		#makes the modules
make modules_install	#copies the modules to the appropriate place
make bzlilo		#Backs up the current kernel and system map to .old
			#copies the new kernel and system map
			#executes the lilo command
Before installing a new kernel, I make sure that I have lilo commands for
all 3 kernels. I normally have lilo set up to boot in single user,
multi-user command line, and multi-user GUI, and Windoz. I also keep a
bootable rescue floppy so I don't paint myself into the corner. Using the
above procedure, I am normally assured to have my kernel and modules
coordinated. Lately, I have been working with a 2.2.7 kernel which still has
a few minor problems (more like nits). 


-- 
Jerry Feldman (HP On-Site Consultant) http://gbrweb.msd.ray.com/~gzf/
+-------------------------------------------------------+-----Note: ------+
| Raytheon Electronic Systems  (W) (781)999-1837/1-1837 | My views may not|
| Mail Stop:  S3SG10           (F) (781)999-4030/1-4030 | reflect the     |
| 180 Hartwell Road            (W) gzf at gbr.msd.ray.com  | views of my     |
| Bedford, MA 01730-2498      (FWD:H+W) gaf at blu.org     | employer.       |
+-------------------------------------------------------+-----------------+
-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).