From: norman@oclsc.org (Norman Wilson)
To: tuhs@tuhs.org
Subject: Re: [TUHS] v7 uucp debugging help requested
Date: Fri, 3 Jul 2020 20:35:52 -0400 (EDT) [thread overview]
Message-ID: <20200704003552.EB5914422E@lignose.oclsc.org> (raw)
Grant Taylor:
I'm a little surprised that you're trying to use the 'g' protocol to
talk to v7. I thought the 'g' protocol came out later for TCP over
Ethernet connections. As such I wonder if UUCP on v7 supports the 'g'
protocol.
=====
You're mis-remembering. g was the original protocol,
intended for use over possibly-noisy serial lines (e.g.
modems on POTS). It does error checking of various
sorts with retransmission. I believe it is named g
after the protocol's original designer, Greg Chesson.
Later protocols meant to work over reliable, error-
checked links like a TCP/IP circuit were t and e.
Norman Wilson
Toronto ON
next reply other threads:[~2020-07-04 0:44 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-04 0:35 Norman Wilson [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-07-07 19:20 Norman Wilson
2020-07-07 22:47 ` Rob Pike
2020-07-07 23:42 ` Adam Thornton
2020-07-03 20:52 Adam Thornton
2020-07-03 21:26 ` Clem Cole
2020-07-03 22:38 ` Grant Taylor via TUHS
2020-07-04 0:28 ` Clem Cole
2020-07-04 0:31 ` Clem Cole
2020-07-04 19:33 ` Adam Thornton
2020-07-04 20:02 ` Clem Cole
2020-07-04 21:58 ` Adam Thornton
2020-07-05 5:42 ` Adam Thornton
2020-07-03 22:50 ` John Cowan
2020-07-04 16:33 ` Adam Thornton
2020-07-04 18:34 ` John Cowan
2020-07-04 18:44 ` Jon Forrest
2020-07-04 19:34 ` Adam Thornton
2020-07-06 4:12 ` Dave Horsfall
2020-07-06 4:18 ` Warner Losh
2020-07-06 6:51 ` arnold
2020-07-06 7:11 ` Michael Usher via TUHS
2020-07-06 13:57 ` Clem Cole
2020-07-06 18:51 ` John Cowan
2020-07-06 19:19 ` arnold
2020-07-06 19:36 ` John Cowan
2020-07-06 19:58 ` John Cowan
2020-07-06 20:48 ` Clem Cole
2020-07-07 6:21 ` arnold
2020-07-10 5:05 ` Win Treese
2020-07-10 5:19 ` Warner Losh
2020-07-14 2:52 ` Dave Horsfall
2020-07-06 21:47 ` Dave Horsfall
2020-07-07 6:23 ` arnold
2020-07-07 21:45 ` Dave Horsfall
2020-07-06 21:18 ` Dave Horsfall
2020-07-06 21:47 ` John Cowan
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=20200704003552.EB5914422E@lignose.oclsc.org \
--to=norman@oclsc.org \
--cc=tuhs@tuhs.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).