On Mon, 24 Dec 2001, Federico Sevilla III wrote: > On Sun, 23 Dec 2001 at 19:03, fooler wrote: > > im not putting down linux also but i still watch and observe its > > performance. but nowadays, it is too scary to implement new kernel > > version of linux in a production environment due to some reports that it > > can corrupt a filesystem, its virtual memory is in mess, and others. > > While I do not contest your claims about FreeBSD's performance, I have to > disagree on your claim about Linux kernel stability. As of Linux kernel > 2.4.16, AFAIK, the VM in particular is ready to rock and roll. And 2.4.17 > is out, with a rather hefty ChangeLog, but nothing drastic, it seems. So > I'd say that all's well with the latest stable kernel. But then again I > could be wrong so let me know what data you have on this. :) > > But "it works for me" (tm). ;>
How can you judge 2.4.16-17 as now "stable" when it just came out a few days ago? And say in the end "But then again I could be wrong so let me know what data you have on this.", you are not sure then? Time will really tell if a specific kernel was indeed stable. IMHO, 20.36 (2.0.x series) and 2.2.17 (2.2.x series) were the best rock solid kernels that I have used. And they weren't even the newest kernel. Maybe new releases to you means "better" and "stable"? In a production environment, you simply don't plug a new kernel because it's new... In a devbox, that's fine though. What I usually do is look at the CHANGELOG of the newer kernel and if not much has changed and no compelling reason to upgrade, I'll stick with the old but proven kernel. Indeed, the FS corruption and VM problem with some 2.4.x stable kernels were worrying. Have not seen that big magnitude of a problem with 2.0.x and 2.2.x. regards, --- Andre M. Varon, SCSA http://andre.lasaltech.com Fear can hold you prisoner, Hope can set you free. _ Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph To leave: send "unsubscribe" in the body to [EMAIL PROTECTED] To subscribe to the Linux Newbies' List: send "subscribe" in the body to [EMAIL PROTECTED]
