On Thu, Sep 11, 2014 at 08:27:46AM -0700, Matt Ventura wrote: > Quick question: I want Debian to not switch Grub2 to a new kernel > when I update > it, since I have a custom kernel on a particular machine. When I > install a new > kernel from apt, I don't want to immediately use it. What's the > cleanest way of > doing this?
How does your custom kernel get into the grub2 configuration - i.e. which bit of /etc/grub.d defines the custom kernel boot instructions? If it's a custom file (XX_custom) that you wrote yourself, make sure it is numbered lower than the files which generate the lines for Debian/other kernels, it will then be the 'first' OS that is defined. I think '06_' would be suitablly low (the first OS-defining configuration item in my directory is 10_linux, so you'd want earlier than that, but after some of the pre-OS boiler plate, the latest of which for me is 05_debian_theme). Grub2 defaults to the first item (this is configurable in /etc/default/grub). Once you've made the necessary changes run update-grub to generate the grub2 config file. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140912125745.ga5...@bryant.redmars.org
