Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ukma!rutgers!elbereth.rutgers.edu!ron.rutgers.edu!ron From: ron@ron.rutgers.edu (Ron Natalie) Newsgroups: comp.os.misc Subject: Re: Don't support System V Message-ID: Date: 3 Feb 89 16:35:13 GMT References: <1659@fai.UUCP> <9301@cit-vax.Caltech.Edu> <2443@cuuxb.ATT.COM> Organization: Rutgers Univ., New Brunswick, N.J. Lines: 23 Having a 3B20 inside AT&T is a lot different than being stuck with one in the field. When I was a consultant, I found that the 3B20 tty driver wasn't SVID complient due to a hideous bug in the VMIN/VTIME handling that caused processes to lock up in an unkillable state. I was working around this problem on an AT&T machine when they put up the new release of UNIX. A year and a half later, on the outside, I was still not able to get this release. As for the Ethernet interface. It refuses to work with anything but these black brick 3COM transcievers that AT&T provides. The CE's are worthless trying to fix this problem. Even when it is working the thing frequently goes on to net spewing continuous garbage datagrams. The telnet/rlogin response is pretty poor in any case compared to what we get on the 3B2's and 3B15's. I talked to some AT&T guys from a group in Princeton, and they admit that their machine is much more advanced with regard to engineering changes than ours. Unfortuatenly, even the $$$ I paid for the hardware upgrade to run TCP hasn't made a big improvement. My conclusion, AT&T really isn't exerting any effort into making the 3B20 a computing product. The 3B15's and the workstations have real support available for them. The 3B20 seems to be a lost soul. -Ron