Bug 64402
| Summary: | Upgrade doesn't preserve grub config. | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | hjl | ||||||
| Component: | anaconda | Assignee: | Jeremy Katz <katzj> | ||||||
| Status: | CLOSED NOTABUG | QA Contact: | Brock Organ <borgan> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 7.3 | ||||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | i386 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2002-05-06 19:05:15 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: | |||||||||
| Attachments: |
|
||||||||
|
Description
hjl
2002-05-03 16:46:24 UTC
Please attach your resulting /etc/grub.conf file. Created attachment 56289 [details]
/boot/grub/grub.conf.rpmsave
Created attachment 56290 [details]
/boot/grub/grub.conf
Actually, an upgrade performs a kernel installation, so that does indeed wipe out the old kernels, and the result of that is that when grub gets rewritten, then the old entries get dropped, as they are no longer installed on the system. What about custom kernels? Anaconda works fine with lilo in 7.1. It preserves lables for custum kernels. What option did you select on the upgrade boot loader screen? Here is my kickstart file. ---- lang en_US #url --url http://china/RedHat-7.0 harddrive --partition sda5 --dir /redhat/cdrom/i386 network --bootproto dhcp keyboard us upgrade bootloader --location mbr reboot Then it's doing exactly what you told it -- create a new bootloader config on the MBR. Use 'bootloader --upgrade' to get the behavior you want The old one in 7.1 is clever enough to know that I already specified "upgrade" . 7.1 only had one boot loader to ever worry about. |