I enabled AUTOREMOVE=yes in /etc/sysconfig/installkernel on two systems
and on both I got
[root@cooker root]# rpm -ivh
/cooker/i586/Mandrake/RPMS/kernel-2.4.10-2mdk.i586.
rpm
Preparing... ###########################################
[100%]
1:kernel ###########################################
[100%]
look like there was a problem, the default vmlinuz version is not the
same
of the initrd
On one it was 2.4.8-26mdk -> 2.4.10-1mdk, on another one 2.4.10-1mdk ->
2.4.10-2mdk. The second one was updated yesterday from 2.4.8-26mdk as
well without any hiccup (before this change).
The problem is that after this
- /boot/vmlinuz is not linked to correct version
[root@cooker scsi]# ll /boot/{initrd,vmlinuz}*
-rw-r--r-- 1 root root 110062 Oct 4 10:36
/boot/initrd-2.4.10-1mdk.img
-rw-r--r-- 1 root root 112065 Oct 5 09:48
/boot/initrd-2.4.10-2mdk.img
lrwxrwxrwx 1 root root 28 Oct 5 09:48 /boot/initrd.img
-> /boot/initrd-2.4.10-2mdk.img
lrwxrwxrwx 1 root root 19 Oct 4 10:35 /boot/vmlinuz ->
vmlinuz-2.4.10-1mdk
-rw-r--r-- 1 root root 1218354 Oct 3 19:25
/boot/vmlinuz-2.4.10-1mdk
-rw-r--r-- 1 root root 1218372 Oct 4 19:09
/boot/vmlinuz-2.4.10-2mdk
- initrd.img is linked to absolute pathname (/boot/initrd-$VERSION)
instead of relative. But it may be general problem.
- no lilo entry for new version is created.
-andrej
