I'm not sure if this is something that should be fixed but when using GRUB-2 the newest installed kernel is not always created as entry 0 (corresponding with the /etc/default/grub DEFAULT option of 0). One would expect that this automation would allow us to simply issue grub2-mkconfig and reboot to enter the new kernel but I wanted to pose the question here to find out if this is a valid expectation. Reproducible: Always Steps to Reproduce: 1.Install *-sources-3.2.2 (for example) 2.Update grub with these sources like normal (grub2-mkconfig) 3.Install *-sources-3.2.11 (for example) 4.Update grub with these sources like normal (grub2-mkconfig) Actual Results: The kernel entries in the grub configuration (created by /etc/grub.d/10_linux) are 3.2.2 and then 3.2.11 not 3.2.11 and then 3.2.2 like one would expect (again I'm open to this being disputed). With the default boot entry being zero the old kernel boots by default. Expected Results: The kernels are in ascending age order in the grub menu and the newest kernel will take place zero in the menu configuration.
Please indicate the full version of grub you are using. grub-2* is not useful.
Just noticed I was testing on grub-1.99-r2. I will verify if this still exists in the latest incarnation before continuing with this report.
Sorry to have wasted time with this report. Should've checked the latest release first. It is working as I expected in sys-boot/grub-2.00_beta3-r1. Marking as invalid since 1.99-r1 has been superseded by 2.00_beta3-r1.
