On Friday 24 December 2004 10:24, Mark Crean wrote:
A new kernel came out this morning so I updated to it using apt, having seen a security announcement a couple of days ago. How very silly of me.
Alas, this has comprehensively hosed my system and I can no longer boot up, messages complaining about being unable to find the correct reiserfs and sata modules.
Any way out or is it a reinstall? In which case I think it will be with Debian as I can't see them issuing an update like this.
Hello there, SuSE techs: if you want to issue kernel updates that hose systems, be my guest. But in that case SuSE will join the couple of hundred other distros out there and few or no people use because they are so buggy and unreliable. There was a time when SuSE was a cut above all this.
apt is hardly a supported method of upgrading packages. If you want to complain about suse methods, you should use suse methods. You can boot from the CD and select the rescue system. Then mount your root partition and chroot to it. Something like mkdir tmp mount /dev/hda2 tmp chroot tmp Then mount /boot in case it is on a separate partition, and reinstall the kernel rpm from /var/lib/YaST2/you/mnt/i386/update/9.2/rpm/i586/ You might also want to check what apt did, how it upgraded the kernel rpm, did it use -i or -U?