Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!spool.mu.edu!news.nd.edu!mentor.cc.purdue.edu!purdue!ames!agate!bionet!raven.alaska.edu!news.u.washington.edu!plains!tinguely@plains.NoDak.edu From: tinguely@plains.NoDak.edu (Mark Tinguely) Newsgroups: comp.unix.bsd Subject: Re: help needed with X386 Message-ID: <19569@plains.NoDak.edu> Date: 7 Aug 92 14:10:47 GMT Article-I.D.: plains.19569 References: <1992Aug7.032219.4649@newshub.sdsu.edu> Sender: Unknown@plains.NoDak.edu Organization: North Dakota State University Lines: 22 In article <1992Aug7.032219.4649@newshub.sdsu.edu> boyns@newshub.sdsu.edu (Mark Boyns) writes: >I have been trying to get the X386 stuff working but I have had no >luck. First of all I am nfs mounting all the X386 from another >machine and I have made all the links correctly. If you are not running as root, some programs need to be suid (like xterm). Be sure root is root on the NFS mount (or copy xterm to the local disk to suid) If you want to put the window in the utmp, then: ln -s /var/run/utmp /etc/utmp I want to thank all that responded to my question about the Logitech serial mouse. It appears the com line parameters are not being set properly. Manually set the line to 1200 baud, 7 bits (odd parity). I still get keyboard freezes but that is either due to the com.c driver or an ST-01 SCSI card (darn if that doesn't have my X binaries on it :-((). my .xinitrc stty cs7 clocal hupcl cread ignbrk ignpar ospeed 1200 ispeed 1200 < /dev/com1 xhost plains twm & xterm -ls -g 80x35 -bg green