[PLUG] Kernel size?

Rich Shepard rshepard at appl-ecosys.com
Mon Sep 9 20:39:39 UTC 2002


On Mon, 9 Sep 2002, Anthony Schlemmer wrote:

> I think that would depend on how you compiled your kernel. If you 
> compile your kernel so that many of the features are in modules you do 
> tend to end up with a smaller kernel. 

Tony,

  Is is modular. When I looked more closely I saw this:

-rw-r--r--    1 root     root       804587 Aug  7 10:02 vmlinuz-2.4.18-10BOOT
-rw-r--r--    1 root     root      1030147 Apr 18 07:45 vmlinuz-2.4.18-3
-rw-r--r--    1 root     root      1167673 Sep  9 16:01 vmlinuz-2.4.19

  Apparently, bzImage was copied to vmlinuz-2.4.19 for me.
 
> Make sure you do a: "make modules modules_install" So your modules are 
> compiled and in place for your new kernel.

  Yup. Did these, too. However, there's no module-info for the new kernel.
This is what I have in /boot:

boot.b                    kernel.h                  System.map-2.4.18-3
bzImage                   lost+found/               System.map-2.4.19
chain.b                   message                   vmlinux-2.4.18-10BOOT*
config-2.4.18-10BOOT      module-info@              vmlinux-2.4.18-3*
config-2.4.18-3           module-info-2.4.18-3      vmlinuz@
grub/                     os2_d.b                   vmlinuz-2.4.18-10BOOT
initrd-2.4.18-10BOOT.img  System.map@               vmlinuz-2.4.18-3
initrd-2.4.18-3.img       System.map-2.4.18-10BOOT  vmlinuz-2.4.19

  The module-info link points to the 2.4.18-3 file (there's no module-info
for the 2.4.18-10 kernel, either. System.map points to System.map-2.4.19.

  After what I've gone through the past couple of weeks, I want to be
certain of what I'm doing before I get into deep trouble. :-) Ergo, my
hesitation when I'd charge ahead in the past.

  Also, here's how I set up /boot/grub/grub.conf (a.k.a.
/boot/grub/menu.lst):

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /boot/, eg.
#          root (hd0,1)
#          kernel /vmlinuz-version ro root=/dev/hda1
#          initrd /initrd-version.img
#boot=/dev/hda
default=2
timeout=10
fallback=1
title linux (2.4.19)
	root (hd0,1)
	kernel /vmlinuz-2.4.19 ro root=/dev/hda1
title linux-old (2.4.18-10BOOT)
	root (hd0,1)
	kernel /vmlinuz-2.4.18-10BOOT ro root=/dev/hda1
	initrd /initrd-2.4.18-10BOOT.img
title linux single (2.4.18-10BOOT)
	root (hd0,1)
	kernel /vmlinuz-2.4.18-10BOOT ro root=/dev/hda1 single
	initrd /initrd-2.4.18-10BOOT.img
title linux (2.4.18-3)
	root (hd0,1)
	kernel /vmlinuz-2.4.18-3 ro root=/dev/hda1
	initrd /initrd-2.4.18-3.img

  I _think_ the ''fallback'' phrase is in the right place. Once I know it's
working properly I'll change the linux single to the 2.4.19 kernel.

Thanks,

Rich





More information about the PLUG mailing list