>
> On Wed, 2010-05-26 at 14:57 -0400, m.roth@xxxxxxxxx wrote:
>> Bowie wrote:
>> > m.roth@xxxxxxxxx wrote:
>> >> Bowie wrote:
>> <snip>
>> >> Once it's on, it's fairly stable... though the update of the kernel
>> >> does *not* always work correctly. With nearly 200 machines that I'm
>> >> rolling out
>> >> updates to, not infrequently, I'll see that the default= line in
>> >> /etc/grub.conf is reset... to the last kernel,rather than the
>> >> current, or to the debug kernel. I always have to check to verify
>> >> that it's pointing correctly before rebooting.
>> >>
>> > And, in fact, that is exactly what happened. The default= line was
>> > set to 1, so it booted the old kernel instead of the new one.
<snip>
>> I have *no* idea. I've even seen it pointing to 2, or 4. Anyone here
>> have any idea why it wouldn't *always* change the default to 0?
> ----
> Where did you get the kernel from? There is a reason why I ask this
> because all installed kernels I have installed that were built by CentOS
> do the right thing. As in update the boot sequence for you.
>
We build our own repository directly from an upstream CentOS mirror; in
this case, mirror.cc.vt.edu::centos/5.5. The exact same thing happened
with 5.4, and with some updates.
> The exception is The Upstream Real Time Kernel does not do this and is
> docoed.
Nope. 64 bit plain, mostly, with an occasional 32 bit, and fewer PAE. No
real time.
<snip>
mark
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
