Xref: utzoo comp.mail.uucp:5481 comp.dcom.modems:7385
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!bbn.com!papaya.bbn.com!rsalz
From: rsalz@bbn.com (Rich Salz)
Newsgroups: comp.mail.uucp,comp.dcom.modems
Subject: Re: What should a new UUCP protocol do?
Message-ID: <2992@litchi.bbn.com>
Date: 16 Nov 90 16:01:22 GMT
References: <1990Nov07.155516.17815@ism.isc.com> <1889.2739aa0d@dcs.simpact.com> <+2m8g2.lb1@smurf.sub.org> <1898.273bd977@dcs.simpact.com>
Followup-To: comp.mail.uucp
Organization: BBN Systems and Technology, Inc.
Lines: 13

In <1898.273bd977@dcs.simpact.com> jeh@dcs.simpact.com writes:
>THis I have not seen -- I have tested a 7x4k g through a TB+ and it works fine,
>though it only runs 3x64.
I believe that's because peter wrote the (first version) of the TB spoofing
code.  (He's the H in HDB.)  Most other UUCP's are buggy in that they either
get the negotiation wrong, or believe and then happily overrun their fixed-
sized buffers.  Rick Adams and Carl at Pyramid worked on this stuff over
three years ago (ahh, for the days when pyramid!csg would email me the
latest Pyramid UUCP for the asking... :-)
	/r$
-- 
Please send comp.sources.unix-related mail to rsalz@uunet.uu.net.
Use a domain-based address or give alternate paths, or you may lose out.