From owner-freebsd-current  Sun Jul 28 13:14:01 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id NAA07964
          for current-outgoing; Sun, 28 Jul 1996 13:14:01 -0700 (PDT)
Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA07957
          for <current@freebsd.org>; Sun, 28 Jul 1996 13:13:56 -0700 (PDT)
Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id PAA00488; Sun, 28 Jul 1996 15:13:42 -0500 (EST)
From: "John S. Dyson" <toor@dyson.iquest.net>
Message-Id: <199607282013.PAA00488@dyson.iquest.net>
Subject: Re: libtcl
To: karl@mcs.com (Karl Denninger MCSNet)
Date: Sun, 28 Jul 1996 15:13:42 -0500 (EST)
Cc: marxx@doomsday.org, current@freebsd.org
In-Reply-To: <m0ukc3a-000IDOC@venus.mcs.com> from "Karl Denninger, MCSNet" at Jul 28, 96 03:03:18 pm
X-Mailer: ELM [version 2.4 PL24 ME8]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> 
> Where do I find the list of known-to-be-broken things in -CURRENT at this
> point (is there such a thing?)  -STABLE has serious NFS and VM problems right 
> now - those showed up about three months ago, as a kernel from before that
> time does NOT exhibit the same issues.
> 
> Most of this appears to be fixed in -CURRENT, but is there anything that I
> need to be aware of in a production environment?  (-STABLE, as of now, isn't
> in that environment for us).
> 
As of approx 25-Jul, I made a VM commit with some problems.  In a production
environment use a kernel just before that date.  It will
be fixed before the snap, but TODAY, use a kernel checked out like:

cvs co -D24-Jul sys

John