From owner-freebsd-current Mon Aug 27 16:18:19 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id A292F37B406; Mon, 27 Aug 2001 16:18:16 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.6/8.11.2) id f7RNIGu26916; Mon, 27 Aug 2001 16:18:16 -0700 (PDT) (envelope-from dillon) Date: Mon, 27 Aug 2001 16:18:16 -0700 (PDT) From: Matt Dillon Message-Id: <200108272318.f7RNIGu26916@earth.backplane.com> To: Robert Watson Cc: John Baldwin , Julian Elischer , current@FreeBSD.ORG Subject: Re: RE: Headsup! KSE Nay-sayers speak up! References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :I'm not fundamentally opposed to KSE: I would like to see it in the system :as much as you, and am quite aware of the potential benefits. I just want :to make sure we don't go three years without a stable release to get :there. If the answer to the questions is either fine, or addressible, :... : :Robert N M Watson FreeBSD Core Team, TrustedBSD Project :robert@fledge.watson.org NAI Labs, Safeport Network Services I think if KSE goes in (in the next couple of weeks, on Julian's timeline with reasonable, but not excessive additional testing), I will personally be a much happier camper in regards to working on -current. To me it will be a real turning point for the project -- the last 'big' piece of technology we promised ourselves we would get in. And I have been and will continue to be available to help track down and work out bugs in that work, and in other work. The single biggest problem -current faces right now is in unwinding Giant. It is an even larger problem then people think, I think. Because Giant still surrounds nearly all the running code there are almost certainly dozens of bugs that will come out of the woodwork as Giant gets moved inward. Hell, maybe I shouldn't be working on the VM system at all right now... maybe I should be working on mutexing data structures in order to move Giant inward. e.g. filesystem and I/O paths. The VM code is the hardest piece, it should probably be saved for last. We are not going to truely be able to stabilize -current until Giant is mostly gone. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message