Date: Sun, 28 Jul 1996 15:13:42 -0500 (EST) From: "John S. Dyson" <toor@dyson.iquest.net> To: karl@mcs.com (Karl Denninger MCSNet) Cc: marxx@doomsday.org, current@freebsd.org Subject: Re: libtcl Message-ID: <199607282013.PAA00488@dyson.iquest.net> In-Reply-To: <m0ukc3a-000IDOC@venus.mcs.com> from "Karl Denninger, MCSNet" at Jul 28, 96 03:03:18 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199607282013.PAA00488>