djb@cbterra.ATT.COM (David J. Bryant) (04/21/88)
Alas, I have spent the last four days trying to get X11R2 installed on some Sun workstations here and have been unable to get things completely operational. After exhausting my own immediate resources, I discovered comp.windows.x and thought I'd apply to the net for guidance. Here's the situation -- I am installing the full distribution on our Sun 2/170 fileserver, and attempting to run it on my diskless Sun 2/120. Both are running Sun UNIX 4.2 Release 3.2 (and are quite operational under suntools and with rlogin, et. al). Here's what I've done: 0) disen-tar'ed the distrubution onto acres of fertile disk 1) edit util/imake.includes/Sun.macros to prevent -O compiler optimization (I learned this from this newsgroup, by the way!) 2) make World 3) make install 4) put /usr/bin/X11 in my path 5) make Xsun, xterm and xinit setuid root. 6) cd /dev ; MAKEDEV bwtwo0 ; /etc/mknod /dev/bell c 12 2 Attempts to execute X produce the following: A) % xinit I get the full-screen halftone and an X cursor I can steer with my mouse. No xterm window. After ~10 seconds X exits leaving me back in suntools. No error messages. B) % xinit xclock -g 200x200-0+0 -display unix:0 -- Xsun Again the full-screen halftone and ambulatory X cursor. After a few seconds, a white square appears in the upper right corner of the display, but no clock face (or anything else) ever appears. From another terminal a "ps" reveals xinit, xclock and Xsun are all idle. I "kill -1" the xclock and everything exits and I'm back in suntools. Again no error messages. Trying to start xterm explicitly from the xinit command line produces results like those in case A) above. Other xtools (uwm, xlogo) exhibit the same behaviour as xclock in case B) (e.g. they do something simple (draw a white or black square, beep the bell) then sit idle). What obviously simple thing am I overlooking? I can't imagine it's not something straightforward -- bunches of other folks have certainly done exactly what I'm trying to do and haven't had this problem (except perhaps the cc -O headache). Help?!? I humbly submit my supplication to the collective wisdom of comp.windows.x. I want X-Windows working! (Please?) David J. Bryant AT&T Bell Laboratories Columbus, Ohio cbosgd!djb (614) 860-4516 (call collect, even)