On Mon, 1 Dec 2008 10:20:49 +1300, Bruce Kingsbury wrote:
Errrr.. it does?
If I tell it to always boot 'the third' entry, and some update adds a newer kernel, all the other boot entries get bumped down the list (two places, since there's also a single user entry by default). Does grub automatically recognise that I now want to boot 'the fifth' entry?
If you use 'saved' instead of a number grub will instead boot the entry specified as 'savedefault'. Comments from menu.lst: ## default num <snip> # You can specify 'saved' instead of a number. In this case, the default entry # is the entry saved with the command 'savedefault'. # WARNING: If you are using dmraid do not change this entry to 'saved' or your # array will desync and will not let you boot your system. The link Craig posted below explains the savedefault setting. - Dean
2008/12/1 Craig Box <craig(a)dubculture.co.nz>:
On Sun, Nov 30, 2008 at 4:30 AM, Bruce Kingsbury <zcat(a)zcat.geek.nz> wrote:
BTW, the problem with changing "default=" is that every time there's a new kernel package, the one you want it to boot moves down one entry. That's why I didn't do it that way... The proper way it to 'pin' the kernel package I think, but I never figured out how to do that.
With 'default saved' and 'savedefault' defined in your kernel entries in grub, it will always boot the most recently used kernel, not the newest added one.
http://www.gnu.org/software/grub/manual/html_node/savedefault.html Craig