From: brad@anduin.eldar.org (Brad Spencer)
Subject: [TUHS] uucp protocol nits
Date: Fri, 10 Mar 2017 09:28:46 -0500 [thread overview]
Message-ID: <xoninnhnr35.fsf@anduin.eldar.org> (raw)
In-Reply-To: <E48E0A0D-7C80-4FA7-8DE3-13F2B385C292@orthanc.ca> (message from Lyndon Nerenberg on Thu, 9 Mar 2017 18:23:37 -0800)
Lyndon Nerenberg <lyndon at orthanc.ca> writes:
> So if we are going to talk UUCP, how can we not bring up the protocol, and it's beloved behaviour, in certain implementations.
>
> 'g' protocol was what everyone ran. 64 byte packets, in a three packet window. By default. But 'g' could really race along, if provoked. The window could slide up to seven! Unless you were running Xenix, where that provoked a core dump. On most systems, increasing the window size meant binary patching uucico.
>
> I fuzzily remember 'g' implementations that could handle packets up to 256 bytes, but I can't remember now if the basic (pre-HDB) UUCP could deal with that.
>
> HDB cleaned up a lot of things. While complicating the configuration files to no end.
>
> In parallel to all this, Rick Adams was pounding the living daylights out of the BSD UUCP code. That which ran on seismo. Then uunet.
>
> -- uunet!ncc!lyndon (so many uucp path sigs ...)
Back a long time ago, I ran OS/9 on a 6809E Tandy Color Computer 3. The
relationship to Unix is that it was obviously inspired by it, especially
Vx where x <= 6 [or perhaps 4 or 5, the block diagrams describing OS/9
could have described the older Unix systems ]. One of the items I
worked on quite extensively was the UUCP implementation. I didn't write
the original C code reimplementation that it used, but modified it quite
a bit and one of the items I added to it was the ability of the g
protocol to handle a bigger packet window and probably to handle bigger
packets. At the time I dialed it into UUNET once or twice a day for
email and some very small amount of Usenet news. This all would have
been in the 1992 - 1994 time frame. So, ya, the UUCP g protocol could
be fiddled with somewhat and it would likely work.
--
Brad Spencer - brad at anduin.eldar.org - KC8VKS
http://anduin.eldar.org - & - http://anduin.ipv6.eldar.org [IPv6 only]
next prev parent reply other threads:[~2017-03-10 14:28 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-07 17:17 [TUHS] Help request: uucp, mail on 4.2BSD Clem Cole
2017-03-07 17:43 ` Jaap Akkerhuis
2017-03-07 21:14 ` SPC
2017-03-08 1:51 ` John Labovitz
2017-03-10 0:31 ` Steve Simon
2017-03-10 2:04 ` Lyndon Nerenberg
2017-03-10 2:09 ` Lyndon Nerenberg
2017-03-10 2:23 ` [TUHS] uucp protocol nits Lyndon Nerenberg
2017-03-10 2:57 ` Larry McVoy
2017-03-10 3:08 ` Lyndon Nerenberg
2017-03-10 3:28 ` Lyndon Nerenberg
2017-03-10 3:28 ` Lyndon Nerenberg
2017-03-10 14:28 ` Brad Spencer [this message]
2017-03-10 20:34 ` Ron Natalie
2017-03-10 21:42 ` Arthur Krewat
2017-03-10 22:10 ` Lyndon Nerenberg
2017-03-10 22:26 ` Corey Lindsly
2017-03-12 19:38 ` Dave Horsfall
2017-03-10 2:51 ` [TUHS] Help request: uucp, mail on 4.2BSD Dave Horsfall
2017-03-10 3:45 ` Dan Cross
2017-03-10 4:40 ` Lyndon Nerenberg
2017-03-10 9:57 ` Joerg Schilling
2017-03-10 6:34 ` Jaap Akkerhuis
2017-03-10 7:22 ` Erik E. Fair
2017-03-10 7:27 ` Lars Brinkhoff
2017-03-10 15:00 ` Dave Horsfall
2017-03-07 17:45 ` Arthur Krewat
2017-03-07 18:30 ` Jacob Goense
2017-03-07 18:30 ` Dan Cross
2017-03-07 19:00 ` Erik E. Fair
2017-03-07 22:04 ` Dave Horsfall
2017-03-10 6:10 ` Jim Carpenter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xoninnhnr35.fsf@anduin.eldar.org \
--to=brad@anduin.eldar.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).