Please excuse a possibly dumb question. Prior to the release of CentOS 5.4 I believe two updated 5.4 kernels were released as part of 5.3 2.6.18-164.el5 and 2.6.18-164.2.1.el5 Now that 5.4 is released we have just the 2.6.18-164.el5 kernel. Now the dumb question - what happened to the updated kernel? I now have workstations running 5.4 with the 164.2.1.el5 as they get yum update run regularly, however I do not reboot my servers as often and now find these do not have the later kernel. If some kind soul would please enlighten me..... Rob
Karanbir Singh wrote:
On 10/30/2009 02:52 PM, Rob Kampen wrote:
If some kind soul would please enlighten me.....
rpm -qa --last
164.2.1 was never released in the 5.3/updates
- KB
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Sorry - I missed that as my workstations use the .plus kernel. Thanx Rob
On Fri, Oct 30, 2009 at 10:52:55AM -0400, Rob Kampen wrote:
Prior to the release of CentOS 5.4 I believe two updated 5.4 kernels were released as part of 5.3 2.6.18-164.el5 and 2.6.18-164.2.1.el5 Now that 5.4 is released we have just the 2.6.18-164.el5 kernel. Now the dumb question - what happened to the updated kernel?
It's in the updates tree (for 32bit, anyway, so I'd expect 64bit)
kernel-2.6.18-164.2.1.el5.i686.rpm
Arrived around 4 days ago.
On 10/30/09, Stephen Harris lists@spuddy.org wrote:
On Fri, Oct 30, 2009 at 10:52:55AM -0400, Rob Kampen wrote:
Prior to the release of CentOS 5.4 I believe two updated 5.4 kernels were released as part of 5.3 2.6.18-164.el5 and 2.6.18-164.2.1.el5 Now that 5.4 is released we have just the 2.6.18-164.el5 kernel. Now the dumb question - what happened to the updated kernel?
It's in the updates tree (for 32bit, anyway, so I'd expect 64bit)
kernel-2.6.18-164.2.1.el5.i686.rpm
Arrived around 4 days ago.
--
rgds Stephen _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On 10/30/09, Rob Kampen rkampen@kampensonline.com wrote:
Please excuse a possibly dumb question. Prior to the release of CentOS 5.4 I believe two updated 5.4 kernels were released as part of 5.3 2.6.18-164.el5 and 2.6.18-164.2.1.el5 Now that 5.4 is released we have just the 2.6.18-164.el5 kernel. Now the dumb question - what happened to the updated kernel? I now have workstations running 5.4 with the 164.2.1.el5 as they get yum update run regularly, however I do not reboot my servers as often and now find these do not have the later kernel. If some kind soul would please enlighten me..... Rob
If you do not reboot the new kernel never activates.
Almost the same with libs and binaries. If an old binary is running then the update is not magically activated. For libs and binaries it is possible that the old buggy bits to continue to run at the same time that new version is available or running. Some interesting actions with programs like firefox, apache, python and other plugin friendly programs might be observed.
Some programs/ services like sshd do force a restart on the live system to side step some of these risks when reinstalled or updated.
It does pay to inspect the announcements, change log and release notes so a reboot is not delayed and the system left open to risk.
Yeah! I agree you ! If you get the newer kernel , you should reboot the computer ,then the OS will read the file called /etc/grub.conf That file decide which kernel you login ~~
On Sat, Oct 31, 2009 at 3:44 AM, NiftyCluster Tom Mitchell < niftycluster@niftyegg.com> wrote:
On 10/30/09, Rob Kampen rkampen@kampensonline.com wrote:
Please excuse a possibly dumb question. Prior to the release of CentOS 5.4 I believe two updated 5.4 kernels were released as part of 5.3 2.6.18-164.el5 and 2.6.18-164.2.1.el5 Now that 5.4 is released we have just the 2.6.18-164.el5 kernel. Now the dumb question - what happened to the updated kernel? I now have workstations running 5.4 with the 164.2.1.el5 as they get yum update run regularly, however I do not reboot my servers as often and now find these do not have the later kernel. If some kind soul would please enlighten me..... Rob
If you do not reboot the new kernel never activates.
Almost the same with libs and binaries. If an old binary is running then the update is not magically activated. For libs and binaries it is possible that the old buggy bits to continue to run at the same time that new version is available or running. Some interesting actions with programs like firefox, apache, python and other plugin friendly programs might be observed.
Some programs/ services like sshd do force a restart on the live system to side step some of these risks when reinstalled or updated.
It does pay to inspect the announcements, change log and release notes so a reboot is not delayed and the system left open to risk.
-- NiftyCluster T o m M i t c h e l l _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-
Karanbir Singh -
Majian -
NiftyCluster Tom Mitchell -
Rob Kampen -
Stephen Harris