Dennis Robertson wrote:
>
> I am posting to this list because my question has elements similar to
> the post on kernel naming answered by Warren Doney.
> I have downloaded(from kernel.org), installed and recompiled kernel
> 2.2.14 to replace kernel 2.2.13-7mdk in my LM6.1.
> I thought I should make a new boot disk but when I try mkbootdisk 2.2.14
> I get: /boot/vmlinuz-2.2.14 does not exist. This is true enough and the
> /boot directory refers only to bzImage(the new kernel) while containing
> references to system map, module-info and vmlinuz(all 2.2.13-7mdk).
> /usr/src contains directories linux, linux-2.2.13 and linux-2.2.14.
> Questions. How do I make a boot disk for the new kernel? How do I
> remove references to the old kernel? Do I rename bzImage to
> vmlinuz-2.2.14? If I uninstall 2.2.13 kernel, headers and source using
> kpackage, would that do it?
> Can I convert the .tar.gz file for 2.2.14 to an rpm?
> All inexpert questions I know but help would be appreciated.
> --
> Dennis Robertson 2/2 Sylvia Street NOOSAVILLE QLD 4566 AUSTRALIA
> Phone: 61 7 54742343 Mobile: 0419 535539 Fax: Phone first for setup.
See what happens if you cp /boot/bzImage to
/boot/vmlinuz-2.2.14-XXxxx where XXxxx is the
version number you find in /lib/modules/2.2.14XXxxx
the mkbootdisk script will only do a kernel named
vmlinuz-whatever.
Then try it...
If it works o.k., its safe to configure/run lilo
to point to it.
-WBD
