LISTSERV - SCIENTIFIC-LINUX-USERS Archives

SCIENTIFIC-LINUX-USERS Archives

October 2014

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

	LISTSERV Archives
	SCIENTIFIC-LINUX-USERS Home
	SCIENTIFIC-LINUX-USERS October 2014

	Log In
	Register

	Subscribe or Unsubscribe

	Search Archives

Options:	Use Monospaced Font Show Text Part by Default Show All Mail Headers
Message:	[<< First] [< Prev] [Next >] [Last >>]
Topic:	[<< First] [< Prev] [Next >] [Last >>]
Author:	[<< First] [< Prev] [Next >] [Last >>]

Subject:	Re: SL7rc2 grub2 setting wrong kernel version as default after a kernel update
From:	Bill Maidment <[log in to unmask]>
Reply To:	Bill Maidment <[log in to unmask]>
Date:	Fri, 10 Oct 2014 18:26:51 +1100
Content-Type:	text/plain
Parts/Attachments:	text/plain (24 lines)

Thanks again Akemi.
When I looked at the bugzilla there was a new fix (for /usr/share/grub/grub-mkconfig_lib) suggested today that worked for me.

Regards
Bill Maidment 
 
-----Original message-----
> From:Akemi Yagi <[log in to unmask]>
> Sent: Thursday 9th October 2014 23:51
> To: Users, Scientific Linux ([log in to unmask]) <[log in to unmask]>
> Subject: Re: SL7rc2 grub2 setting wrong kernel version as default after a kernel update
> 
> On Thu, Oct 9, 2014 at 3:20 AM, Bill Maidment <[log in to unmask]> wrote:
> > After a yum update the latest kernel is set as the second entry rather than the first entry in the boot menu.
> > This seems to be because it sorts the kernel name using a simple alpha-numeric test rather than a more intelligent version number test
> 
> What you are seeing is a known bug as detailed in this upstream bugzilla:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1124074
> 
> Akemi
> 
>

ATOM RSS1 RSS2

LISTSERV.FNAL.GOV