From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S267828AbUGWQiN (ORCPT ); Fri, 23 Jul 2004 12:38:13 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S267835AbUGWQiN (ORCPT ); Fri, 23 Jul 2004 12:38:13 -0400 Received: from wsip-68-99-153-203.ri.ri.cox.net ([68.99.153.203]:57022 "EHLO blue-labs.org") by vger.kernel.org with ESMTP id S267828AbUGWQiK (ORCPT ); Fri, 23 Jul 2004 12:38:10 -0400 Message-ID: <41013F49.7030902@blue-labs.org> Date: Fri, 23 Jul 2004 12:39:37 -0400 From: David Ford User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8a3) Gecko/20040721 X-Accept-Language: en-us, en MIME-Version: 1.0 To: szonyi calin CC: "H. Peter Anvin" , linux-kernel@vger.kernel.org Subject: Re: A users thoughts on the new dev. model References: <20040723152421.52282.qmail@web52904.mail.yahoo.com> In-Reply-To: <20040723152421.52282.qmail@web52904.mail.yahoo.com> Content-Type: multipart/mixed; boundary="------------020203020502050700020208" Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org This is a multi-part message in MIME format. --------------020203020502050700020208 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit This is malarkey, 99.9% pure FUD. I personally use just about every kernel revision there is that is "newest", i.e. I use 2.4.x until 2.5 appears then I switch to 2.5.x. I may skip a few versions here and there due to frequent releases or a known brown bag release. However by far and large even the development or "unstable" line of releases as some people have a bad habit of calling them, are far more reliable than Windows. I use odd.x releases even on my servers. Every once in a while there's a significant bug in code that I'll have an issue with that can't be worked around. So I avoid that version. In short, your statement is pure bullsh*t, because there is very little code put out that is actually a messy or unstable release. Most bugs are quickly fixed, worked around, or avoided for that person because that feature isn't really such a necessity. Linux (*nix) gives you a LOT of ways to get a particular task done but people have this penchant for finding a way that is broken and hyping/harping it up to make a big issue out of it instead of just reporting the bug and getting the job done in a different fashion. "Oh my gawd it's a bug, let me piss on everyone's doorstep and make caustic remarks on LKML about horribly broken code. Never mind you that I can probably get it done another way." Give the developers a little credit, we all make mistakes; they happen to fix theirs pretty fast and they're downright honest about fessing up to them. David >>>From the LWM story i understood that linux will be like windows: >lots of "features" but no stability, except if you use a > distribution kernel. And that seriously made me think about > using another free *nix for a stable system. > --------------020203020502050700020208 Content-Type: text/x-vcard; charset=utf-8; name="david+challenge-response.vcf" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="david+challenge-response.vcf" begin:vcard fn:David Ford n:Ford;David email;internet:david@blue-labs.org title:Industrial Geek tel;home:Ask please tel;cell:(203) 650-3611 x-mozilla-html:TRUE version:2.1 end:vcard --------------020203020502050700020208--