Fedora 20 Final blocker bug status report (ACTIONS REQUIRED: karma from QA, fixes from devs)

Gene Czarcinski gczarcinski at gmail.com
Thu Nov 28 22:19:10 UTC 2013

On 11/28/2013 12:17 AM, poma wrote:
> On 28.11.2013 03:25, Adam Williamson wrote:
>> * https://bugzilla.redhat.com/show_bug.cgi?id=864198 "grubby fatal error
>> updating grub.cfg when /boot is btrfs" - grubby - the problem here is
>> clearly defined. We are waiting on pjones to decide how to move forward
>> with this. Gene Czarcinski has posted a proposed change to
>> new-kernel-pkg to use grub2-mkconfig instead of grubby for updating
>> bootloader config, which would address this bug but be a late, major
>> change in our behaviour. The alternative would be to fix the problem in
>> grubby. Either way, this is waiting on Peter as the bootloader guy.
> "grub2-mkconfig" for the EXTLINUX too!?
> You should share whatever you have.
> LoL!
> Bee awesome.:!
I am going to regret opening my mouth here but being foolish has never 
stopped me before ;)

Actually, no, I would never use grub2-mkconfig to update a extlinux.conf 
file.  However, I do have this 308 lines bash script "program" which can 
"edit" a extlinux.conf file to add or remove a kernel entry.

Right now, about the only thing I really propose is to use the patch I 
created to handle the grubby/BTRFS problem and that only.  Yes, I 
"solve" the problem by not using grubby at all and instead use 
grub2-mkconfig to update (actually it completely rebuilds) the grub.conf 

It works.  I believe with a little code inspection (it is all 
bash-script) you can "prove" it only effects BTRFS.  Since BTRFS 
currently does not work, how could this be worse?

Post the F20 push, then there can be a discussion as to if this is a 
good general direction for the config-file-update in response to kernel 
install or removal.  And, then of course, there is the question of 
phasing a solution in or a "flash-cut" replacement ... there are 
advantages and disadvantages to both.

A major point I would like to make is that anaconda is depeneding on 
grub2-mkcondif to create the grub.cfg and grubefi.cfg files for almost 
all systems (arm and the S390 excluded).  So why shouldn't the 
post-install process also use grub2-mkconfig.  Besides, when I did it, I 
was really surprised at how easy it was to make it work.

I am going to regret writing this.


More information about the devel mailing list