From owner-freebsd-questions Fri Nov 16 4: 0:32 2001 Delivered-To: freebsd-questions@freebsd.org Received: from he0.easygolucky.de (he0.easygolucky.de [62.208.187.122]) by hub.freebsd.org (Postfix) with ESMTP id EF25237B41A for ; Fri, 16 Nov 2001 04:00:28 -0800 (PST) Received: (from mhe@localhost) by he0.easygolucky.de (8.11.6/8.11.6) id fAGC1On39350; Fri, 16 Nov 2001 13:01:24 +0100 (CET) (envelope-from mhe) Date: Fri, 16 Nov 2001 13:01:24 +0100 From: Manuel Hendel To: Jan Grant Cc: FreeBSD Questions Subject: Re: vmware - could not get address for /dev/vmnet1: Message-ID: <20011116120124.GA38872@he0.easygolucky.de> References: <20011116074848.GA37900@he0.easygolucky.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23.2i Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Nov 16, 2001 at 11:49:45AM +0000, Jan Grant wrote: > This seems to be coming from the linux compatability layer upgrade. It's > been discussed a bit on -stable, no solutions as yet. You could try > going back to a -STABLE with a release date prior to the changes > (November 5th, I think, is ok). I thought that there's something wron with vmware. Where does vmware get the information that the network interface is /dev/vmnet1? This doesn't exist. > > You'll probably find that the port's maintainer is already aware of > this; have you checked for/filed a PR? ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ I don't understand this, what do you mean? -- Never look down on anybody unless you helping him up. -Jesse Jackson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message