Path: utzoo!attcan!uunet!convex!killer!ames!ncar!tank!oddjob!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.mail.uucp
Subject: Re: uucp via a rlogin session
Keywords: uucp, tcp
Message-ID: <13797@mimsy.UUCP>
Date: 30 Sep 88 22:56:15 GMT
References: <531@comdesign.CDI.COM> <317@magnus.UUCP>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 23

>In article <531@comdesign.CDI.COM> pst@comdesign.cdi.com (Paul Traina) writes:
>>I've heard that someone out there has managed to get UUCP to work over
>>rlogin sessions. ...

In article <317@magnus.UUCP> mml@magnus.UUCP (Mike Levin) writes:
>	Sorry, Paul.  Unless I'm *very* much mistaken, rlogin only supports
>an ASCII (7 bit) data stream.  UUCP requires full 8-bits.  This *may* not
>be true on your machine, but I'm sure it is on mine.  :-(

The g-protocol requires an 8-bit path; UUCP itself does not care, but
if you only have the g protocol inside it, you are stuck.  But rlogin
*does* support an 8 bit data path (`rlogin -8').  The problem is that
rlogin, as it is delivered by Berkeley (and thus presuably DEC and Sun)
will not allow you to disable escapes.  `rlogin -e\255' (as Paul tried)
sets the escape character to \.  Since the escape character is in fact
a `char' variable, and holds only 8 bits, there is no input that will
set it to something UUCP will never use.

If you have source, you can fix this; if not, you will have to plead
with your vendor.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris@mimsy.umd.edu	Path:	uunet!mimsy!chris