grub2-mkconfig with 3.2.10 kernels?

[Colin J Thomson]

On Monday 19 Mar 2012 10:09:50 Michael D. Setzer II wrote:
> On 19 Mar 2012 at 7:47, Ed Greshko wrote:
> 
> > On 03/18/2012 11:00 PM, Michael D. Setzer II wrote:
> > > Just did an update and it included a new kernel, but then on
> > > reboot after running grub2-mkconfig noticed that the newest one was
> > > not first. Seems to be sorting the 9 before the 10?
> > > 
> > > Is this a bug?
> > > I use the default="0", so this makes it not use the latest?
> > 
> > FWIW, yesterday came a kernel update to 3.2.10-3 and everything seems
> > fine here. I've not modified anything and my grub.conf contains set
> > default="0".
> 
> The issue is that the order is coming up wrong.
> On my sytem, it adds the new kernel, but it is the in this order
> from the grub.cfg file.
> 
> menuentry 'Fedora Linux, with Linux 3.2.9-2.fc16.x86_64'
> menuentry 'Fedora Linux, with Linux 3.2.9-2.fc16.x86_64
> (recovery mode)'
> menuentry 'Fedora Linux, with Linux 3.2.9-1.fc16.x86_64'
> menuentry 'Fedora Linux, with Linux 3.2.9-1.fc16.x86_64
> (recovery mode)'
> menuentry 'Fedora Linux, with Linux 3.2.10-3.fc16.x86_64'
> menuentry 'Fedora Linux, with Linux 3.2.10-3.fc16.x86_64
> (recovery mode)'
> 
> Thus 0 is the 3.2.9-2 kernel, and the new 3.2.10-3 would be
> number  4?
> 
> Is yours listing 3.2.10-3 as being 0?

Michael, I am seeing the same as you after the kernel update with 3.2.10 being 
at the bottom of the list so not the default of 0.

I keep only two kernels so have temporarily changed the default to 2 so 3.2.10 
will be the kernel that is booted.

Colin
-- 
Fedora release 16 (Verne)
Registered Linux user number #342953