[lkml]   [1998]   [Oct]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Different kernels coexisting on the same does it work??
At 23:58 12/10/98 +0200, Marc Corel wrote:
>Originally, I have redhat 5.0/kernel 2.0.32 on my linux box.
>I went downloading kernel 2.0.34 and 2.0.35, did installed them in their
>respective directories. That gives me following directories in /usr/src:
>..What I did is to run make config/make dep/make clean/make_modules,
>make modules_install in each directory and copied their zImage in
>- cp /usr/src/li/usr/src/linux-2.0.32/arch/i386/boot/zImage
>-cp /usr/src/li/usr/src/linux-2.0.34/arch/i386/boot/zImage
>-cp /usr/src/li/usr/src/linux-2.0.35/arch/i386/boot/zImage
>Of course I also did:
>In /boot: ln -sf vmlinuz-2.0.32 vmlinuz
> ln -sf vmlinuz-2.0.34 vmlinuz
> ln -sf vmlinuz-2.0.35 vmlinuz
>Finally, in /etc/lilo.conf , there are several stanzas of my several


Maybe you should just sumlink your latest kernel (2.0.35) to vmlinuz and in
lilo put new stanzas that point to vmlinuz-2.0.32 and vmlinuz-2.0.34.
then, label them linux32 and linux34, for instance, and 2.0.35 could just
be linux or even linux35. This one could either be made default with
(default=linux35) or just placed as the first stanza. so you could hit tab
when the lilo prompt comes up and then type in the label of the kernel you
want to run.

here is an example (modified from the example in the lilo HOWTO)

image = /boot/vmlinuz # your zImage file which is symlinked to vmlinuz-2.0.35
root = /dev/hda1 # Your linux partition (assuming it is the first one)
but use whatever number yours is.
label = linux35 # any name you want
read-only # mount root read-only

image = /boot/vmlinuz-2.0.34 # your 2.0.34 kernel
root = /dev/hda1 # i think this is right
label = linux34 # any name you want

mage = /boot/vmlinuz-2.0.32 # your 2.0.32 kernel
root = /dev/hda1 # i think this is right
label = linux32 # any name you want

>II) Whatever kernel I m bootin, the config files stay the same...but
>this cause a problem:
>for ie..on kernel 2.0.32 IP_forwarding was not built in. On kernel
>2.0.34 I specifically recompile IP_forwarding in, but there s no
>appearent difference between both.

maybe because you symlinked all three kernel images to the same name.

>III) Is the way I ve configured my system right (with those 3 kernels)??
>To make sure I m bootin the kernel of my choice, I copied the zImage of
>ech kernel on a floppy. So I just boot with the right floppy

my suggestion above should work.

hope that helps.

adrian b.

The law of gravity says no fair jumping up without coming back down.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:45    [W:0.068 / U:5.900 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site