From owner-freebsd-questions Sun Jun 20 20:57:56 1999 Delivered-To: freebsd-questions@freebsd.org Received: from server4.reno.powernet.net (server4.reno.powernet.net [208.226.189.15]) by hub.freebsd.org (Postfix) with ESMTP id AD83614C18 for ; Sun, 20 Jun 1999 20:57:52 -0700 (PDT) (envelope-from trzy@powernet.net) Received: from p3-21.reno.powernet.net (p3-21.reno.powernet.net [208.226.189.141]) by server4.reno.powernet.net (8.9.0/8.8.5) with ESMTP id UAA19260; Sun, 20 Jun 1999 20:57:25 -0700 (PDT) Date: Sun, 20 Jun 1999 20:52:24 -0700 (PDT) From: Bart Trzynadlowski X-Sender: trzy@Brzuszek To: Andrew MacIntyre Cc: "J.M. Paden" , freebsd-questions@FreeBSD.ORG Subject: Re: x configuration files In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Immediately after I sent the message I figured that out, thats a big "oops" on my part. Thanks for helping me out though! Bart Trzynadlowski On Sun, 20 Jun 1999, Andrew MacIntyre wrote: > On Sat, 19 Jun 1999, Bart Trzynadlowski wrote: > > > file but now X goes to the point where it displays that gray-ish weaving > > background with an X cursor and just quits. The only message is something > > about XKEYBOARD keymap compiler and that errors here are not fatal to the > > X server. Yet it shuts down anyway. My xinitrc is included below. I > > changed nothing except for what is below the "# start some nice programs" > > line. Everything else was originally in the xinitrc file. Thanks for the > > help! > > {...} > > > wmaker & > ^ > xinitrc needs to wait on something, and that is nearly always the window > manager. drop the " &" and it should work. > > -- > Andrew I MacIntyre "These thoughts are mine alone..." > E-mail: andrew.macintyre@aba.gov.au (work) | Snail: PO Box 370 > andymac@bullseye.apana.org.au (play) | Belconnen ACT 2616 > Fido: Andrew MacIntyre, 3:620/243.18 | Australia > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message