Bug 494103
| Summary: | Anaconda does not detect older Fedoras (in grub.conf) | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Ahmed Kamal <email.ahmedkamal> |
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | rawhide | CC: | ackistler, anaconda-maint-list, blinkous, email.ahmedkamal, jgranado, jlaska, pjones, rmaximo, vanmeeuwen+fedora |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-06-02 14:02:20 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Ahmed Kamal
2009-04-04 12:04:20 UTC
*** Bug 501063 has been marked as a duplicate of this bug. *** Ahmed: so you are installing on top of F10 and choosing to use, but *not* reformat, the existing '/boot' partition. If that is the case, I don't believe you can expect any existing bootloader configuration to remain intact since anaconda will install a new bootloader. If you wish to add entries for existing boot targets, you can do that in the anaconda bootloader screen, or by hand post-install. I multi-boot all the time using a common /boot, so I'm quite familiar with how anaconda/grub handles installing the bootloader when there's already one installed and configured.
1. There's only one MBR, so there can be only one binary.
The stage files get overwritten to match what's in the MBR.
That's the way you *want* it to be.
2. The existing grub.conf and menu.lst are moved to grub.conf.rpmsave and
menu.lst.rpmsave. They're not deleted. menu.lst is a logical link, so
it doesn't make a lot of sense to mv it, but it doesn't hurt anything.
(Remember that grub.conf is really in /boot/grub, not in /etc, just
where you *want* it to be, eh?)
After you boot into the new OS, just run
cat grub.conf.rpmsave >> grub.conf
then vi it to get rid of the duplicate header lines and "rm *rpmsave"
Getting anaconda and/or grub to edit the existing grub.conf rather than mv it would be nice, but it works fine the way it is. That's also the way it's always worked since grub has been the bootloader. (lilo.conf really did go in /etc, but you could pull some link fakery like grub does now, too.)
If the old grub.conf really did get blown away, there'd be a lot of angry folks racing you to file a bug on it. As it is, I'd say this one is a WORKSFORME (alpha through preview so far).
HTH
comment #3 sounds pretty much right. Another thing you could do (What I do in my installs) is to tell anaconda not to install a bootloader. This will skip the installation of the grub package and avoid all the grub.conf.rpmsave stuff. You do have to edit the grub.conf with the parameters of your new install though. +1 for WORKSFORME |