<div class="gmail_quote">On Sun, Jun 17, 2012 at 10:15 PM, Josh Boyer <span dir="ltr"><<a href="mailto:jwboyer@gmail.com" target="_blank">jwboyer@gmail.com</a>></span> wrote:<br><blockquote style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class="gmail_quote">
<p>I'm not willing to change the kernel spec file for this.<br>
<br>
The kernel calls 'new-kernel-pkg', which today is provided by grubby.<br>
Despite the similar name, grubby actually works with more than just<br>
grub and grub2. It also supports bootloaders found on other<br>
architectures, such as yaboot, elilo, silo, zipl, and U-Boot. So,<br>
rather than conditionalize all of this junk in the kernel spec file,<br>
we call our nice purposeful abstraction script and whatever provides<br>
that does the bootloader stuff for us.<br>
<br>
If someone wants to make something else provide 'new-kernel-pkg' and<br>
do similar magic, great. If it's pushed into a per-bootloader thing<br>
that would work too (though I would find it wasteful and suboptimal).<br>
However, the abstraction grubby provides is actually _useful_ and<br>
beneficial overall, so fixing any deficiencies because of the grub -><br>
grub2 transition would seem like a better idea to me.<br></p></blockquote><div> </div><div>Hmm, okay.</div><div> </div><div>In that case, would it be possible (or at least, a better idea) to modify *grubby* to call grub2-mkconfig when the bootloader is grub2? Then we'd still have all the other abstractions for other bootloaders but new kernel entries would be added in a way that respects the configurations in /etc/default/grub and /etc/grub.d.</div>
<div> </div><div>Ben</div></div>