From owner-freebsd-emulation@FreeBSD.ORG  Sat Mar 13 13:32:33 2004
Return-Path: <owner-freebsd-emulation@FreeBSD.ORG>
Delivered-To: freebsd-emulation@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id E0E0316A4CE
	for <emulation@freebsd.org>; Sat, 13 Mar 2004 13:32:33 -0800 (PST)
Received: from relay.pair.com (relay.pair.com [209.68.1.20])
	by mx1.FreeBSD.org (Postfix) with SMTP id 56CD443D31
	for <emulation@freebsd.org>; Sat, 13 Mar 2004 13:32:33 -0800 (PST)
	(envelope-from silby@silby.com)
Received: (qmail 74771 invoked from network); 13 Mar 2004 21:32:31 -0000
Received: from niwun.pair.com (HELO localhost) (209.68.2.70)
  by relay.pair.com with SMTP; 13 Mar 2004 21:32:31 -0000
X-pair-Authenticated: 209.68.2.70
Date: Sat, 13 Mar 2004 15:32:31 -0600 (CST)
From: Mike Silbersack <silby@silby.com>
To: emulation@freebsd.org
Message-ID: <20040313152945.K1617@odysseus.silby.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: VMware 3 changes commited, rtc updated as well
X-BeenThere: freebsd-emulation@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Development of Emulators of other operating systems
	<freebsd-emulation.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-emulation>,
	<mailto:freebsd-emulation-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-emulation>
List-Post: <mailto:freebsd-emulation@freebsd.org>
List-Help: <mailto:freebsd-emulation-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-emulation>,
	<mailto:freebsd-emulation-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Mar 2004 21:32:34 -0000


I just went ahead and committed the changes I had posted to the list
early today.  If you have a working installation of vmware + rtc, there's
no need to update.  Here's my commit message, which sums up the changes:

----
A slew of changes to allow vmware3 to work on 5.x with dynamic device
numbering while not breaking 4.x compatibility:

- Stop using device nodes in /usr/compat/linux/dev and instead rely
on the linuxaltor passing though to /dev
- Create needed device nodes in /dev (on 4.x)
- Account for a change in falloc's semantics that was preventing
the vmmon module from being unloaded on 5.1+ machines.
----

Of course, testing would still be appreciated if you have the time.  I
tested on 4.9-stable and 5.2-current, but there are many ways in which I
still could have broken the port. :)

Mike "Silby" Silbersack