up2date defaults to skipping kernel updates

[jeem machine]

On Wed, 28 Jul 2004 12:20:13 -0400, Robert Locke <rlocke at ralii.com> wrote:
> On Wed, 2004-07-28 at 09:43, jeem machine wrote:
> > Just go to /boot/grub.conf and change default to 0
> > Then it will always boot with the last kernel installed
> > Jeem
> >
> 
> Ummmm, careful on how you say that....
> 
> While rpm -i will place the "new kernel" as the first stanza in
> grub.conf, it also shifts the default= line to continue to point to
> whichever kernel was being booted by default before.
> 
> It is only through a post-installation function in yum or "perhaps no
> longer" in up2date that it will make the new kernel the default one.
> The problem in this thread is discussing the merits "or not" of this
> post-installation routine "automatically" pointing to the new kernel.
> It appears, at the moment, that kernel updates via up2date are now
> requiring us to manually edit the /boot/grub/grub.conf file and make the
> edit you are suggesting, but that needs to be done following each kernel
> update.  Currently, yum is making the change automatically.
> 
> --Rob
> 
> 
> 
> 
> --
> fedora-list mailing list
> fedora-list at redhat.com
> To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
> 
Thanks for pointing that out. I just found out myself and was confused.
Jeem