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. My grub.conf file is of course consistent with this copy mistake showing that I boot a bunch of files called bzImage-xxx, and the machine certainly does boot, but I'll follow the convention from now on. Thanks. > /boot/vmlinuz (if it's the working kernel image) is _always_ required. > bzImage in the kernel build tree is only generated when one builds a kernel, > and can be deleted. Sure. Makes sense. > > > > QUESTION 2: What is the process to create these files if I want them? > > > > Do `make vmlinux` instead of `make bzImage` - they should be in the > > source root. (They may actually be there after doing make bzImage - have > > a look - but that's what you do if you don't want the compressed image.) Does 'make vmlinuz' make an uncompressed kernel? > > You don't need the uncompressed kernel. The proper sequence of commands (or > one of them) to create a new kernel is as follows: > > cd /usr/src/linux [assuming this is the base of your kernel source tree] > make menuconfig [set things the way you want them] > make dep > make clean > make bzImage modules > make modules_install > cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz-whatever > I'm sorry for not being clearer. The above steps, other than the second name in the last cp command, are what I always do. That was not what drop 2/3's of my question. You've now explained why I had bzImage files and had this one vmlinuz file. That's cool, but that's only 1/3. 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? Or are they only created if you do some other step not listed above? (If so, what's the step? The only other one I know of is to do 'make install' instead of the copy by hand. Maybe there is a 'make System.map' step or something I've never heard of. Thanks much to you, and also to Brett, Collins and Dived for their responses also. Cheers, Mark -- [EMAIL PROTECTED] mailing list
