On Tue, 2002-03-19 at 03:00, Charles A Edwards wrote: > On Sun, 17 Mar 2002 21:04:32 +0000 > John Richard Smith <[EMAIL PROTECTED]> wrote: > > > I recently downloaded an updated kernel version 2.4.8-26mdk.rpm > > which is said to be suited to LM8.1 . > > > > How can I install this without overwriting my existing kernel > > version k2.4.8-19mdk in /boot partition. > > > > When I went to install it using RPM package manager I am sure > > it was going to overwrite so I chose to leave it. > > > > I want to install kv2.4.8-16mdk in the same /boot partition as > > old kernel version and work out a Lilo boot script to boot it.So > > I bet it isn't that simple ? > > Can I do this ? > > > > > cd to the directory to which you downloaded the kernel. > Su to root and do: > rpm -ivh kernel-2.4.8-16mdk.rpm > > Using any editor open /etc/lilo.conf > Verify that the new kernel image listing was created that the initrd= is correct and >that the append options are also correct. > If you wish for the new kernel to be the default edit the 4th line of lilo.conf to >read default= 248-16 > Save the change and exit the editor. > > >From the terminal, still as root, enter: lilo > This writes your new lilo and on your next boot you will have the option to boot to >either of your installed kernels with the -18 being the default. > > Just so that you can see one that has been altered several time I have attached a >copy of mine. > > > Charles > ---- >
> Want to buy your Pack or Services from MandrakeSoft? > Go to http://www.mandrakestore.com It's also a good idea at the time you check the LILO settings, to do a "ls -l /boot" and look at what is linked to what. Pay particular attention to any flashing filenames as that indicates a broken link. I have found that sometimes, installing a new kernel has resulted in both a new entry in lilo.conf and changes in links which together effectively mean that I lost the ability to boot the old kernel. i.e. One lilo setting was pointing directly at the new kernel and the other was pointing at the old link, but the link had been updated to point at the new kernel. Clear? Maybe not. Here's an example: image=/boot/vmlinuz-2.4.8-26mdk label=linux root=/dev/hda5 initrd=/boot/initrd-2.4.8-26mdk.img image=/boot/vmlinuz-2.4.8-34.1mdk label=248-341 root=/dev/hda5 initrd=/boot/initrd-2.4.8-34.1mdk.img These two extracts from lilo.conf clearly provide the option to boot two different kernels, but if the first one were to read: image=/boot/vmlinuz label=linux root=/dev/hda5 initrd=/boot/initrd.img as it did from my original install, the kernel booted depends on where vmlinuz and initrd.img are linked. In my case, installing 2.4.8-34 resulted in the creation of the 248-341 label and relinking of vmlinuz and initrd.img to point at the 2.4.8-34 kernel. In effect, both lilo entries were pointing at the same kernel. That's OK if it works. It didn't and I had to boot in rescue mode to recover. OK, so I'm confused - if you are too, reply to this and I'll try to do a better explanation. Brian
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
