Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!mit-eddie!bu-cs!budd
From: budd@bu-cs.UUCP
Newsgroups: comp.dcom.lans,comp.unix.wizards,comp.mail.uucp
Subject: Re: uucp through Bridge CS/100
Message-ID: <5817@bu-cs.BU.EDU>
Date: Sat, 28-Mar-87 14:02:11 EST
Article-I.D.: bu-cs.5817
Posted: Sat Mar 28 14:02:11 1987
Date-Received: Sun, 29-Mar-87 09:40:58 EST
References: <463@umnd-cs.D.UMN.EDU>
Reply-To: budd@bu-cs.UUCP (Philip Budne)
Followup-To: comp.mail.uucp
Organization: Boston Univ. CS Dept.
Lines: 19
Xref: utgpu comp.dcom.lans:307 comp.unix.wizards:1579 comp.mail.uucp:371

Summary:
Keywords:


If you have 4.3 uucp (or 4.2 bsd with the 'f' protocol), you might try
that.  The 'f' (PAD) protocol assumes only 7 bit characters, flow
control, and no control characters other than ^P and NUL.  If ^P is a
problem you can patch location Msync to contain some other character.

The PAD protocol exists for connections on X.25 PAD lines that are
"mostly" reliable and flow controlled.  Checksumming is done on a
per-file basis.  The SYSVR2 'x' protocol does NOT appear to be
compatible (does no checksumming?)

rlogin will still have problems for normal uucp: some control
characters are sent as out of band messages, and you cannot disable
the attention (~) sequences.

I have been experimenting with uucp over our Ungerman/Bass NET1
terminal network with the 'g' (standard uucp packet) protocol modified
to quote all control and 8-bit characters. We have only one directly
connected modem on bu-cs, but the terminal network has a bank of 97!!