Return to BSD News archive
Newsgroups: comp.os.386bsd.questions From: ian@helen.demon.co.uk (Ian Newham) Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!yarrina.connect.com.au!munnari.oz.au!spool.mu.edu!howland.reston.ans.net!gatech!udel!news2.sprintlink.net!news.sprintlink.net!demon!helen.demon.co.uk!ian Subject: Re: XOpenDisplay failures References: <771348887snz@helen.demon.co.uk> Organization: (none) Reply-To: ian@helen.demon.co.uk X-Newsreader: Simple NEWS 2.0 (ka9q DIS 1.24) Lines: 23 Date: Mon, 13 Jun 1994 19:35:10 +0000 Message-ID: <771536110snz@helen.demon.co.uk> Sender: usenet@demon.co.uk In article <771348887snz@helen.demon.co.uk> ian@helen.demon.co.uk writes: > I'm running NetBSD-current, 5th March ...not so current:) with XFree86 2.00 > > I've recently tried compiling a few things, eg ghostscript, but they > all seem to fail with a Cannot Open Display ':0.0' or similar message > etc.... Somebody has just email'd me explaining this. Apparently a certain span of -current wouldn't allow the screen to be opened for newly compiled binaries. :-( I'm on a dial up in the U.K. so getting the latest -current is impractical for me (read v.expensive) so can anyone out there using -current remember a fix/workaround? Apart from this 'feature' my system seems pretty stable so I don't want to have to start from scratch again if I can help it. Ian. -- +----------------------------------------------------+ | Ian Newham Nottingham, U.K. | | ian@helen.demon.co.uk | +----------------------------------------------------+