Bug 31194

Summary: upgrade 3.0.3 to 7.1 (qa0308.0) lilo hosed
Product: [Retired] Red Hat Linux Reporter: David Lawrence <dkl>
Component: anacondaAssignee: Matt Wilson <msw>
Status: CLOSED RAWHIDE QA Contact: Brock Organ <borgan>
Severity: high Docs Contact:
Priority: high    
Version: 7.1   
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: 2001-03-09 23:29:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Attachments:
Description Flags
old lilo.conf file (lilo.conf.rpmsave)
none
new lilo.conf file none

Description David Lawrence 2001-03-09 17:45:26 UTC
Encountered a problem with lilo.conf when upgrading a 3.0.3 system to
qa0308.0.  The lilo.conf that anaconda wrote would not boot properly since
the old 3.0.3 kernel was still
trying to load. Here is the lilo.conf from the 3.0.3 system before upgrade
(taken from lilo.conf.rpmsave)

boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
image=/vmlinuz
	label=linux
	root=/dev/hda5
	read-only


Here is the lilo.conf as written by anaconda for post reboot

boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
message=/boot/message
linear
default=linux

image=/vmlinuz
	label=linux
	root=/dev/hda5
	read-only

As you can see the old kernel is still being used as the default image. It
should read

image=/boot/vmlinuz

to boot the new 2.4.2 kernel instead of the old 1.2.13 kernel.

Comment 1 David Lawrence 2001-03-09 17:47:08 UTC
Created attachment 12202 [details]
old lilo.conf file (lilo.conf.rpmsave)

Comment 2 David Lawrence 2001-03-09 17:47:32 UTC
Created attachment 12203 [details]
new lilo.conf file

Comment 3 Glen Foster 2001-03-09 23:29:16 UTC
This defect considered MUST-FIX (show-stopper) for Florence Gold

Comment 4 Matt Wilson 2001-03-16 05:00:06 UTC
Fixed in cvs.


Comment 5 Matt Wilson 2001-03-27 17:15:42 UTC
*** Bug 28280 has been marked as a duplicate of this bug. ***

Comment 6 Matt Wilson 2001-04-02 15:33:48 UTC
*** Bug 26790 has been marked as a duplicate of this bug. ***

Comment 7 Matt Wilson 2001-04-02 15:34:43 UTC
*** Bug 26910 has been marked as a duplicate of this bug. ***