05-12-2016, 09:06 PM
There is a little trick that you might want to use. You can assign a hotkey to each menuentry when you edit /boot/grub/grub.cfg
EXAMPLE:
menuentry 'Korora 23 on /dev/sda4' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-5c185ea1-b08c-44cb-9279-cdb87e4168af' { etc...
can be assigned the hotkey "a" like this:
menuentry 'a - Korora 23 on /dev/sda4' --hotkey=a --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-5c185ea1-b08c-44cb-9279-cdb87e4168af' { etc...
So you don't have to arrow down and press ENTER, you just press "a" to boot Korora.
You can use a single letter, a to z, or a single number, 0 to 9. However, you can't use "c" or "e" because those already have a Grub menu function assigned - ("command line" and "edit")
EXAMPLE:
menuentry 'Korora 23 on /dev/sda4' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-5c185ea1-b08c-44cb-9279-cdb87e4168af' { etc...
can be assigned the hotkey "a" like this:
menuentry 'a - Korora 23 on /dev/sda4' --hotkey=a --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-5c185ea1-b08c-44cb-9279-cdb87e4168af' { etc...
So you don't have to arrow down and press ENTER, you just press "a" to boot Korora.
You can use a single letter, a to z, or a single number, 0 to 9. However, you can't use "c" or "e" because those already have a Grub menu function assigned - ("command line" and "edit")
Linux Lite 2.2 (64 bit), Quad core AMD A8-3870 with Radeon HD Graphics 6550D, 8GB DDR3, Ralink RT2561/RT61 802.11g PCI
Microsoft-free environment since 1996
Microsoft-free environment since 1996