Hi All: I just downloaded and installed the latest kernel patch for 9.2 which carried a security warning and it crippled my system. It took me best part of a day to repair it and in the end I had to create a new symlink for initrd. Very poor indeed. I hope this does not reflect what is in stall under Novell? Paul -- De omnibus dubitandum
Hi All:
I just downloaded and installed the latest kernel patch for 9.2 which carried a security warning and it crippled my system. It took me best part of a day to repair it and in the end I had to create a new symlink for initrd. Very poor indeed. I hope this does not reflect what is in stall under Novell?
Thanks Paul, has anyone else seen this? Adrian
Paul -- De omnibus dubitandum
On Wednesday 29 December 2004 11:52, Adrian Wells wrote:
Thanks Paul, has anyone else seen this?
SuSE were pretty quick off the mark to warn people about this. This message appeared on suse-security-announce less than twenty minutes after the original posting about the availability of the updated kernel: ********************** The following only affects SUSE Linux 9.2. We received additional reports of breakage if you have additionaly the UserMode Linux Kernel package "kernel-um" installed. In this case the system initrd will be created from "kernel-um" and not from "kernel-default" or "kernel-smp" As workaround: - If you do not need the kernel-um package, deinstall it using: rpm -e kernel-um and recreate the system initird by running: mkinitrd before rebooting. - if you need the kernel-um package, restore the symlink using: ln -sf /boot/initrd-2.6.8-24.10-default /boot/initrd (replace -default by the kerneltyp you use, detectable by: rpm -qa|grep kernel- which will be either "default", "smp" or "bigsmp".) after installing the updated packages and before booting the new kernel. Ciao, Marcus ********************** -- Phil Driscoll
On Wednesday 29 December 2004 12:21, Phil Driscoll wrote:
On Wednesday 29 December 2004 11:52, Adrian Wells wrote:
Thanks Paul, has anyone else seen this?
SuSE were pretty quick off the mark to warn people about this. This message appeared on suse-security-announce less than twenty minutes after the original posting about the availability of the updated kernel:
I suppose I should be on that :) I also updated another machine that I have at home and had no problems so it is somewhat dependent on installation. The good thing is that I managed to sort it out which is a tribute to the support I have had on this forum over the years so I second Adrian's comments and wish everyone on the list a happy new year's open source.
********************** The following only affects SUSE Linux 9.2.
We received additional reports of breakage if you have additionaly the UserMode Linux Kernel package "kernel-um" installed.
In this case the system initrd will be created from "kernel-um" and not from "kernel-default" or "kernel-smp"
As workaround:
- If you do not need the kernel-um package, deinstall it using: rpm -e kernel-um
and recreate the system initird by running: mkinitrd
before rebooting.
- if you need the kernel-um package, restore the symlink using:
ln -sf /boot/initrd-2.6.8-24.10-default /boot/initrd
(replace -default by the kerneltyp you use, detectable by: rpm -qa|grep kernel-
which will be either "default", "smp" or "bigsmp".)
after installing the updated packages and before booting the new kernel.
Ciao, Marcus **********************
-- Phil Driscoll
-- De omnibus dubitandum
participants (3)
-
Adrian Wells -
Paul Taylor -
Phil Driscoll