From owner-freebsd-questions Fri Nov 24 23:23:36 2000 Delivered-To: freebsd-questions@freebsd.org Received: from buchanan-181-249.stures.iastate.edu (buchanan-181-249.stures.iastate.edu [129.186.181.249]) by hub.freebsd.org (Postfix) with ESMTP id E254037B479 for ; Fri, 24 Nov 2000 23:23:32 -0800 (PST) Received: (from kparz@localhost) by buchanan-181-249.stures.iastate.edu (8.11.1/8.11.1) id eAP7QS481168; Sat, 25 Nov 2000 01:26:28 -0600 (CST) (envelope-from kparz) Date: Sat, 25 Nov 2000 01:26:27 -0600 From: Krzysztof Parzyszek To: Bill Schoolcraft Cc: Tim McMillen , freebsd-questions@freebsd.org Subject: Re: VMware for FreeBSD ? Message-ID: <20001125012627.A44419@buchanan-181-249.stures.iastate> References: <3A1E015F.5588E6E5@wiliweld.com> <20001124023630.B7169@buchanan-181-249.stures.iastate> <3A1ECB09.FDF4CDB8@wiliweld.com> <20001124155657.A10072@buchanan-181-249.stures.iastate> <3A1F1471.B5A7F7D4@wiliweld.com> <20001124211929.A12645@buchanan-181-249.stures.iastate> <3A1F5CEC.DF2DDD63@wiliweld.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <3A1F5CEC.DF2DDD63@wiliweld.com>; from bill@wiliweld.com on Fri, Nov 24, 2000 at 10:32:12PM -0800 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Nov 24, 2000 at 10:32:12PM -0800, Bill Schoolcraft wrote: > > Oh, I did, and it installed fine. It's when I go to run it I receive the > following: > > ///////////////////////////////////////// > > [root@FreeBSD ~]--> /usr/bin/vmware & > [1] 572 > [root@FreeBSD ~]--> VMware Workstation is installed, but it has not been > (correctly) configured for your running kernel. To (re-)configure it, your > system administrator must find and run "vmware-config.pl". For more > information, please read the INSTALL file in VMware Workstation's > documentation directory. > > //////////////////////////////////////// Ok, I have figured something out. VMware stores its configuration files in /etc/vmware/ I was able to force vmware to display this message by putting a file `not_configured' in that directory. Removing it brought the usual behavior back (i.e. it was working again). My next guess would be to look for file `not_configured' in the vmware config directory and remove it. As I said, in my case vmware stores it's config stuff in /etc/vmware (it is itself a symbolic link). $ ls -l /etc/vmware/ total 1 -rw-r--r-- 1 root wheel 344 Oct 20 02:52 config lrwxr-xr-x 1 root wheel 21 Oct 19 12:17 vmware -> /usr/local/etc/vmware If you don't have the file `config', here are contents of mine. If you use it, make sure the directories are valid. $ cat /etc/vmware/config vmware.fullpath = "/usr/local/lib/vmware/bin/vmware" wizard.fullpath = "/usr/local/lib/vmware/bin/vmware-wizard" dhcpd.fullpath = "/usr/local/lib/vmware/bin/vmnet-dhcpd" loop.fullpath = ""/usr/local/lib/vmware/bin/vmware-loop" libdir = "/usr/local/lib/vmware/lib" vmnet1.HostOnlyAddress = "192.168.1.1" vmnet1.HostOnlyNetMask = "255.255.255.0" I hope this helps. -- ,oPq J --- Krzysztof Parzyszek 10/15/2000 1:29am --- 7 `8oP' --- Abandon the search for Truth; settle for a good fantasy. --- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message