Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!snorkelwacker!spdcc!dyer
From: dyer@spdcc.COM (Steve Dyer)
Newsgroups: comp.windows.x
Subject: problem starting X11R4; what's (not so) obvious?
Message-ID: <1130@ursa-major.SPDCC.COM>
Date: 5 Jan 90 01:40:09 GMT
Reply-To: dyer@ursa-major.spdcc.COM (Steve Dyer)
Organization: S.P. Dyer Computer Consulting, Cambridge MA
Lines: 23

Took binaries, libraries, includes of VAX4.3BSD X11R4 installation
over to a uVAX-II/qdss mono system which had heretofore been running
some variant of X10r4.

Everything's in place; no remnants of old X10 stuff around, xterm properly
SUID root, plenty of pseudo-TTYs, /usr/bin/X11/Xqdss linked to /usr/bin/X11/X,
no weird .Xdefaults or .xinitrc files.  The X11 unix domain socket gets 
created OK.  At this point in time, no entries in /etc/ttys for ttyv0/qdss
console (i.e., no getty's sitting waiting).  In other words, nothing obviously
wrong.

Symptom: "xinit" invoked manually from another terminal brings up the
gray stipple and mouse cursor, but then terminates with no errors other
than "waiting for X server to terminate.." which it then does.  I
suspect that "xterm" is failing, but I'm not sure where to look next.
There are no messages betraying why it's failing.

Is there anything obvious I'm missing before I start rolling up my sleeves?

-- 
Steve Dyer
dyer@ursa-major.spdcc.com aka {ima,harvard,rayssd,linus,m2c}!spdcc!dyer
dyer@arktouros.mit.edu, dyer@hstbme.mit.edu