From owner-freebsd-emulation@FreeBSD.ORG Tue Nov 4 08:14:18 2003 Return-Path: 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 29A6016A4CF for ; Tue, 4 Nov 2003 08:14:18 -0800 (PST) Received: from Daffy.timing.com (ns1int.timing.com [206.168.13.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1BA9F43FAF for ; Tue, 4 Nov 2003 08:14:17 -0800 (PST) (envelope-from jhein@timing.com) Received: from gromit.timing.com (gromit.timing.com [206.168.13.209]) by Daffy.timing.com (8.12.8p2/8.12.8) with ESMTP id hA4GEAEx006259; Tue, 4 Nov 2003 09:14:10 -0700 (MST) (envelope-from jhein@timing.com) Received: from gromit.timing.com (localhost [127.0.0.1]) by gromit.timing.com (8.12.6p3/8.12.6) with ESMTP id hA4GDlJE053843; Tue, 4 Nov 2003 09:13:47 -0700 (MST) (envelope-from jhein@gromit.timing.com) Received: (from jhein@localhost) by gromit.timing.com (8.12.6p3/8.12.6/Submit) id hA4GDlqK053840; Tue, 4 Nov 2003 09:13:47 -0700 (MST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16295.53307.533155.165906@gromit.timing.com> Date: Tue, 4 Nov 2003 09:13:47 -0700 From: John E Hein To: Sean Welch In-Reply-To: <15517789.1067961098798.JavaMail.root@donald.psp.pas.earthlink.net> References: <15517789.1067961098798.JavaMail.root@donald.psp.pas.earthlink.net> X-Mailer: VM 7.17 under Emacs 21.1.1 cc: freebsd-emulation@freebsd.org Subject: Re: VmWare 3 on FreeBSD 4.9-RELEASE X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Nov 2003 16:14:18 -0000 Sean Welch wrote at 09:51 -0600 on Nov 4: > Yes, I do. > > NitroPhys$ export DISPLAY=127.0.0.1:0.0 > NitroPhys$ xterm > xterm Xt error: Can't open display: 127.0.0.1:0.0 > NitroPhys$ This whole $DISPLAY thread is almost definitely a red herring, but... Try localhost/unix:0 If you use localhost/unix:0, it will connect using a unix domain socket instead of a tcp socket. The probable reason you can't display to localhost:0 (nor `hostname`:0 I suspect) is that your X server is running with -nolisten tcp. You can turn that off (it's on by default for security reasons; the recommended way is to use ssh with X11 port forwarding), but it's probably not causing your vmware problems, so this is straying off topic. That said, I don't know why you are having refresh problems with vmware3. I've seen similar problems with vnc, but that's probably not related.