On Tue, 16 Mar 2010 09:28:18 -0400 (EDT), Wolodja Wentland wrote: > On Tue, Mar 16, 2010 at 09:03 -0400, Stephen Powell wrote: >> >> My guess is that grub2 simply makes a list of all files in /boot which begin >> with linux-image, sorts them in descending order by the ASCII collating >> sequence, and the one which comes out on top is the default kernel. >> The problem is the decision to use "trunk" in the original 2.6.32 kernel >> image name. This sorts higher than any numeric value. I use lilo; so this >> doesn't affect me; but doesn't grub2 have some option for remembering >> the last kernel booted and making that the default? If you don't want to >> remove/purge the old kernel, it seems to me that that would be the way to go. > > Exactly. The relevant code is: > > --- /etc/grub.d/10_linux ----------------------------------------------- > ... > list=`for i in /boot/vmlinu[xz]-* /vmlinu[xz]-* ; do > if grub_file_is_not_garbage "$i" ; then echo -n "$i " ; fi > done` > prepare_boot_cache= > ... > ------------------------------------------------------------------------ > > Which obviously does not special-case -trunk-, so it sorts based on > LC_COLLATE. Looks as if the -trunk- name was a particularly bad choice > and I'm not sure what is the best way to solve this problem. > > The easiest way would be to enforce a strict naming scheme (maybe with > lintian) so the aforementioned code can stay as simple as it is today.
Oops! I meant to say "starts with vmlinuz", not "starts with linux-image". The package names start with linux-image. The kernel image file names start with vmlinuz. On a related note, when I build custom kernels with kernel-package, it has been my practice to put "custom" in the kernel image name. For example, a stock kernel might be "vmlinuz-2.6.32-3-686" and my custom version might be "vmlinuz-2.6.32-custom3-686". With this naming convention, anything starting with "custom" sorts higher than any stock kernel, providing that the stock kernel uses a numeric value for the upstream revision number. But "trunk" sorts higher than "custom"! Again, is there no way to set a default in grub2? Is there no way, for example, to make the last-booted kernel the default kernel? It doesn't affect me, since I use lilo. Therefore, I won't bother to research this myself. But surely there must be a way to set a default kernel in grub2 other than the one which sorts highest in the collating sequence. If not, then I have yet another reason to be glad that I use lilo! -- .''`. Stephen Powell <zlinux...@wowway.com> : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/512649073.19501971268749756766.javamail.r...@md01.wow.synacor.com
