Bug 34317

Summary:	lilo.conf updating doesn't quite work right
Product:	[Retired] Red Hat Linux	Reporter:	Jeremy Katz <katzj>
Component:	up2date	Assignee:	Preston Brown <pbrown>
Status:	CLOSED RAWHIDE	QA Contact:	Jay Turner <jturner>
Severity:	high	Docs Contact:
Priority:	medium
Version:	7.1	CC:	srevivo
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-04-02 15:21:19 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 Jeremy Katz 2001-04-02 02:17:31 UTC

With up2date-2.4.6-1, the lilo.conf updating doesn't seem to be quite
correct since it always tries to add an initrd to the lilo.conf even if one
isn't needed (and thus isn't created).  Thus the test lilo run fails and
you have to manually do the lilo.conf updating for the kernel package update.

Comment 1 Glen Foster 2001-04-02 13:51:31 UTC

This defect considered MUST-FIX for Florence Gold

Comment 2 Adrian Likins 2001-04-02 14:17:37 UTC

can you attach a copy of the original and the created lilo.conf?

up2date should always run `mkinitrd`, but with the "--if-needed" flag.

Comment 3 Adrian Likins 2001-04-02 15:14:24 UTC

looks like I was assuming that `mkinitrd` returned a different error
code when it existed because an initrd wasnt needed, and when it
was need and created it successfully. Looking though the mkinitrd
script would seem to indicate this never should of worked, but seemed
to work in practice (the error code was determined empirically, apparently
incorrectly...).

Now the code checks for existense of the initrd after calling `mkinitrd`
to see if it did infact create one, since this seems to be the only
way to tell. Should be a fix in cvs for testing now...

Comment 4 Preston Brown 2001-04-02 19:46:15 UTC

tested, fixed in 2.4.7.