I run RHN up2date on a box and had in the past set it to auto-update
even the kernel, and confirmed that it did (even tho there are,
apparantly, many who'd consider that a bit brave...
Now, today I noticed that my /var/log/up2date says that it couldn't
update lilo properly:
[Mon Feb 10 12:39:21 2003] up2date Adding 2.4.18-24.7.x to bootloader
config
[Mon Feb 10 12:39:21 2003] up2date Running lilo with the new
configuration
[Mon Feb 10 12:39:21 2003] up2date Opening rpmdb in /var/lib/rpm/ with
option 0
[Mon Feb 10 12:39:21 2003] up2date Running "/sbin/mkinitrd --ifneeded
/boot/init
rd-2.4.18-24.7.x.img 2.4.18-24.7.x"
[Mon Feb 10 12:39:25 2003] up2date No initrd was created by mkinitrd
[Mon Feb 10 12:39:25 2003] up2date renaming the lilo.conf entry for
linux to lin
ux.bak1234
[Mon Feb 10 12:39:26 2003] up2date making a backup copy of
/etc/lilo.conf as /et
c/lilo.conf.up2date-1044833965.87
[Mon Feb 10 12:39:26 2003] up2date writing out the new /etc/lilo.conf
[Mon Feb 10 12:39:28 2003] up2date Running " /sbin/lilo -t -r /" (lilo
test mod
e)
[Mon Feb 10 12:39:28 2003] up2date restoring the backup file
/etc/lilo.conf.up2d
ate-1044833965.87 to /etc/lilo.conf
[Mon Feb 10 12:39:28 2003] up2date Error installing lilo.conf The
message was:
test install of lilo failed
I've now manually hacked the etc/lilo.conf to point to the 18-24 version
as "label=linux" but /sbin/lilo -v -v failed, so I hacked it back to:
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
message=/boot/message
linear
default=linux
image=/boot/vmlinuz-2.4.18-18.7.x
label=linux
root=/dev/hda8
read-only
image=/boot/vmlinuz-2.4.18-24.7.x
label=linux.2new
root=/dev/hda8
read-only
But now running /sbin/lilo -v -v gives:
LILO version 21.4-4, Copyright (C) 1992-1998 Werner Almesberger
'lba32' extensions Copyright (C) 1999,2000 John Coffman
Reading boot sector from /dev/hda
Merging with /boot/boot.b
Secondary loader: 11 sectors.
Mapping message file /boot/message
Message: 46 sectors.
Boot image: /boot/vmlinuz-2.4.18-18.7.x
Fatal: open /boot/vmlinuz-2.4.18-18.7.x: No such file or directory
Removed temporary file /boot/map~
I'm puzzled and a wee bit worried, so I'd appreciate any hints as to
what went wrong - and how to sort this out...
- steve
=========================================================
http://www.commarc.co.nz
(This e-mail has been scanned by MailMarshal)
