On Tuesday, August 23, 2016 10:41:50 AM Peter Humphrey wrote: > On Tuesday 23 Aug 2016 05:18:02 Tom H wrote: > > On Mon, Aug 22, 2016 at 11:05 AM, Peter Humphrey <[email protected]> > > wrote: > > > Following today's marking of gummiboot as to be deleted in a month, I > > > had a look at efibootmgr in the wiki pages. It looks as though I'll be > > > able to use it instead, but one thing puzzles me: is it possible to > > > create a set of configs for several kernels, the way gummiboot does in > > > /boot/loader/entries/*.conf? Actually, I'd also like to specify each of > > > two kernel versions with three different command lines to start > > > different run levels. > > > > You can create multiple entries with efibootmgr but you'll have to > > boot to your firmware to choose a non-default option. > > Yes, that's how it was looking to me too. Not an ideal arrangement.
If you're not frequently jumping to a non-default boot environment, it's fine. Every time I update my kernel, I either add a new boot entry (or replace the oldest) pointing to my kernel, set the boot order to boot the newest entry by default (also configured via efibootmgr), and...I'm set. If the kernel fails to boot the system, I can still access my previous working kernel for rescue purposes. My current setup: *#* efibootmgr -v The hardest part, honestly, is remembering the commands to do it, since I only do it once every few months... -- :wq
signature.asc
Description: This is a digitally signed message part.
