On Thu, 2012-08-09 at 15:34 -0400, Jan Vcelak wrote: > > I offer my help to "improve" the situation by testing or providing > > patches if involved parties would like to. > > This is great! I can try to identify other "base" packages with the > same problem. There should not be many. > > The question is, what is the best solution. If the configuration file > should be created in the correct location, even with probably > non-functional content which needs some manual changes. Or place a > template file somewhere else, for example into /usr/share/package. > I would be good with both of these solutions. > > And we still do not know if'Anaconda people and other involved people > will agree. The reason anaconda writes /etc/default/grub is that it can actually contain different things depending on the install config. Most notably, the default timeout can change depending on whether you're installing a single-boot or dual-boot system; the intent is that the timeout is 0 for a single-boot system but 5s or 10s or something for dual-boot. I think this might have broken in recent releases, but it's the intent, at least. It also writes different values for serial console installations, and can configure a bootloader password. See pyanaconda/bootloader.py , around line 1730 (that's in the f17 branch) - write_defaults(self) . I don't think this prevents us from including a 'template' /etc/default/grub in the grub2 package (though I actually thought it already had one, I'm sure I've fixed bugs in it...), but it's important to note it can't be relied upon to match what anaconda writes. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
