From owner-freebsd-current Sat May 11 14:29:16 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 8147537B401 for ; Sat, 11 May 2002 14:29:08 -0700 (PDT) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.12.1/8.12.1) with ESMTP id g4BLT68Q104160; Sat, 11 May 2002 17:29:07 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <3CDD607D.BA8EA08C@elischer.org> References: <3CDD607D.BA8EA08C@elischer.org> Date: Sat, 11 May 2002 17:29:05 -0400 To: Julian Elischer , current@FreeBSD.ORG From: Garance A Drosihn Subject: Re: -current and vmware2 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 11:18 AM -0700 5/11/02, Julian Elischer wrote: >seems something broke in the networking side of things using >host-only networking.. vmnet1 doesn't show up any more.. > >If I have a moment I'll look for it but if anyone has >familiarity with it feel free to get there forst.. > >oh yeah.. it doesn't compile any more either... Is this something that just recently broke? I managed to cvsup -current *just* before the new gcc went in, and the vmware2 port is still working for me. However, the last time I compiled vmware2 itself was back on April 10th. I do not remember any problems compiling it before, so I suspect that is related to the new version of gcc. If this is your first attempt to get vmware2 working on -current, there are a few tricks to getting it to work right which the port does not know about yet. The main thing is to check /compat/linux/dev and see what you have for rtc, vmmon, and vmnet1. All of these should be symlinks pointing back to /dev, but rtc and one of the other ones (vmnet1?) are still done via a typical mknod. So, first thing you need to do is: /compat/linux/dev rm rtc vmnet1 ln -s /dev/rtc ln -s /dev/vmnet1 and reboot. Really the port should check for devfs, and do this automatically if that's active. I keep thinking I should try to write a patch for that. That should get vmware to work. When you start a virtual machine, you'll probably still get an error about the rtc device. Me, I just ignore that, because I don't need rtc when running Win2K as the guest OS. But somebody did post a patch to freebsd-current which was supposed to fix that problem. I should dig that patch up and try it out. -- Garance Alistair Drosehn = gad@gilead.netel.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