The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: schily@schily.net (Joerg Schilling)
Subject: [TUHS] Help request: uucp, mail on 4.2BSD
Date: Thu, 09 Mar 2017 10:30:09 +0100	[thread overview]
Message-ID: <58c120a1.g7rF8La2GBRyETlb%schily@schily.net> (raw)
In-Reply-To: <e6953ec7-306d-56af-e9bd-ad1b860f95f9@kilonet.net>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1535 bytes --]

Arthur Krewat <krewat at kilonet.net> wrote:

> This is one of the reasons Telebit did the whole UUCP "g" acceleration 
> in the Trailblazer/Worldblazer modems.
>
> The turn-around time for the small packets being acknowledged was so bad 
> over normal modems that it was painful.
>
> So Telebit made the modem do the acknowledgements (IIRC), stream the 
> data over the phone line, and the receiving end would "play along" on 
> the acknowledgements.
>
> It was very effective for news especially.

If you have been forced to connect to a "traditional UUCP" site, this may have 
been a useful concept.

With a packet size of 64 bytes and max. 3 windows, the protocol was OK for 2400 
baud, but not really usable for faster modems.

My enhanced packet handler supported dynamic packet sizes between 32 bytes and 
4096 bytes and 1..7 windows. 

Given that I could update the UUCP implementation of my news-feed in the 
university, this was a better solution than the Telebit protocol spoofing.

BTW: UUCP enhancements have been discussed by many people in comp.mail.uucp
Active people in that group have been e.g.

Ian Lance Taylor	various

Rick Adams		t protocol for TCP/IP

Matthias Urlichs	e protocol. similar to t protocol

Peter Honeyman		g protocol description

Jörg

-- 
 EMail:joerg at schily.net                  (home) Jörg Schilling D-13353 Berlin
       joerg.schilling at fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/


  parent reply	other threads:[~2017-03-09  9:30 UTC|newest]

Thread overview: 76+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-07  7:09 Warren Toomey
2017-03-07  7:11 ` Cory Smelosky
2017-03-07  7:54 ` Lars Brinkhoff
2017-03-07  8:27   ` Warren Toomey
2017-03-07  9:09 ` Warren Toomey
2017-03-07 15:23   ` Dave Horsfall
2017-03-07 20:43   ` Warren Toomey
2017-03-07 22:38     ` Dave Horsfall
2017-03-07 22:45       ` John Floren
2017-03-07 22:50       ` Jacob Goense
2017-03-07 22:58       ` Warren Toomey
2017-03-07 23:46         ` Cory Smelosky
2017-03-07 23:54           ` William Pechter
2017-03-07 23:55             ` Cory Smelosky
2017-03-08  0:03           ` John Floren
2017-03-08  0:05             ` Cory Smelosky
2017-03-08  4:05         ` Dave Horsfall
2017-03-08 10:21         ` arnold
2017-03-07 23:14       ` Arthur Krewat
2017-03-07 23:19         ` Dave Horsfall
2017-03-07 23:27           ` Arthur Krewat
2017-03-08 21:20             ` Josh Good
2017-03-08 21:42               ` Corey Lindsly
2017-03-08 22:59                 ` Arthur Krewat
2017-03-09 20:26                   ` Josh Good
     [not found]     ` <86varkclj1.fsf@molnjunk.nocrew.org>
2017-03-08  7:17       ` Warren Toomey
2017-03-08  9:20     ` [TUHS] UUCP: working systems, come and get them Warren Toomey
2017-03-08 22:16       ` Warren Toomey
2017-03-08 22:31         ` Dave Horsfall
2017-03-11  0:14           ` Mary Ann Horton
2017-03-08 22:33         ` Kurt H Maier
2017-03-09  6:36           ` arnold
2017-03-09 13:02         ` Lars Brinkhoff
     [not found]         ` <86fuimbobi.fsf@molnjunk.nocrew.org>
2017-03-09 22:28           ` Warren Toomey
2017-03-10  7:11             ` Lars Brinkhoff
     [not found]         ` <CAL4LZyjBG_TL06CAhoNY-BW3pCR6qJHVVMq2oUnfVqOHsAf9kA@mail.gmail.com>
2017-03-09 23:19           ` Warren Toomey
2017-03-09 23:23             ` John Floren
2017-03-10  1:57             ` Cory Smelosky
     [not found]               ` <20170310020203.GA14221@minnie.tuhs.org>
2017-03-10  2:03                 ` Cory Smelosky
2017-03-10  1:49       ` John Floren
2017-03-10  2:06         ` Warren Toomey
2017-03-10  2:09           ` Cory Smelosky
2017-03-10 12:25         ` Jason Stevens
2017-03-10 17:50           ` John Floren
2017-03-10 21:38           ` Warren Toomey
2017-03-08 22:03 ` [TUHS] Help request: uucp, mail on 4.2BSD Joerg Schilling
2017-03-08 23:07   ` Arthur Krewat
2017-03-08 23:18     ` Cory Smelosky
2017-03-08 23:39       ` Arthur Krewat
2017-03-09  0:22         ` Cory Smelosky
2017-03-09 14:51           ` Arthur Krewat
2017-03-09 17:53             ` SPC
2017-03-11  5:29             ` jsteve
2017-03-09  1:59     ` Dave Horsfall
2017-03-09  9:30     ` Joerg Schilling [this message]
2017-03-07 17:17 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:51     ` 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=58c120a1.g7rF8La2GBRyETlb%schily@schily.net \
    --to=schily@schily.net \
    /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).