- This topic has 21 replies, 3 voices, and was last updated Mar 25-9:53 pm by dukester.
-
Posts
-
Brian Masinick
Yeah, on this old beast, where I’m only running antiX, I just use the entire disk for the setup and it doesn’t bother with EFI/UEFI; just as well here. Regarding “custom”, yes, I’ve used that in the past. The most recent was a year or two ago when EndeavourOS wasn’t passing the correct strings to boot loaders on other systems. That “issue” is long past and I’ve not needed a custom section ever since.
In the ancient GRUB Legacy, I used to mess with it all the time, but back then, the setup was simpler and everything was in a text file that you could change and the effect was immediate as soon as you updated grub. You could easily save the configuration and experiment all day if you had the time.
GRUB still has text configuration files, but when you perform an update-grub command it looks at your setup in the text file /etc/default/grub, the values in this file determine whether only the current OS is included or if your system should probe for other operating systems.
--
Brian Masinick
dukester
it looks at your setup in the text file /etc/default/grub, the values in this file determine whether only the current OS is included or if your system should probe for other operating systems.
I’ll have to have a peek at this file. Never dealt with it before – because I didn’t realize that it existed I suppose.
--
dukesterBrian Masinick
/etc/default/grub looks similar to this:
# If you change this file, run 'update-grub' afterwards to update # /boot/grub/grub.cfg. # For full documentation of the options in this file, see: # info -f grub -n 'Simple configuration' GRUB_DEFAULT=0 GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR=<code>grep PRETTY_NAME /etc/lsb-release | cut -d= -f2 | cut -d\" -f2 2> /dev/null || echo Debian</code> GRUB_CMDLINE_LINUX_DEFAULT="quiet selinux=0" GRUB_CMDLINE_LINUX="" # Uncomment to enable BadRAM filtering, modify to suit your needs # This works with Linux (no patch required) and with any kernel that obtains # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...) #GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef" # Uncomment to disable graphical terminal (grub-pc only) #GRUB_TERMINAL=console # The resolution used on graphical terminal # note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the commandvbeinfo’
#GRUB_GFXMODE=640×480# Uncomment if you don’t want GRUB to pass “root=UUID=xxx” parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=”true”# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE=”480 440 1″GRUB_DISABLE_OS_PROBER=false
GRUB_BACKGROUND=/usr/share/wallpaper/grub/back.png `The line
GRUB_DISABLE_RECOVERY=”true” is one that I uncommented because I multi-boot my system.
On the other systems I was using earlier I left this file alone because they were single boot systems.
This system is newer and it DOES use UEFI and lots of other stuff, so practically everything here
is customized, not just GRUB.--
Brian Masinickdukester
GRUB_DISABLE_RECOVERY=”true”
What’s the significance/reason of this entry in context of multi-booting?
--
dukesterBrian Masinick
‘GRUB_DISABLE_RECOVERY’
If this option is set to ‘true’, disable the generation of recovery mode menu entries.
https://www.gnu.org/software/grub/manual/grub/html_node/Simple-configuration.html
--
Brian MasinickBrian Masinick
In other words, it spares the creation of additional entries that are used an/or generated during recovery mode.
You’d only want to turn that on if you were having repeated issues and specifically wanted to at least temporarily boot from an image marked as a recovery. I can’t think of a time when I’ve wanted to do this, even if I was experimenting with GRUB, so I keep recovery entries out of my GRUB menu.
--
Brian Masinickdukester
- You must be logged in to reply to this topic.
