From owner-freebsd-current Tue Oct 2 1:21:58 2001 Delivered-To: freebsd-current@freebsd.org Received: from rj.sgi.com (rj.SGI.COM [204.94.215.100]) by hub.freebsd.org (Postfix) with ESMTP id 9DDAA37B405 for ; Tue, 2 Oct 2001 01:21:55 -0700 (PDT) Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f928LsL08305 for <@rj.corp.sgi.com:current@freebsd.org>; Tue, 2 Oct 2001 01:21:54 -0700 Received: from sgiger.munich.sgi.com (sgiger.munich.sgi.com [144.253.192.2]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via SMTP id KAA1598147 for <@eugate.sgi.com:current@freebsd.org>; Tue, 2 Oct 2001 10:21:26 +0200 (CEST) mail_from (gwk@sgi.com) Received: from cuckoo.munich.sgi.com (cuckoo.munich.sgi.com [144.253.192.109]) by sgiger.munich.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id KAA10991; Tue, 2 Oct 2001 10:21:23 +0200 Received: from hunter.munich.sgi.com (hunter.munich.sgi.com [144.253.197.18]) by cuckoo.munich.sgi.com (SGI-8.9.3/8.9.3) with ESMTP id KAA66441; Tue, 2 Oct 2001 10:21:08 +0200 (CEST) Received: from hunter.munich.sgi.com (localhost.munich.sgi.com [127.0.0.1]) by hunter.munich.sgi.com (8.11.6/8.11.6) with ESMTP id f928KmS01419; Tue, 2 Oct 2001 10:20:49 +0200 (CEST) (envelope-from gwk@sgi.com) Date: Tue, 02 Oct 2001 10:20:48 +0200 Message-ID: From: "Georg-W. Koltermann" To: current@freebsd.org Subject: VMWare2 permission problems on -current as of Sep 26 User-Agent: Wanderlust/2.4.1 (Stand By Me) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) Emacs/20.7 (i386--freebsd) MULE/4.0 (HANANOEN) Organization: SGI X-Attribution: gwk MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII 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 Hi, I have applied the KSE patches to vmware2 that were posted on http://www.ripe.net/home/mark/files/vmware2_kse.patch.tgz. I can now build vmware2, but run into a number of permission problems running it: 1. Xlib: connection to ":0.0" refused by server Xlib: Client is not authorized to connect to Server Error: Can't open display: :0 Can be worked around by "chmod 644 ~/.Xauthority". 2. Cannot open /dev/tty0: permission denied (in a GUI message box). Linux /dev/tty0 seems to refer to FreeBSD /dev/ttyv0, using a chain of two symlinks. "chown $USER /dev/ttyv0" doesn't seem to be effective, but "chmod 666 /dev/ttyv0" makes the message go away. 3. Active virtual terminal (/dev/tty9) is not valid. Permission denied. (in a GUI message box). Seems to be like the above, Linux tty9 is really FreeBSD ttyv8, and a chown is ineffective but a chmod 666 solves it. 4. Warning: Tried to connect to session manager, Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed on stderr. Don't know if this is a problem or just a warning. 5. Permission error creating lockfiles (vmware-lock.whoever) The directory is owned by me. In summary, it seems as though the vmware binary (which is SUID root) is unable to access any files that are only accessible to the invoking user (like .Xauthority), and also unable to access any files accessible by root (like the /dev nodes). Is there a kind of changed permission policy in the new linuxulator that could cause this? By any chance, would I need to recompile the linux_base port? Is anyone using VMWare2 successfully on a recent -current? -- Regards, Georg. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message