Roberto Angelo wrote:
> rpm -q -a | grep kernel
>
> to see what kernel parts are installed so download the new rpms with the same
> name (but number of verswion upgraded) and you have to download the initscripts
> rpm too so do that
>
> rpm -Uvh
>
> for all kernel rpms and iniscripts rpm too.
>
> After you have to tell lilo that you have changed the kernel (I don't know how
> because I use loadlin). In loadlin case you have to use new kernel linuz (see
> at /boot/linuz) to boot
>
Hi, Roberto, David and everybody else,
thank you for your answer. I have tried the command line you told me "rpm -q -a |
grep kernel", and got the following output:
kernel-2.2.9-19mdk
kernel-headers-2.2.9-19mdk
kernel-pcmcia-cs-2.2.9-19mdk
kernel-source-2.2.9-19mdk
=>kernelcfg-0.5-6mdk
But when I went to the ftp directory I couldn't find the last package
"kernelcfg-0.5-6mdk". It was not there. I downloaded the following files:
kernel-2.2.9-27mdk.i586.rpm
kernel-headers-2.2.9-27mdk.i586.rpm
kernel-pcmcia-cs-2.2.9-27mdk.i586.rpm
kernel-source-2.2.9-27mdk.i586.rpm
=>initscripts-4.16-26mdk.i586.rpm
I hope I've done everything right till now.
So, my first question is simple: Should I upgrade all the packages listed above
except the last one (kernelcfg-0.5-6mdk) which is not in the ftp directory and
don't bother about it?
And about initscripts rpms... You told me that they were important and that I
should install them too. The file that I have found in the same directory is
"initscripts-4.16-26mdk.i586.rpm". Please note that it is "26mdk" instead of
"27mdk" like the rest of the files. Is it ok? Should I worry? When doing the
upgrade do I have to install it first (before all the other files) or the order
doesn't matter?
Now let's go to the next question: Can I use the Kpackage to do the upgrade or I
am supposed to do it through the term (out of the X) using the second command line
that you used: "rpm -Uvh".
I received this message from the newbie mailing list. It is talking about
Roberto's message. And I became curious.
>Hi,
>
>No ! Never upgrade your kernel by � rpm -U �. You will erase the old
>kernel and if the new doesn't work your computer can not boot.
>
>Always use � rpm -i new_kernel � and if all work fine, you can delete
>the old with � rpm -e old_kernel �.
>
>
>Cordialement / Regards,
>
>David BAUDENS
>
So, how would I know that everything would have gone right. I keep both kernels
and keep two boot disks to boot each of them. That's what you were talking about,
David? In this case, even if the new kernel didn't work I would still have the old
one and would be able to boot it?
Ops! One last thing: I believe the only change I have to do in lilo.conf is:
image=/boot/vmlinuz-2.2.9-19.mdk
to
image=/boot/vmlinuz-2.2.9-27.mdk
Is it right? If I am wrong, someone please tell me.
Thanks to everybody,
Rodrigo Oliveira
