*BSD News Article 88957


Return to BSD News archive

#! rnews 1735 bsd
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!lucy.swin.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!cs.mu.OZ.AU!munnari.OZ.AU!news.ecn.uoknor.edu!news.wildstar.net!news.ececs.uc.edu!newsfeeds.sol.net!nntp.uio.no!sn.no!online.no!not-for-mail
From: ragnar@online.no (Ragnar Nielsen)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: FreeBSD - X Windows config error
Date: Wed, 12 Feb 1997 12:50:34 GMT
Organization: ID Communication as
Lines: 24
Message-ID: <3301ba9b.10222474@news.online.no>
References: <32FCCC7A.6BF4@iserv.net> <5dilbn$26o@uuneo.neosoft.com>
NNTP-Posting-Host: elmer.idgruppen.no
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Newsreader: Forte Agent .99g/32.339
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:35361

On 8 Feb 1997 19:49:11 GMT, conrads@neosoft.com (Conrad Sabatier)
wrote:

In article <32FCCC7A.6BF4@iserv.net>,
	Bill <wott@iserv.net> writes:
> While installing FreeBSD 2.1.6, when I get to the point of configuring 
> X-Windows I receive an error:
>  "_X11TransSocketUNIXConnect:can't connect error=02"

I remember seeing the same thing, and if memory serves me correctly,
the culprit was the X support having been removed from the generic
install kernel. (Due to space constraints? I am quite amazed that 
they managed to cram as much as they did onto a single boot floppy.)
I recall solving the problem by rebuilding a kernel with, among other
things, X support enabled.

(If I am correct about the install kernel lacking X support, perhaps
the sysinstall routine ought to be changed to reflect this? I'm not
certain, this was a while ago, and I did a lot of things with my
kernel config.)

Regards,

Ragnar