Robert... just install a Suse 8.0 machine and do the kernel upgrade... you'll see the messages and the kernel panic A.S.A.P. after the reboot... then boot with a cd and "boot the installed system" when Yast ask about "Install a new..." "Upgrade an existing..." and "Boot installed" ...you'll see exactly what I'm talking about... Radu ----- Original Message ----- From: "Robert Davies" <rob_davies@ntlworld.com> To: "Radu Voicu" <suse@ploiesti.rdsnet.ro> Cc: <suse-security@suse.com>; <suse-linux-e@suse.com> Sent: Thursday, March 27, 2003 10:47 AM Subject: Re: [suse-security] SuSE Security Announcement: kernel (SuSE-SA:2003:021)
On Thursday 27 March 2003 08:07, Radu Voicu wrote:
No offence, but I think you'll have to pay more attention when you compile the kernel upgrade... for instance, in the upgrade 2.4.18 for SuSE 8.1, you use modules from 2.4.19... and no machine will start... NEVER EVER... I
But module versioning allows loading of compiled modules into different kernel releases, so long as the compile options are compatible (memory model, SMP, CPU etc).
Rob