I installed with rpm -Uvh, it still wiped out my other kernel in lilo.conf and /boot
eg
image=/boot/vmlinuz label=linux-2.4.19mdk root=/dev/hde2 initrd=/boot/initrd.img append="devfs=mount hdc=ide-scsi" vga=788 read-only
but in /boot vmlinuz -> vmlinuz-2.4.21-0.13mdk
So its still not working mdksoft, is this an known issue? Is anyone working on a fix for it?
Cheers
JG
It has been explained many times over the past three years that I am aware is that you don't -U(pdate) a kernel. At one point, MandrakeUpdate mistakenly enabled such an update, which removes your old kernel and which created a lot of problems when the new kernel wouldn't work for some people. That has since been changed so that urpmi will install, not upgrade a kernel:
$ cat /etc/urpmi/inst.list
# Here you can specify packages that need to be installed instead
# of being upgraded (typically kernel packages).
kernel
kernel-smp
kernel-secure
kernel-enterprise
kernel-linus2.2
kernel-linus2.4
kernel22
kernel22-secure
kernel22-smp
hackkernel
I have had no problem doing rpm -i the kernel, which installs the new kernel in parallel, mkinitrd, ifneeded, changes the default links in /boot to point to the new kernel, and creates a new entry in the bootloader (grub, for me) for the previous default kernel.
As it turns out, this particular kernel has the same version for a security-vulnerable edition and the patched edition, which came out right at the time of release, thus the use of the same version. If you were running the first, vulnerable kernel and wanted to install the patched kernel of the same version (which, afaict, is not the case here), you would have to implement some non-standard strategy, as discussed in this thread:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg103870.html
In short, I don't think you have an issue that, as defined, presents a fixable bug for Mandrake.
rolf
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
