On Fri, Jul 20, 2012 at 6:55 PM, Adam Williamson <awilliam(a)redhat.com> wrote:
Um. I think you might be working from a completely false premise. If
did a fresh install of Fedora 16 you should have grub2. Not grub.
Hmmm. This laptop has had F14, but IIRC it got a wipe-and-reinstall
treatment. You may be right on that point...
way grubby works, if you have a grub2-based system it'll 'complain'
about the lack of a grub1 config file sometimes, but this isn't a
problem in itself and can be ignored; if something's going wrong, that
isn't the reason why. The file that needs to be updated
is /boot/grub2/grub.cfg (/etc/grub2.cfg is a symlink to it).
/boot/grub2 exists, but is empty.
So preupgrade / grubby don't work with grub, and should bail out if
grub is the bootloader? Should that be my bug report?
Note that once you reach the point of bootloader configuration,
preupgrade did its job long ago. You're now just using plain anaconda.
Preupgrade is driving, at least in the "prep" stage, so I'll file
those bugs against preupgrade. Up to preupgrade maintainers to know
more about who to blame ;-)
However, due to a bit of an oversight, a preupgrade-based upgrade
TBH, I think that BZ#813973 is a high value bug that affects all
"small boot partition" users, it should be fixed, or at least then
known workaround noted in the wikipage.
I'm really a bit confused by exactly what bootloader you actually
Plain grub. I apologize, this may be a F14->F16 box. Cannot check
right now, it is finally upgrading...
If old grub is no longer the cool thing, I'll try to replace it with
grub2 once my upgrade is complete.
martin(a)laptop.org -- Software Architect - OLPC
- ask interesting questions
- don't get distracted with shiny stuff - working code first