On Mon, 15 Sep 2003 18:31:46 -0700 Mark Knecht <[EMAIL PROTECTED]> wrote:
> On Mon, 2003-09-15 at 15:40, Lindsay Haisley wrote: > > > bzImage doesn't contain the system symbol map, but the symbol map is > > frequently used to translate numeric locations in bzImage into symbol names > > for debugging purposes. System.map isn't required. > > > > The file /usr/src/linux/arch/xxx/boot/bzImage gets copied, usually, to > > /boot/vmlinuz when one builds a kernel, so they're the same file, really. > > OK, so for a couple of years I've made a consistent 'mistake' because I > almost always do this copy by hand, but I never rename it. So the > bzImage files in my /boot directory, by convention, should really be > named vmlinuz, but I haven't been doing that. > No mistake, my friend. What you name the copy of the generated kernel on /boot is totally immaterial (read that statement again). The only thing that matters is that your grub or lilo info matches the name you chose. You may have many kernel images in /boot. Even if you name the kernal "junk,", if you call it "junk" in your lilo/grub references, it's cool. > > > > The other 2/3's are where do the System.map and config files come from? > If they are created by the above set of steps, then are they under > /usr/src/linux somewhere after I've built the kernel? The System.map (always this name) is always generated in the top level directory of the kernel source tree (/usr/src/linux.../). You can optionally copy it to /boot and give it any name. Your system will not run better or worse without a System.map file in /boot. An example, here is a lysting of my files in /boot lrwxrwxrwx 1 root root 22 Sep 10 07:35 System.map -> System.map-2.6.0-test5 -rw-r--r-- 1 root root 582820 Jul 4 08:26 System.map-2.4.20-r5 -rw-r--r-- 1 root root 834050 Aug 6 21:09 System.map-2.6.0-test2 -rw-r--r-- 1 root root 861825 Aug 29 21:02 System.map-2.6.0-test3-ip -rw-r--r-- 1 root root 868095 Sep 10 07:34 System.map-2.6.0-test5 ... lrwxr-xr-x 1 root root 17 Jul 27 16:47 bzImage -> bzImage-2.4.20-r5 -rw-r--r-- 1 root root 1209213 Jul 4 08:26 bzImage-2.4.20-r5 -rw-r--r-- 1 root root 2127731 Aug 6 21:09 bzImage-2.6.0-test2 -rw-r--r-- 1 root root 2302783 Aug 29 21:02 bzImage-2.6.0-test3-ip -rw-r--r-- 1 root root 2315221 Sep 10 07:34 bzImage-2.6.0-test5 Currently, I'm only using bzImage-2.6.0-test5; the other names are just leftover baggage. You can see a steady progression from my last 2.4 kernel through current. the ...test3-ip kernel was the first to contain all the necessary additions to run the shorewall firewall. A side note: I've never had any reason to use the System.map files in five years running linux, but I keep them just in case I ever have a kernel crash. Enjoy, -- Collins Richey - Denver Area if you fill your heart with regrets of yesterday and the worries of tomorrow, you have no today to be thankful for. -- [EMAIL PROTECTED] mailing list
