-----BEGIN PGP SIGNED MESSAGE----- Am Montag, 31. März 2003 23:11 schrieb Hatto von Hatzfeld:
I have had a frozen system twice after installing the new kernel in a SuSE 7.3 system (upgrading thus from 2.4.10 to 2.4.18). This never had happened before. But I am glad that this until now did not happen to my webserver (same SuSE 7.3, same patch).
Now I reinstalled the original kernel - at my desktop I can handle the risk and do a workaround since I'm the only person working on the machine. A system which freezes several times is unfortunately unacceptable to me when I always have to check the file system manually what takes several minutes, because the hard disk is corrupted arfter a reboot. And I thinking to leave a productional server unpatched and do a "echo /dummy > /proc/sys/kernel/modprobe" to avoid being hacked. To the Server I dont have console access and will have to call the guys at the NOC. Or are there any better suggestions?
What is the best thing to do now - to go back to the unpatched kernel (and to live with the security problem), to remain with the risk of a freeze or to try the k_deflt-2.4.19-patch?
=> see above. I'm not lucky with the situation. I've experienced SuSE to be a good, reliable distribution but what happens now is what I wanted to avoid with changing from windows to linux some years ago. Hope that SuSE will provide a patch which is better tested than this one the next time. Regards: Tobias - -- - ------------------------------------- Tobias Cremer Hohenzollernstr. 20 80801 München to.c@gmx.net http://www.tobiwan-kenobi.de -----BEGIN PGP SIGNATURE----- Version: 2.6.3in Charset: noconv iQCVAwUBPojOK7d9JiPf/I1hAQGIwwQAg5wLy/9zhXoZZbG3PhvNNYlar4zcTkLs 4ge9p0mHPuJ8WVXU4hQeKc4DSqQ9Yv4Iy5cJw4/waYslcFT9t4a+E49CcesG6ZLt xVe22+oxPKhmD8UCMi/KtDG/Y8JPDb5TkivKLw4+5evjdHPbKeJVQITPBjO1Abwj dbwpn+dulh8= =aFb9 -----END PGP SIGNATURE-----