<br><br><div class="gmail_quote">On Mon, Oct 10, 2011 at 7:02 AM, Adam Williamson <span dir="ltr"><<a href="mailto:awilliam@redhat.com">awilliam@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5">On Sun, <a href="tel:2011-10-09" value="+4920111009">2011-10-09</a> at 12:43 +0200, Christian Menzel wrote:<br>
><br>
><br>
><br>
> Hi,<br>
><br>
><br>
> I have F16 running on a ThinkPad X220 and therefore a EFI setup with<br>
> both grub and grub2 installed.<br>
><br>
><br>
> Today yum wants to update (among others) the kernel and grub as well<br>
> as grub2.<br>
> But a conflict is reported stating: 1:grub-0.97-79.fc16.x86_64 has<br>
> installed conflicts grub2: 1:grub2-1.99-6.fc16.x86_64.<br>
><br>
><br>
> Should I try the suggested --skip-broken switch? I don't want to end<br>
> up with an unbootable system.<br>
<br>
</div></div>What's eventually going to happen is that grub2 will replace grub and<br>
you'll have to write a new config manually. You can beat the rush and do<br>
it now - install grub2, remove grub (you can use yum shell mode to do<br>
this without any complaints), run 'grub2-mkconfig<br>
-o /boot/grub2/grub.cfg' then 'grub2-install /dev/whatever' ,<br>
where /dev/whatever is the device you want to boot from.<br><font class="Apple-style-span" color="#888888"><br></font></blockquote></div><div><br></div>Thanks for your answer, I appreciate it, but are you sure this also works with UEFI?<br>
<div>Is it really /boot/grub2/grub.cfg? The installation created two partitions sda1 which was mounted as /boot/efi and is 6GB big and sda2 mount as /boot which is just 500MB big. Does your approach mean that /boot/efi is not used anymore after the switch to grub2? And why were grub and grub2 installed in parallel, I didn't do it manually.</div>
<div><br></div><div>Chris</div>