From owner-freebsd-questions Tue Feb 1 19: 5:54 2000 Delivered-To: freebsd-questions@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by builder.freebsd.org (Postfix) with ESMTP id D41014000 for ; Tue, 1 Feb 2000 19:05:51 -0800 (PST) Received: from nospam.hiwaay.net (tnt8-208-170-119-97.dialup.HiWAAY.net [208.170.119.97]) by mail.HiWAAY.net (8.9.3/8.9.0) with ESMTP id VAA10453; Tue, 1 Feb 2000 21:05:42 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.9.3/8.9.3) with ESMTP id UAA20375; Tue, 1 Feb 2000 20:47:33 -0600 (CST) (envelope-from dkelly@nospam.hiwaay.net) Message-Id: <200002020247.UAA20375@nospam.hiwaay.net> X-Mailer: exmh version 2.1.1 10/15/1999 To: R Joseph Wright Cc: freebsd-questions@FreeBSD.ORG From: David Kelly Subject: Re: XWindows won't work with new kernel In-reply-to: Message from R Joseph Wright of "Tue, 01 Feb 2000 00:37:50 PST." <38969B5E.FF82FD53@nwlink.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 01 Feb 2000 20:47:33 -0600 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG R Joseph Wright writes: > Bill Campbell wrote: > > > > I have built a new kernel but when I try to run Xwindows, I get all kinds > > of "Cannot open socket for..." errors and it won't start. I think it also > > says something like "Cannot open socket for tcp". Any help would be > > greatly appreciated. > > There are a few things wrong with your config file. First, I think you > need to choose only *one* processor type. As it is now, you have them > all included. No, that is OK. The GENERIC kernel comes that way so it runs on all variations possibly bypassing some CPU specific optimizations. -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message