From owner-freebsd-stable Wed Mar 29 2: 6:53 2000 Delivered-To: freebsd-stable@freebsd.org Received: from knight.cons.org (knight.cons.org [194.233.237.86]) by hub.freebsd.org (Postfix) with ESMTP id 62DE637B6A2 for ; Wed, 29 Mar 2000 02:06:46 -0800 (PST) (envelope-from cracauer@knight.cons.org) Received: (from cracauer@localhost) by knight.cons.org (8.9.3/8.9.3) id MAA10554; Wed, 29 Mar 2000 12:06:38 +0200 (CEST) Date: Wed, 29 Mar 2000 12:06:38 +0200 From: Martin Cracauer To: Didier Derny Cc: "Forrest W. Christian" , Martin Cracauer , freebsd-stable@FreeBSD.ORG Subject: Re: Let 3.x die ASAP? Message-ID: <20000329120638.A10455@cons.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from didier@omnix.net on Wed, Mar 29, 2000 at 09:57:25AM +0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In , Didier Derny wrote: > > now with 3.x I have uptimes between 2/6 weeks! > with 2.x I had uptimbes between 2/6 months! I don't think that uptime wars are the right thing to decide over the issue. What counts are the number of case where an upgrade to 4.x had an instant positive effect. I have several such occasions. In one case, the IDE hardware that crashed 3.4-stable reproducable worked under 3.1 when directly switching harddisks. Speaking of reproduceable, why didn't I debug the issues? In all these cases, the machines were for one reason or another not suitable for debugging (production machines, fixed frequency monitors, hard hang with no crashdump etc.). 3.x and especially the old wd driver wasn't important enough for me to go through the effort on a saturday->sunday night. It seems that other committers think on the same line and hence I want 3.x to die soon. (Where "die" means that no new users jump on it). Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message