Red Hat Bugzilla – Bug 54792
up2date doesn't update lilo.conf if existing linux.bak
Last modified: 2015-01-07 18:52:17 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.4.9-6 i686)
Description of problem:
Launched gui up2date and installed packages, and then revisited to get the
latest kernel packages on 18-OCT-01 which failed the end of the kernel
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Clean install RH7.1 (kernel-2.4.2-2)
2. Go to rhn via up2date before 09-OCT-01 and get new kernel/header
3. Go to rhn via up2date after 09-OCT-01 and get new kernel/header
Actual Results: up2date reports that it's unable to modify lilo.conf. I
had to workaround and hack in a new entry for kernel-2.4.9-6.
Expected Results: the up2date procedure (step 2) reproduced.
docs kind of helped but could be better.
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. ***