From owner-freebsd-current Sun Jan 25 10:00:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28220 for current-outgoing; Sun, 25 Jan 1998 10:00:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA28213 for ; Sun, 25 Jan 1998 10:00:03 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id MAA25937; Sun, 25 Jan 1998 12:59:35 -0500 (EST) (envelope-from toor) Message-Id: <199801251759.MAA25937@dyson.iquest.net> Subject: Re: Last stable -current? In-Reply-To: <19980125145536.61375@keltia.freenix.fr> from Ollivier Robert at "Jan 25, 98 02:55:36 pm" To: roberto@keltia.freenix.fr (Ollivier Robert) Date: Sun, 25 Jan 1998 12:59:35 -0500 (EST) Cc: current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk Ollivier Robert said: > According to Amancio Hasty: > > I haven't seen any posting from Dyson so I assume that -current still has > > vm problems. > > The bad period is between Dec, 28th and Jan, 20th approx. nullfs/umapfs are > unusable right now although some unionfs fixes are probably relevant to > them as well. > Things should be better now. I am being very cautious about making any claims, however, try again. (The problems weren't strictly with VM but with VFS.) PHK had started some things in motion, not breaking the system, but showed me where things needed work. I initially broke the system, but worked on some stuff that followed up on PHK's work. Things should be better now, including the system should be more memory efficient. Keep me posted. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig.