Re: booting secondary kernels

Marcel J.E. Mol (marcel@mesa.nl)
Thu, 10 Jun 1999 19:40:33 +0200

On Thu, Jun 10, 1999 at 03:28:32PM +0200, naughton@poweronline.net wrote:
> I want to experiment with development kernels and still keep my
> original, good working kernel (SuSE 6.1 self-compiled), so i altered
> the makefile of the development kernel to install the kernel in
> /dboot, so that i can have my old one in /boot. Then i added the
> necessary lines to lilo.conf and told it that a secondary kernel
> /dboot/vmlinuz exists.
>
> Problem turns out to be, that when i boot the development kernel
> (the normal one works fine), the module info is loaded from
> /boot/system.map instead of /dboot/system.map, so the version is
> different and this results in an error.

I do it like this:
copy the new kernel and system.map to /boot/linux-x.y.z (or
linuxxyz for simplicity) and /boot/system.map-x.y.z, and do make
modules_install.
The 'production' kernel has a link to from /linux.
I have a small script the takes a default lilo.conf.first (containing
a dos entry and one for /linux), adds all /boot/linux* kernels
as seperate entries, writes that to /etc/lilo.conf and runs lilo.
The rc.sysinit gets the linux version from uname and links
/boot/System.map to the System.map-x.y.z. Works great for several years
now.

-Marcel

-- 
     ======--------         Marcel J.E. Mol                MESA Consulting B.V.
    =======---------        ph. 015-3101310/06-54724868    P.O. Box 112
    =======---------        marcel@mesa.nl                 2630 AC  Nootdorp
__==== www.mesa.nl ---____U_n_i_x______I_n_t_e_r_n_e_t____ The Netherlands ____


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/