From owner-freebsd-current Sun Jul 28 14:12:39 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA11043 for current-outgoing; Sun, 28 Jul 1996 14:12:39 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA11035 for ; Sun, 28 Jul 1996 14:12:35 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id PAA19564; Sun, 28 Jul 1996 15:12:29 -0600 (MDT) Date: Sun, 28 Jul 1996 15:12:29 -0600 (MDT) Message-Id: <199607282112.PAA19564@rocky.mt.sri.com> From: Nate Williams To: "Karl Denninger, MCSNet" Cc: current@freebsd.org Subject: Bugs in -current (was Re: libtcl) In-Reply-To: References: 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. '-stable' has no known VM bugs in it that I'm aware of that don't exist in -current. Many bugs were fixed in the weeks prior to the release. However, NFS bugs exist in both -stable and -current, although a set of patches were recently made to -current to fix some of them. As far as a list of 'known-to-be-broken' things, I'm not aware of any such list, except maybe one that appears on David Greenman's white-board. No such list is 'officially' kept except in the GNATS database and/or individual developers own mind. Nate