From owner-freebsd-current Tue Mar 26 16:38:44 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 1A54B37B41A for ; Tue, 26 Mar 2002 16:38:41 -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 g2R0cd4k131136; Tue, 26 Mar 2002 19:38:39 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20020326063634.A23222@laptop.6bone.nl> References: <20020326063634.A23222@laptop.6bone.nl> Date: Tue, 26 Mar 2002 19:38:38 -0500 To: Mark Santcroos From: Garance A Drosihn Subject: Re: VMWare2 was broken in recent -current (seems OK now) Cc: current@FreeBSD.ORG 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:36 AM +0100 3/26/02, Mark Santcroos wrote: >Currently rebuilding with latest sources, will look into >it after that. Whatever the problem had been, it looks like it was fixed between March 23 and today (the 26th). I did a buildworld as of 4pm or so, and vmware2 is up and running OK on the most recent snapshot of current. Thanks for offering to look into it. Hopefully there'll be nothing that you have to do... :-) -- 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