Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1a 12/4/83; site rlgvax.UUCP Path: utzoo!watmath!clyde!burl!ulysses!mhuxl!eagle!harpo!seismo!rlgvax!guy From: guy@rlgvax.UUCP (Guy Harris) Newsgroups: net.unix Subject: Re: virtual terminal Message-ID: <1678@rlgvax.UUCP> Date: Wed, 8-Feb-84 02:14:24 EST Article-I.D.: rlgvax.1678 Posted: Wed Feb 8 02:14:24 1984 Date-Received: Fri, 10-Feb-84 01:23:04 EST References: <16162@sri-arpa.UUCP> <43800006@hpfcla.UUCP> Organization: CCI Office Systems Group, Reston, VA Lines: 13 Actually, bashing the innards of UUCP to make it run over a LAN isn't too bad. We're running the 4.2BSD UUCP here, and it has support for UUCP over a TCP/IP connection (it assumes the UNET TCP/IP implementation, though we have a library that provides UNET-compatible subroutine calls under 4.2BSD); we added a super-dumb protocol that assumes that the underlying network protocol (TCP, in this case) does all the error handling and flow control. It gets about 150KB over the Ethernet, which is about the same or higher than the bandwidth FTP gets; running a vanilla UUCP over a LAN would be quite a bit less efficient, as the "g" link-level protocol's overhead would be unnecessarily added to the other transmission overheads. Guy Harris {seismo,ihnp4,allegra}!rlgvax!guy