From owner-freebsd-questions Mon Dec 16 02:36:50 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA17353 for questions-outgoing; Mon, 16 Dec 1996 02:36:50 -0800 (PST) Received: from pulm1.accessone.com (pulm1.accessone.com [198.68.191.10]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id CAA17348 for ; Mon, 16 Dec 1996 02:36:47 -0800 (PST) Received: by pulm1.accessone.com (4.1/SMI-4.1) id AA00493; Mon, 16 Dec 96 02:37:11 PST Message-Id: <9612161037.AA00493@pulm1.accessone.com> From: "Eric Kylstra" To: "questions" Date: Mon, 16 Dec 96 02:36:38 -0800 Reply-To: "Eric Kylstra" Priority: Normal X-Mailer: Eric Kylstra's Registered PMMail 1.53 For OS/2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: X-Windows - trying to get working Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 16 Dec 1996 06:56:28 +0100 (MET), Bogusz Jelinski wrote: > > >On Sun, 15 Dec 1996, Eric Kylstra wrote: > >> Excuse a few dumb questions here. I have installed 2.1.5 and all the >> basics are working (bash and users are set up). As part of the install >> I took the setup options after the main install to set up XF86Config. >> >> I may have made a mistake when I accepted the default to place >> XF86Config in /etc. I also copied it to /usr/X11R6/lib/X11 after >> things were done. >No mistake here. >> >> At this point none of the programs in /usr/X11R6/bin work even though >> they have the executable permission is set. >What kind of message is displayed on the screen. I bet - xinit file not >found >The most common mistake is to run X without having set the PATH correctly. >That is /usr/X11R6/bin should be added > > > >> Do I need to compile things from xc/programs/Xserver with make >> Makefile, make Makefiles, and make depend? >No need! >Cheers, > >Bogusz > I'm afraid all the path stuff is correct. What I get when I try to run startx, X or any other X-windows program is that a program by that name doesn't exist. This is even though the permissions are correctly set to executable. Any other ideas? Eric Kylstra erick@accessone.com