From owner-freebsd-current Sat Feb 23 20:25:27 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id 505E937B404 for ; Sat, 23 Feb 2002 20:25:25 -0800 (PST) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.12.1/8.12.1) with ESMTP id g1O4PFPA110844; Sat, 23 Feb 2002 23:25:16 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: Date: Sat, 23 Feb 2002 23:25:14 -0500 To: Dag-Erling Smorgrav , current@FreeBSD.org From: Garance A Drosihn Subject: Re: -CURRENT in pretty good shape, after all Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: MIMEDefang 2.3 (www dot roaringpenguin dot com slash mimedefang) 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 At 6:24 PM +0100 2/23/02, Dag-Erling Smorgrav wrote: >Thumbs up and big cheers to all of you (well, us) guys working on >-CURRENT. It's pretty stable and has been for a while now - and >even on my poor old 350 MHz K6-2, it performs well enough to make >a kickass desktop & development platform. Let's hope it'll only >get better from here on out :) It is working fairly well for me too, on a dual-pentium machine. I can't get vmware2 working, but most of everything else that I do is working, and I'm not running into any mysterious crashes. -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message