Bug 54792
Summary: | up2date doesn't update lilo.conf if existing linux.bak | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | a4a91120 <a4a91120> |
Component: | up2date | Assignee: | Adrian Likins <alikins> |
Status: | CLOSED ERRATA | QA Contact: | Jay Turner <jturner> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | CC: | dregnery, gafton, mihai.ibanescu, 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-11-05 22:36:17 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
a4a91120
2001-10-19 01:17:30 UTC
Could you append a copy of your lilo.conf file? There can be a couple of reasons up2date will raise an error about not being able to update lilo.conf: 1. the test mode run of lilo fails, typically caused by the version of lilo.conf installed being incorrect 2. Upsupported config paramaters are used. (the lilo support code in up2date-2.5.4 doesnt support bios drive remapping for example) Okay, think I see what I going on here. the label names chosen for the backup lilo stanza's are failing. Should be a fix in the next version of the client. *** Bug 55731 has been marked as a duplicate of this bug. *** |