On Wed, 2012-03-21 at 11:17 -0400, Peter Jones wrote: > On 03/21/2012 02:27 AM, Adam Williamson wrote: > > On Wed, 2012-03-21 at 00:12 -0600, Chris Murphy wrote: > >> On Mar 21, 2012, at 12:08 AM, Chris Murphy wrote: > >> > >>> It seems reasonable to consider this a grubby bug, yes? > >> > >> > >> Considering grub2-mkconfig -o /boot/grub2/grub.cfg produces the exact > >> correct result, guess I'm not understanding the purpose of grubby. Are > >> we in transition? > > > > grubby is less 'drastic' that grub2-mkconfig. it takes the existing > > config and appends a new entry to it. grub2-mkconfig blows away the > > config and starts over again each time. > > > > i don't recall whether we ever made a specific decision to keep using > > grubby over grub2-mkconfig or whether it's just inertia, though. pjones > > might. > > We definitely want to keep using grubby instead of running grub2-mkconfig and > clobbering whatever's in your config file every time. > > Has somebody filed a bz about this issue? I haven't seen one referenced in the > thread. https://bugzilla.redhat.com/show_bug.cgi?id=805310 I haven't yet managed to reproduce, though. I'm running grub2 '1.99-19', I installed a kernel package, got no errors, rebooted, and the new kernel was booted. So it seems this doesn't hit every config, we'll have to figure out what the busted configs have in common. Can those experiencing issues with the new grub please take a look at the bug, check their symptoms match the reporter's symptoms, and provide as much info as possible? Thanks. -- 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
