Description of Problem:
When performing an upgrade frmo 7.2 -> Hampton B2, grub overwrites the exising
grub.conf with only the data provided in th anaconda session
Very. Reproduced on a 7.2 -> Hampton Upgrade, and a fresh install where 2K,
FreeBSD, and a Linux partition shared a grub.conf. In the latter case, the
FreeBSD was lost, but the 2K (since it was a bootable primary) was retained in
Steps to Reproduce:
Add your own kernel to gurb.conf and do an upgrade. The "user" kernel will be
gone on the post-upgrade reboot.
The expectation is that my custom settings from the prior install will be
retained, or at least modified, not just blown away in one big swoop. If the rpm
upgrade fo a kernel can do it, why can't anaconda?
Because anaconda is rewriting the GRUB config because there's no way to *know*
where to install GRUB. A lot of these questions were going to get addressed by
new bootloader code that isn't landing with the new Hampton schedule. I'll see
what I can this week, but this may well end up just being deferred :(
Okay, implemented new screens to handle this today. I would appreciate testing
of this as much as possible during the next beta.