Kernel packages are designed to coexist with other kernel package
versions. Other packages are not. If you update a kernel you are
replacing it. If there is a problem with your new kernel, you don't have
another kernel to test with to try and isolate the issue, because you just
replaced it.
On Sun, 16 Oct 2011, Musayev, Ilya wrote:
I would agree with you if this would be an existing OS, but since it's a fresh
install and we burn tested the kernel, why keep both?
Unless I do install and remove of old, I'm not aware of any reason why update
would be bad for a fresh OS installation.
Thanks
ilya
-----Original Message-----
From: rhelv5-list-boun...@redhat.com [mailto:rhelv5-list-boun...@redhat.com] On
Behalf Of Barry Brimer
Sent: Sunday, October 16, 2011 12:38 AM
To: Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list
Subject: Re: [rhelv5-list] Kernel update via kickstart on rhel5.7
On Sat, 15 Oct 2011, Musayev, Ilya wrote:
I'm a bit puzzled, I was under impression in the %post of kickstart I can mount
the NFS share and install/upgrade the new kernel. For some reason though, the
kernel would not get updated.
I have something like this in my post:
%post
mkdir /mnt/update
mount nfsserver:/update /mnt/update
rpm -iUvh kernel-2.6.18-274.3.1.rpm
For some reason this does not work. I cannot use YUM in this case due to some
other issue.
You *NEVER* want to update a kernel RPM .. always install.
rpm -ivh /path/to/kernel.rpm is correct.
_______________________________________________
rhelv5-list mailing list
rhelv5-list@redhat.com
https://www.redhat.com/mailman/listinfo/rhelv5-list
_______________________________________________
rhelv5-list mailing list
rhelv5-list@redhat.com
https://www.redhat.com/mailman/listinfo/rhelv5-list
!DSPAM:4e9a6e39253726317911594!
_______________________________________________
rhelv5-list mailing list
rhelv5-list@redhat.com
https://www.redhat.com/mailman/listinfo/rhelv5-list
