Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!caip!seismo!umcp-cs!cvl!umd5!zben
From: zben@umd5.UUCP (Ben Cranston)
Newsgroups: net.lang.c
Subject: Re: cdecl availability
Message-ID: <1056@umd5.UUCP>
Date: Wed, 2-Jul-86 18:37:18 EDT
Article-I.D.: umd5.1056
Posted: Wed Jul  2 18:37:18 1986
Date-Received: Fri, 4-Jul-86 08:27:51 EDT
References: <2218@umcp-cs.UUCP>
Reply-To: zben@umd5.UUCP (Ben Cranston)
Organization: U of Md, CSC, College Park, Md
Lines: 29
Summary: BitNet linkage at UMD2

In article <2218@umcp-cs.UUCP> chris@maryland.UUCP (Chris Torek) writes:

> ....  BITNET people should consider using
> umd2.umd.edu as a gateway, as it is practically on the same Ethercable
> as mimsy.umd.edu.

Well, Chris, this is close (and we hope will be closer in the near feature).
As I understand it UMD1 is on the Ethercable.  UMD1 has a 40KB sync link to
UMD2, which then has a 64KB HASP link to UMDD.  So far, not too terribly bad.
But the kicker is that UMDD's link to the rest of BitNet is all of 9600 baud
and is going to be the bottleneck.   

We have the hardware for UMD2 to talk directly to the Ethercable and have
bounced commands off it, so all we really need to do is cobble together a
device driver and low level communications handler for it.

If there is a huge demand for cdecl on BitNet maybe we can get one of the
BitNic servers to carry it.  Then BitNet people would say (something like):

     tell bitnic sendme cdecl

and a card deck would automagically appear in their (virtual) card reader.

Chris, I hope there aren't any lines in CDECL longer than 80 characters...

-- 
                    umd5.UUCP    <= {seismo!umcp-cs,ihnp4!rlgvax}!cvl!umd5!zben
Ben Cranston zben @ umd2.UMD.EDU    Kingdom of Merryland Sperrows 1100/92
                    umd2.BITNET     "via HASP with RSCS"