On Wednesday 31 January 2001 06:38, Tomás García Ferrari opined:
> Hi,
>
> I am trying to upgrade the kernel to kernel-2.2.16-3. I did it like this:
> > [root@host RPMS]# rpm -Uvh kernel-source-2.2.16-3.i386.rpm
> > kernel-headers-2.2.16-3.i386.rpm
> > kernel-source
> > ################################################## kernel-headers
> > ################################################## cannot remove
> > /usr/src/linux-2.2.14/include/linux - directory not empty cannot remove
> > /usr/src/linux-2.2.14 - directory not empty
> > [root@host RPMS]# rpm -ivh kernel-2.2.16-3.i586.rpm
> > kernel
> > ##################################################
>
> Then I add in /etc/lilo.conf this:
> > image=/boot/vmlinux-2.2.16-3
> > label=newlinux
> > read-only
> > root=/dev/hda5
>
> And when I run lilo -v I have this error message (kernel boot is too
> big!)...
>
> > [root@host RPMS]# lilo -v
> > LILO version 21, Copyright 1992-1998 Werner Almesberger
> >
> > Reading boot sector from /dev/hda
> > Merging with /boot/boot.b
> > Boot image: /boot/vmlinuz-2.2.14-5.0
> > Added linux *
> > Boot image: /boot/vmlinux-2.2.16-3
> > Kernel /boot/vmlinux-2.2.16-3 is too big
>
> Why is this happening? Any clue?
Well, if the above is accurate, you don't have the new kernel installed. I
saw source and headers, but no kernel. It will be kernel-2.2.16-3.i386.rpm.
The one you show is the source, which is the sourcecode not the kernel.
And, before you do it (as I did once and I know others have) don't do -Uch
on the kernel itself as that can create some very nasty consequences.
Instead, use -ivh and it will work just fine. As a matter of fact -ivh
would also work OK for the source and just leave 2 source trees installed
for 2 different kernel versions.
--
If only closed minds came with closed mouths.
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
