Fri 26 Jul 2013 03:41:39 AM UTC, original submission:
Example use case:
Home PC, has Linux on sda, Windows 8 on sdb, deprecated (non-bootable) Windows 7 environment also on sda with data that must be kept.
Current behavior:
Vendor kernel update re-writes boot menu entries, correctly hides old Linux entries behind submenu. Adds broken Windows 7 entry as primary menu named "Windows" and adds working Windows 8 entry as primary menu but names it "Recovery environment for Windows 8 (/dev/sdb)" which confuses non-technical spouse who also uses said PC.
Requested behavior:
Allow sysadmin to override all the multiple files in /etc simply by making changes to grub.cfg rather than monkeying with executable permissions in multiple files in /etc.
One suggestion would be to have an override flag in grub.cfg such as:
GRUBCFG_OVERRIDE_ETC_FILES = Yes
When grub2-mkconfig (or equivalent) runs, priority is given to changes in grub.cfg, grub2-mkconfig reports out to a logfile any changes that were deferred.
The grub2 method of numerous config files in multiple locations (eg: /boot/grub2, /etc/grub2, /etc/default/grub2, /etc/sysconfig/grub2, etc) over-automates and over-complicates the process to the point where it's almost unmanageable without significant time investment, well beyond what was needed to become proficient working with grub or lilo and (IMHO) well beyond what's needed to become proficient managing a boot loader.
Can we please get the option to simplify this for easier management?
|