Date:  Wed, 26 Aug 2009 18:09:35 -0400
From:  "Darrell D. Mobley" <dmobley (at mark) uhostme.com>
Subject:  [coba-e:15955] Re: Strange kernel stuff
To:  <coba-e (at mark) bluequartz.org>
Message-Id:  <AC9E4257D71245F5B3F842ED460DA126@HP9925NR>
In-Reply-To:  <25D803650B644741AC0A0B7AA5D6DF1D@raqware>
References:  <4A959A9C.4124.C8EEC8 (at mark) localhost> <4A95A0EF.11270.E1A496 (at mark) localhost> <25D803650B644741AC0A0B7AA5D6DF1D (at mark) raqware>
X-Mail-Count: 15955

> -----Original Message-----
> From: Gerald Waugh [mailto:gwaugh (at mark) frontstreetnetworks.com]
> Sent: Wednesday, August 26, 2009 4:26 PM
> To: coba-e (at mark) bluequartz.org
> Subject: [coba-e:15954] Re: Strange kernel stuff
> 
> Change default=1
>  to default=0
> and reboot.
> During reboot, you may hit the space bar, to allow time to select a kernel
> to boot, in case you have trouble you can boot a dif kernel
> 
> Also, I like a high resolution console screen, so I add vga=791 to the
> kernel line.
> kernel /vmlinuz-2.6.9-89.0.9.ELsmp ro root=/dev/md1 vga=791

Why would she want to change from an SMP kernel to a non-SMP kernel?
Shouldn't she just reboot the server?  I got the 2.6.9-89.0.9 kernel last
night, so it may be the server hasn't been rebooted to load the newest
kernel.  When I looked at mine, it was just as she explained.  I rebooted
and now uname -a reports the most recent kernel is running.

Also, does anyone know if the 2.6.9-89.0.9 kernel the latest one that
corrects the most recent vulnerability?