From owner-freebsd-current Tue Nov 20 11:47:29 2001 Delivered-To: freebsd-current@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with ESMTP id 81EEA37B419 for ; Tue, 20 Nov 2001 11:47:21 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hcshh.hcs.de (Postfix) with ESMTP id 600D9BA10; Tue, 20 Nov 2001 20:47:20 +0100 (CET) Received: from hcswork.hcs.de (hcswork.hcs.de [172.24.124.5]) by hcshh.hcs.de (Postfix) with ESMTP id 25976BA08; Tue, 20 Nov 2001 20:47:19 +0100 (CET) Received: by hcswork.hcs.de (Postfix, from userid 200) id DBAEA3B9; Tue, 20 Nov 2001 20:47:18 +0100 (MET) Subject: Re: vmware fails on -current In-Reply-To: "from Georg-W. Koltermann at Nov 19, 2001 11:00:18 am" To: "Georg-W. Koltermann" Date: Tue, 20 Nov 2001 20:47:18 +0100 (MET) Cc: hm@hcs.de, FreeBSD Current Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL84 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: <20011120194718.DBAEA3B9@hcswork.hcs.de> From: hm@hcs.de (Hellmuth Michaelis) X-Virus-Scanned-HCS: by AMaViS perl-11 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 From the keyboard of Georg-W. Koltermann: > At Sun, 18 Nov 2001 09:37:12 +0100 (MET), > Hellmuth Michaelis wrote: > > > > Thought i update my current this morning and ran into two problem with > > vmware: > > > > 1) when starting vmware, vmware.sh aborts with > > > > vmware.sh: cannot create /compat/linux/dev/vmnet1: no such device > > or address > > Hi Hellmuth, > > that can be fixed with using /dev/vmnet1 instead of the /compat device > in /usr/local/etc/rc.d/vmware.sh. I needed this change since about > two months now, IIRC. Today i got it to compile and run: - apply the patch from Munehiro Matsuda to hostif.c, this makes the vmware2 port compile under -current as of today - as described above, use /dev/vmnet1 instead of /compat/linux/dev/vmnet1 in /usr/local/etc/rc.d/vmware.sh - replace /compat/linux/dev/vmnet1 with a symlink to /dev/vmnet1 (perhaps the previous step would be unnecessary by this one) After this, vmware comes up and then complains about not able to use /dev/rtc (/dev/rtc is present in /compat/linux and is kld-loaded) but then continues to start up and runs. One thing which looks funny to me is this that the vmnet1 device files have different minor numbers: /root ll /usr/compat/linux/dev/vmnet1-BAK /dev/vmnet1 crw------- 1 root wheel 149, 0x00800001 Nov 20 18:50 /dev/vmnet1 crw-rw-rw- 1 root wheel 149, 0x00010001 Nov 20 18:42 /usr/compat/linux/dev/vmnet1-BAK (where /usr/compat/linux/dev/vmnet1-BAK is from the vmware2 port install and moved from vmnet1 to vmnet1-BAK before the new symlink was made). hellmuth -- Hellmuth Michaelis Tel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message