Bug 45584 – up2date couldn't upgrade lilo.conf

Bug 45584 - up2date couldn't upgrade lilo.conf

Summary:	up2date couldn't upgrade lilo.conf

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	up2date (Show other bugs)
Sub Component:
Version:	7.1
Hardware:	i386 Linux

Priority	medium Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Adrian Likins
QA Contact:	Jay Turner
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2001-06-22 21:19 EDT by Ed McKenzie
Modified:	2015-01-07 18:46 EST (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2001-07-05 16:10:35 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
renegade lilo.conf (220 bytes, text/plain) 2001-06-22 21:22 EDT, Ed McKenzie	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Ed McKenzie 2001-06-22 21:19:52 EDT

up2date failed to upgrade my kernel, instead muttering something about a
test lilo.conf failing.  It did build an initrd successfully.  My lilo.conf
is attached.

Comment 1 Ed McKenzie 2001-06-22 21:22:05 EDT

Created attachment 21625 [details]
renegade lilo.conf

Comment 2 Adrian Likins 2001-07-02 22:34:56 EDT

I'll add a copy of your lilo.conf to the up2date test suite.

Offhand, I dont see anything odd about it that might cause problems,
but will add it into the testing cycle to see.

Comment 3 Ed McKenzie 2001-09-01 11:07:46 EDT

lilo has been superseded by grub for next release.

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