Description of problem: I had previously modified my /etc/default/grub file to have different default kernel options (remove rhgb, etc) and also to disable the os prober. Today I got new updates and my /etc/default/grub file is back to the original contents as shipped with grub2. I thought this was supposed to be the file where customizations were intended to be made. Version-Release number of selected component (if applicable): grub2-1.99-7.fc16.x86_64 How reproducible: Just got the update, so can't really try again. Steps to Reproduce: 1.get grub2 update 2.see /etc/default/grub replaced 3. Actual results: customizations wiped out Expected results: customizations retained Additional info:
Another grub2 update, and another /etc/default/grub has been set back to what is apparently the grub2 default contents, the one line: GRUB_CMDLINE_LINUX="quiet rhgb" When I first installed f16 beta from the dvd, there was a whole bunch of customizations added to /etc/default/grub, customizations which are apparently responsible for the different kinds of menu entries I see in the initial grub.cfg file. By constantly wiping out /etc/default/grub, you also wipe out the ability to regenerate a grub.cfg file that looks even vaguely like the one you get following the initial anaconda install. What is the point of /etc/default/grub? Why not just hard code the default if every grub2 update is going to wipe out custom settings? I just installed grub2-1.99-9.fc16.x86_64 and got this behavior.
This is the sort of content anaconda leaves in /etc/default/grub: GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR="Fedora" GRUB_DEFAULT=saved GRUB_CMDLINE_LINUX="rd.md=0 rd.lvm=0 rd.dm=0 KEYTABLE=us quiet SYSFONT=latarcyrheb-sun16 rhgb rd.luks=0 LANG=en_US.UTF-8" I usually want to add: GRUB_DISABLE_OS_PROBER="true" since I chainload f16 and don't want f16's menu cluttered up with things I already get to a different way. Anyway, this all goes away when I get a new grub2 update.
*** This bug has been marked as a duplicate of bug 741045 ***