I just tried to update my 2.2.15-4mdk kernel to 2.2.16-9mdksecure by RPM
and I think something is jacked up. I used Mandrake updater to install
2.2.16-9mdksecure kernel and 2.2.16-9-docs like Mandrakeuser.org says on
it's upgrade page, although I didn't allow it to install the
kernel-headers rpm because a dependency error came up stating that it
was going to overwrite the headers package for my 2.2.15-4 kernel and I
didn't want to risk screwing up my working kernel.
Anyway, I went to /etc/lilo.conf and saw that the new 2.2.16-9mdk-secure
kernel is properly set as the new default kernel. I did a 'lilo -v' to
update lilo and it gave an error:
Reading boot sector from /dev/sda
Merging with /boot/boot.b
Mapping message file /boot/message
Boot image: /boot/vmlinuz-secure
Fatal: open /boot/vmlinuz-secure: No such file or directory
When I look in /boot (xterm w/ colors on) the link for System.map@ and
vmlinuz-secure@ are highlighted in red, which I assume means something
is wrong because the link for vmlinuz@ (2.2.15-4 kernel)is in blue. The
related files for these links are there:
System.map-2.2.15-4mdk
System.map-2.2.16-9mdksecure
vmlinuz-2.2.15-4mdk
vmlinuz-2.2.16-9mdksecure
I (again assume) that System.map-2.2.16-9mdksecure needs to be linked to
System.map@ and vmlinuz-2.2.16-9mdksecure needs a working link with
vmlinuz-secure@.
Should I just do a 'ln -s /boot/System.map-2.2.16-9mdksecure
/boot/System.map' and 'ln -s /boot/vmlinuz-2.2.16-9mdksecure
/boot/vmlinuz-secure' to create working links? Then run 'lilo -v' again
to see if everything is hunky-dory?
Or is this problem something far more sinister? Like needing to force
update kernel-headers.
Any suggestions appreciated,
Victor
