I ran up2date on my up-to-date system (RH 7.1). New kernel kernel-2.4.3-12
has been succesfully downloaded (I used -k command line option), but the
up2date bombs out when trying to update my /etc/lilo.conf. The reason is
that I have four lines in lilo.conf to boot from SCSI disk (with system
and with root FS). I have IDE disk too, but this disk is removable. Thus I
have this four lines in my lilo.conf:
The lilo.conf could be easily upgraded, no modification to lilo.conf is
needed (these four lines are "global" options). Of course new image=
section should be added.
My actual lilo.conf:
Up2date bomb out with this traceback:
Traceback (innermost last):
File "/usr/sbin/up2date", line 831, in ?
File "/usr/sbin/up2date", line 806, in main
sys.exit(batchRun(onlyList, pkgNames, fullUpdate))
File "/usr/sbin/up2date", line 596, in batchRun
File "/usr/share/rhn/up2date/up2date.py", line 2222, in installBootLoader
ret = lilocfg.installNewImages(kernelList,test=0)
File "/usr/share/rhn/up2date/lilocfg.py", line 266, in installNewImages
raise LiloConfParseError("\n" + "%s" % config.unsupported)
lilocfg.LiloConfParseError: lilo options that are not supported by up2date
are used in the default
lilo.conf. This file will not be modified. The options include:
['disk=/dev/sda', 'bios=0x80', 'disk=/dev/hda', 'bios=0x81']
Bombing out is bad, but leaving original global parameters should be
possible in this case.
These options should be support in the next versions of the clients
(and I believe the errataed version as well).
The 7.1 stock version as the code for handling those cases
commented out, as it wasnt well tested at that time. The updated
version seems to handle this correctly, leaving them as global
the lilo.conf has been added to the test suite for up2date...