From owner-freebsd-stable Wed Mar 29 2:44:31 2000 Delivered-To: freebsd-stable@freebsd.org Received: from workhorse.iMach.com (workhorse.iMach.com [206.127.77.89]) by hub.freebsd.org (Postfix) with ESMTP id D492437B9F6 for ; Wed, 29 Mar 2000 02:44:27 -0800 (PST) (envelope-from forrestc@workhorse.iMach.com) Received: from localhost (forrestc@localhost) by workhorse.iMach.com (8.9.3/8.9.3) with ESMTP id DAA20288; Wed, 29 Mar 2000 03:44:40 -0700 (MST) Date: Wed, 29 Mar 2000 03:44:39 -0700 (MST) From: "Forrest W. Christian" To: Didier Derny Cc: Martin Cracauer , freebsd-stable@FreeBSD.ORG Subject: Re: Let 3.x die ASAP? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 29 Mar 2000, Didier Derny wrote: > now with 3.x I have uptimes between 2/6 weeks! > with 2.x I had uptimbes between 2/6 months! Yes and I have a box which is running 2.2.2-RELEASE and has uptimes of between 5 and 10 days because I have a scsi drive which has decided that it needs a power cycle every week or so. Could you please respond to the following part of my original message? > > I'm curious as to what hardware you're having all these problems > > with. Are you overclocking? Is the airflow adequate? What type of > > drives/controllers are you using? etc.... I really wonder if you've got > > some weird hardware problem which is plaguing (sp?) you. Maybe if you'd provide some information instead of just whining you'd find that not only is freebsd stable, but that it's support is miles ahead of anything else. - Forrest W. Christian (forrestc@imach.com) KD7EHZ ---------------------------------------------------------------------- iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com Solutions for your high-tech problems. (406)-442-6648 ---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message