From owner-freebsd-questions Tue Feb 1 19:15:40 2000 Delivered-To: freebsd-questions@freebsd.org Received: from smtp.nwlink.com (smtp.nwlink.com [209.20.130.57]) by builder.freebsd.org (Postfix) with ESMTP id 1DAF3403B for ; Tue, 1 Feb 2000 19:15:22 -0800 (PST) Received: from nwlink.com (ip32.r16.d.bel.nwlink.com [207.202.176.32]) by smtp.nwlink.com (8.9.3/8.9.3) with ESMTP id TAA04063; Tue, 1 Feb 2000 19:15:14 -0800 (PST) Message-ID: <3897A048.F5602D2@nwlink.com> Date: Tue, 01 Feb 2000 19:11:04 -0800 From: R Joseph Wright X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: David Kelly Cc: freebsd-questions@FreeBSD.ORG Subject: Re: XWindows won't work with new kernel References: <200002020247.UAA20375@nospam.hiwaay.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Kelly wrote: > > 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. I didn't know whether it was something that would cause problems or not, however, if you're going to make a custom kernel, you might as well choose the one processor that you're going to be running on. -- R Joseph Wright *I merely took the energy it takes to pout and wrote some blues --Duke Ellington* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message