Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site ulysses.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!smb
From: smb@ulysses.UUCP (Steven Bellovin)
Newsgroups: net.dcom
Subject: Re: uucp for V6?
Message-ID: <1267@ulysses.UUCP>
Date: Fri, 23-May-86 17:23:41 EDT
Article-I.D.: ulysses.1267
Posted: Fri May 23 17:23:41 1986
Date-Received: Sun, 25-May-86 11:19:24 EDT
References: <141@otto.UUCP> <594@mordred.purdue.UUCP>
Organization: AT&T Bell Laboratories, Murray Hill
Lines: 19

> Phew. I had one many years ago, while I was still at U of Cincinnati.
> The folks at Duke, or BRL, I'm not sure, had developed a v7 compatability
> library and back-ported the v7 c compiler. Maybe one of those folks out
> there still has a copy on a tape somewhere; I know I don't have access
> any more. But, at least, be comforted in knowing that it did exist
> at one point, and perhaps someone can still dig it up for you.

Duke converted to v7 relatively early, so the emulation library was probably
done at BRL.  Back in the mists of time, I retrofitted uucp to v6 when I
was at UNC (to talk with Duke), but I didn't keep a copy.  Apart from the
user-level stuff, you'll have to hack the kernel -- on v6, raw mode tty is
*not* an 8-bit data path; it still uses 0xFF as a delimiter in places (at
least two, as I recall, but it's been at least N years, and maybe more).
There may have been stuff about the parity bit, and about sending ^D characters
out; I recall having to change getty and write to deal with the sudden lack
of parity.  (As you can see, adding uucp to a v6 system doesn't conserve
parity.  But that law of physics has been repealed anyway.)

		--Steve Bellovin