On Sat, Oct 31, 2009 at 1:05 PM, Galen Seitz <[email protected]> wrote:
> I have two CentOS 5 machines that I just updated to 5.4. On both
> machines the new kernel was inserted into the top of the list in
> grub.conf. However, on one machine the default line in grub.conf was
> changed such that the old kernel would boot by default. On the other,
> default was left at 0 so the new kernel would boot. This is not the
> first time I've seen this behavior. What controls whether the default
> gets changed on a kernel update? I can't think of anything I would
> have done that would cause these two machines to behave differently.
>
> thanks,
> galen
>
It's looking for a template - an existing entry in grub.conf that's
pretty darn close
to the kernel that's being installed. I think that 'close enough'
involves having
the same title (should be CentOS) the same-ish version (better be
2.6.18-something)
and the same xenedness and PAEness.
Ali
_______________________________________________
PLUG mailing list
[email protected]
http://lists.pdxlinux.org/mailman/listinfo/plug
