Hello Roman, hello List, I installed this kernel-update this night and after that I have a problem with my network-card. I'm running SuSE 8.1 on a Puretec-Root-Server with a network-card that uses the 8139too module. I can boot into a rescue-system and in the /var/log/boot.msg I see the following error: ##################### <notice>/etc/init.d/rc3.d/S05network start Setting up network interfaces: lo done eth0 ifup: Could not get a valid interface name: -> skipped failed <notice>'/etc/init.d/rc3.d/S05network start' exits with status 0 ##################### I need your help very quickly.... What should I do? Thanks in advance Mario
-----Original Message----- From: Roman Drahtmueller [mailto:draht@suse.de] Sent: Monday, March 24, 2003 6:38 PM To: suse-security@suse.de Subject: [suse-security] kernel updates
Hi,
long awaited, it's there now: The kernel updates for 7.1-8.1 are on their way to the mirrors. 8.2 already has the fix when it hits the stores.
You'll find directories named kernel/2.4.18-20030324/ in each of the update directories of the 7.1, 7.2, 7.3, 8.0, 8.1 distributions. The changelogs are not fully consistent, but the packages are ok and fix the known problems.
8.1 has a 2.4.19 kernel, 8.0 and below have 2.4.18. Basically, the 2.4.19 kernel from 8.1 should run with the older distributions as well, but your mileage may vary.
We have had some problems when we tested the kernel packages, mostly because the first suggested fixes were incorrect. This is why it took us so long.
The announcement will follow later tonight. It will be copied to the update/*/kernel/2.4.1?-20030324 directories as soon as it is published. It will contain detailed information about the commands necessary to install the updates.
In short:
rpm -qf /boot/vmlinuz download the package for your system. rpm -Uhv your_package mk_initrd . /etc/sysconfig/bootloader case "$LOADER_TYPE" in *lilo*) lilo ;; *) ;; esac
Roman.
-- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help@suse.com Security-related bug reports go to security@suse.de, not here