Replacing grubby with grub2-mkconfig in kernel install process

Garrett Holmstrom gholms at fedoraproject.org
Wed Jun 20 00:55:23 UTC 2012


On Tue, Jun 19, 2012 at 12:21 PM, Dennis Gilmore <dennis at ausil.us> wrote:
> El Tue, 19 Jun 2012 20:11:20 +0100
> Matthew Garrett <mjg at redhat.com> escribió:
>> On Tue, Jun 19, 2012 at 08:54:59PM +0200, Dennis Jacobfeuerborn wrote:
>> > pvgrub peeks into the guest disk so it needs to understand the
>> > partition table, the filesystem and the grub config file in the
>> > guest. Initially it didn't handle things like ext4, grub2 and EFI
>> > but AFAIK these should be fine now. I'm not sure what Amazons host
>> > systems use but hopefully they run a relatively modern version of
>> > pvgrub.
>>
>> Ok, so we need to be able to write a grub config file. We don't need
>> to ship grub, though, right?
>
> Correct, we only need to write out a grub compatable config file. it
> doesnt use a bootloader installed into the disk image at all. it doesnt
> care if there is one there or not.

Like I mentioned two days ago, the only thing that matters for EC2
images is that the kernel post-install scripts continue to be capable
of updating grub configuration files, which means that wholesale
replacement of grubby with grub2-mkconfig will probably wind up
breaking things.


More information about the devel mailing list