From owner-freebsd-current Mon Sep 2 9:23:11 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 862DB37B48F for ; Mon, 2 Sep 2002 09:23:01 -0700 (PDT) Received: from haystack.lclark.edu (haystack.lclark.edu [149.175.1.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B1B043E42 for ; Mon, 2 Sep 2002 09:23:01 -0700 (PDT) (envelope-from eta@lclark.edu) Received: from copeland-30-191.lclark.edu (anholt@copeland-30-191.lclark.edu [149.175.30.191]) by haystack.lclark.edu (8.9.3/8.9.3) with ESMTP id JAA19998; Mon, 2 Sep 2002 09:22:49 -0700 (PDT) Subject: Re: groff and X11 broken (before gcc3.2) From: Eric Anholt To: Christian Weisgerber Cc: freebsd-current@FreeBSD.ORG In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 02 Sep 2002 09:22:49 -0700 Message-Id: <1030983769.499.15.camel@anholt.dyndns.org> Mime-Version: 1.0 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 On Mon, 2002-09-02 at 05:35, Christian Weisgerber wrote: > I just finished updating my alpha box to shortly before the gcc3.2 > import and now I'm seeing some weird breakage: > $ startx > [...] > xinit: No such file or directory (errno 2): unable to connect to X server > xinit: No such process (errno 3): Server error. > > (Hmm, actually that may be due to the XFree86-Server-4.2.0_5 to _6 > update. I think I haven't restarted the X11 server since.) You need to either reinstall Xwrapper port, or setuid root your XFree86 and accept the possible security holes. I wish we could accept having some sort of suid Xwrapper installed with XFree86-4-Server, but that would probably be shot down for security concerns by those who don't use startx. -- Eric Anholt http://people.freebsd.org/~anholt/dri/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message