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 at niftyegg.com> wrote: > On 10/30/09, Rob Kampen <rkampen at 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 at centos.org > http://lists.centos.org/mailman/listinfo/centos > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20091101/395d8549/attachment-0004.html>