Replacing grubby with grub2-mkconfig in kernel install process

Josh Boyer jwboyer at gmail.com
Mon Jun 18 02:15:45 UTC 2012


On Sun, Jun 17, 2012 at 12:08 AM, Ben Rosser <rosser.bjr at gmail.com> wrote:
> It seems to me that we should make the boot menu more consistent somehow. I
> feel like the simplest solution is just to run grub2-mkconfig at every
> kernel update, and stop using grubby for this. Then everything would look
> consistent- the "Fedora Linux" boot option would have the latest kernel
> and all kernels would always be listed under the submenu. (As far as I know,
> this would just be a change to the kernel specfile, right?).

I'm not willing to change the kernel spec file for this.

The kernel calls 'new-kernel-pkg', which today is provided by grubby.
Despite the similar name, grubby actually works with more than just
grub and grub2.  It also supports bootloaders found on other
architectures, such as yaboot, elilo, silo, zipl, and U-Boot.  So,
rather than conditionalize all of this junk in the kernel spec file,
we call our nice purposeful abstraction script and whatever provides
that does the bootloader stuff for us.

If someone wants to make something else provide 'new-kernel-pkg' and
do similar magic, great.  If it's pushed into a per-bootloader thing
that would work too (though I would find it wasteful and suboptimal).
However, the abstraction grubby provides is actually _useful_ and
beneficial overall, so fixing any deficiencies because of the grub ->
grub2 transition would seem like a better idea to me.

josh


More information about the devel mailing list