Hide Forgot
Description of problem: currently the grub2 process for updating the boot menu is fairly error prone and open to unexpected results. Editing the boot menu can be accomplished in one of two primary ways: 1) editing /boot/grub2/grub.cfg 2) editing /etc/default/grub, and then running: grub2-mkconfig -o /boot/grub2/grub.cfg The first interface is prone to unexpected reversion, as a subsequent run of grub2-mkconfig will overwrite any administrative changes. The second interface is prone to failure, as it requires the non-intuitive step (based on the relative easy of editing a grub 1 menu), of having to run a second utility to actually apply the changes to the real grub config. Version-Release number of selected component (if applicable): all grub2 How reproducible: always Steps to Reproduce: 1.edit /etc/grub2/grub.cfg 2.run grub2-mkconfig Actual results: changes from step 1 are overwritten Expected results: changes are preserved Steps to Reproduce: 1.edit /etc/default/grub 2.reboot Actual results: changes from step 1 are ignored Expected results: changes are applied Additional info: I think the first problem is solved about as well as it can be with the large DO NOT EDIT THIS FILE warning in the header As for the second problem, I think a small utility to merge the steps into a single step would be helpful, i.e a grub2-edit idea, like: #!/bin/sh $EDITOR /etc/default/grub grub2-mkconfig -o /boot/grub2/grub.cfg
I think this is a great idea. Forcing two steps when editing is terrible (see efi). P.
The problem with the old behaviour you seem to like so much is that user changes were in the middle of autogenerated code. This lead to problems when regenerating since the scripts had to figure what is user part and what is autogenerated and this lead to numerous bugs.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.