/boot partition and modules/kernels

[David A. Bandel]

On Wed, 26 Jun 2002 23:17:16 -0400
begin  Matthew Carpenter <matt at e-i-s.cc> spewed forth:

> I remember reading about someone keeing a /boot partition which holds
> their kernels as well as /lib/modules/2.x.x-x directories, which are
> then linked to in the original locations...  I have attempted this and
> have been running face first into a wall when attempting to load
> modules...  I'd be interested in hearing some pointers on this one.  I
> believe I read it in a post by David Bandel.
> 

no links.

OK, here's what I do:

/boot contains:
	kernel-x.x.x (usually called bzImage-2.4.x-xfs-1.1 or some such)
	System.map-x.x.x (same extension as kernel)
	/modules

/boot is not mounted by any distro, if/when I need to alter it, I mount
it, work with it, umount it.

my lilo.conf contains various images, such as:
image = /boot/bzImage-2.4.18-xfs-1.1
	label = foo
	root = /dev/hda2
	read-only

image = /boot/bzImage-2.4.18-xfs-1.1
	label = bar
	root = /dev/hda3
	read-only

I build the kernel on one partition (say /dev/hda2).  After a complete
install and test boot (usually via a boot disk w/ the kernel dd'd to it),
change lilo.conf, run lilo, copy /lib/modules to /boot/modules, then mount
/dev/hda3, cp -a /boot/modules to /lib/modules there.  This copying is
necessary because /boot is on /dev/hda1 which is never mounted,
/lib/modules/... needs to be accessed early on in the boot process (and so
must be on the root partition).

Now I can boot 27 or more different root partitions (distros) using the
same kernel and modules.

That help?

Ciao,

David A. Bandel
-- 
Focus on the dream, not the competition.
		-- Nemesis Racing Team motto