Path: utzoo!mnetor!uunet!lll-winken!lll-tis!ames!nrl-cmf!cmcl2!rutgers!aramis.rutgers.edu!porthos.rutgers.edu!rapatel From: rapatel@porthos.rutgers.edu ( Rakesh Patel) Newsgroups: comp.windows.x Subject: Re: bugs in X term? and andrew Message-ID: Date: 3 Apr 88 08:12:53 GMT References: <111@cvbnet2.UUCP> Organization: Rutgers Univ., New Brunswick, N.J. Lines: 37 Keywords: andrew, xterm, segmentation fault [ I have some brief questions at the end of this posting for those who have spent some time with the Andrew system.] Here are my experiences with the X11R2 and Andrew installations on Sun 3s running 3.2: The X server will not work when optimized. Most of the clients seem to work fine though. In order to get the Andrew system compiled and at least running (we do get core dumps at times, but it is definitely worth bringing up), you should make sure to get the files in the updates directory within the X.V11R2 distribution from expo.lcs.mit.edu. Also get the README.updates file to find out where the files go. In addition (and also important), you will find fixes in ~ftp/contrib/andrew which help make the system usable. After taking care of the update files and the fixes, there are some things you want to change for a Sun. You want to make sure to change andrew/be2/support/print.c to use the appropriate formating and printing commands. (The default is to look in /usr/ibm for eqn and troff - when on the Sun they are in /usr/bin). You really want to read the installation directions (in the top level README) very carefully. The help program has will run if the fixes are applied and you build the help index as they say to do in the README. The programs are very nice. The help program is great for looking at man pages. For those of you who have things working, I found that the preview program doesn't work. It turned out to be dumping core in nroff!?!?!?! Anyone have any ideas why? Also, has anyone figured out how to set up messages to read newsgroups directly from /usr/spool/news? Rakesh Patel.