🚀 go-pugleaf

In article <30342@bu-cs.BU.EDU> eap@bu-it.bu.edu (Eric Pearce) writes:
>In article <11553@udenva.cair.du.edu> mbrookov@udenva.cair.du.edu (Matthew B. Brookover) says:

>  I think you can shut it up with the "-w" flag.  /bin/hc1.4 seems to
>  be the only compiler that will work in most cases.  All the others 
>  crapped out when I tried to compile emacs 18.52.  

I got emacs 18.53 patch from prep.ai.mit.edu that simplified some of the
expressions that the compiler could not deal with.
My emacs users say it works fine now.

>>4) Rup, rusers, and rwall do not work correctly.  rup and rusers is
>>fine between the 2 RTs, but the output from rstatd on the rt is garbage
>>when read by rup on a VAX 11/750's running BSD 4.3 Unix from Mt Xinu.
>>Rup on the RT does net even see the Vax on the net.  Rwall prints the
>>message 3 times to the users on the specified host, and then says that
>>the host, (including the host that rwall was ran form) did not get the
>>message!

>  All of these worked right out of the box for me.  Are you sure you
>  ifconfig'd the interface correctly?  We have 4 RT's sharing a
>  subnet with Sun3's, Sun4's and Sun386i's running 4.0 and an SGI IRIS
>  4D. They all recognize the rwho/ruptime info correctly between each other.

Here is another comment about rup and rusers:
From fink@nucthy.PHYSICS.ORST.EDU Thu Apr 27 20:53:20 1989:
%>4) Rup, rusers, and rwall do not work correctly.

%Yea, tease things never seem to work right. It seems that there is a 4.2,
%4.3 difference.

I guess it is possible that there are several versions of rup, rusers
and rwall floating around.

ftp, rlogin, and NFS seem to work just fine.  I will double check the ifconfigs
just to make shure.

							Matt