Bug 64402 - Upgrade doesn't preserve grub config.
Summary: Upgrade doesn't preserve grub config.
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda   
(Show other bugs)
Version: 7.3
Hardware: i386 Linux
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Brock Organ
Depends On:
TreeView+ depends on / blocked
Reported: 2002-05-03 16:46 UTC by hjl
Modified: 2007-04-18 16:42 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-05-06 19:05:15 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
/boot/grub/grub.conf.rpmsave (844 bytes, text/plain)
2002-05-03 17:47 UTC, hjl
no flags Details
/boot/grub/grub.conf (562 bytes, text/plain)
2002-05-03 17:48 UTC, hjl
no flags Details

Description hjl 2002-05-03 16:46:24 UTC
When I upgrade to 7.3, all the extra boot entries in grub..conf are gone.
It used to work fine with lilo.

Comment 1 Jay Turner 2002-05-03 17:12:02 UTC
Please attach your resulting /etc/grub.conf file.

Comment 2 hjl 2002-05-03 17:47:39 UTC
Created attachment 56289 [details]

Comment 3 hjl 2002-05-03 17:48:25 UTC
Created attachment 56290 [details]

Comment 4 Jay Turner 2002-05-03 21:40:02 UTC
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.

Comment 5 hjl 2002-05-03 22:39:13 UTC
What about custom kernels? Anaconda works fine with lilo in 7.1.
It preserves lables for custum kernels.

Comment 6 Jeremy Katz 2002-05-06 19:02:33 UTC
What option did you select on the upgrade boot loader screen?

Comment 7 hjl 2002-05-06 19:05:10 UTC
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
bootloader --location mbr

Comment 8 Jeremy Katz 2002-05-06 19:06:49 UTC
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

Comment 9 hjl 2002-05-06 19:10:53 UTC
The old one in 7.1 is clever enough to know that
I already specified "upgrade" .

Comment 10 Jeremy Katz 2002-05-06 19:17:22 UTC
7.1 only had one boot loader to ever worry about.

Note You need to log in before you can comment on or make changes to this bug.