From owner-freebsd-current Wed Jan 12 4:25: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from pauling.research.devcon.net (p3E9EBF37.dip0.t-ipconnect.de [62.158.191.55]) by hub.freebsd.org (Postfix) with ESMTP id 401EF153F7 for ; Wed, 12 Jan 2000 04:25:01 -0800 (PST) (envelope-from cc@devcon.net) Received: from localhost (cc@localhost) by pauling.research.devcon.net (8.9.3/8.9.2) with ESMTP id OAA20277; Wed, 12 Jan 2000 14:27:50 +0100 (CET) (envelope-from cc@devcon.net) Date: Wed, 12 Jan 2000 14:27:49 +0100 (CET) From: Christian Carstensen X-Sender: cc@pauling.research.devcon.net To: Donn Miller Cc: current@freebsd.org Subject: Re: why is my current so .... stable? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 12 Jan 2000, Donn Miller wrote: > My guess is that once -current gets closer to the release date, it becomes > more and more stable. I guess the period of greatest instability occurs > somewhere about 1/4 to 1/2 through the -current life cycle. We could do a > chart plotting stability vs. time for the life cycle of a given > -current. That could help people decide whether or not they want to run > -current. This would be great, but I wonder from what source we could take reliable data about -current's stability. But what I've meant was: I've had these ugly system freezes not perfactly reproducable, but very often. From what I've read on current list, the problems still exist, but not on my system. At least this system runs stable for 1 day now. I'm wondering, why. -- Christian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message