The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] 4.3BSD help: getty ignoring modem status
Date: Sun, 19 Mar 2017 22:25:15 -0400	[thread overview]
Message-ID: <CAC20D2ObQq7fWmxHtTyBRvU-YN6acfAUFxHhH+pLXsazyWvWLQ@mail.gmail.com> (raw)
In-Reply-To: <12242.1489973103@cesium.clock.org>

Eric you are digging out painful memories... he is absolutely right.

On Sun, Mar 19, 2017 at 9:25 PM, Erik E. Fair <fair-tuhs at netbsd.org> wrote:

> One more thing: it's impossible to get an 8-bit clean connection through
> the
> TELNET protocol without speaking the TELNET protocol: even in binary mode,
> you have to escape IAC (0377, 0x7F) in transmission, and eat the IAC byte
> doubling in reception. See RFC-854.
>
> I wrote an implementation of TELNET specifically for the AppleLink/Internet
> E-mail gateway at Apple because we had to speak X.25 (sort of) to the GEIS
> network & mainframe, and I didn't want to buy system-specific, proprietary
> HDLC/LAPB serial gear that would lock me into a particular hardware
> platform,
> so I used a Cisco protocol translator instead - it could be configured to
> map
> a TELNET server connection to a given X.25/X.3 PAD call (akin to a terminal
> server in "milking machine" mode). Worked great, once I had that streaming
> TELNET implementation going to get binary data through the connection.
>
> That design left me free to run the gateway on any Unix system I felt like:
> it started on a Mac SE/30 (A/UX), moved to an SGI-4D/380 (Irix), and ended
> life on a Sun SPARCstation ... 10 or 20 (SunOS 4? Solaris? I forget). So
> long
> as the Unix in question had TCP/IP, Berkeley sockets, a network interface
> (preferably Ethernet), sendmail(8) and perl(1), the gateway could be run on
> it. Didn't even need to be proximate to the Cisco protocol translator -
> just
> somewhere on the same IP network. Most of the code was actually Perl 3 & 4
> because E-mail gatewaying is mostly about string manipulation.
>
>         happy solstice!
>
>         Erik Fair
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170319/cdce6a87/attachment.html>


  reply	other threads:[~2017-03-20  2:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-19  6:37 Noel Chiappa
2017-03-19  7:46 ` Warren Toomey
2017-03-19 13:44 ` Paul Ruizendaal
2017-03-20  0:47   ` Erik E. Fair
2017-03-20  1:25     ` Erik E. Fair
2017-03-20  2:25       ` Clem Cole [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-03-19  5:57 Warren Toomey
2017-03-19  6:18 ` Larry McVoy
2017-03-19  8:06 ` Warren Toomey
2017-03-19  9:57   ` Jacob Goense
2017-03-19 10:08   ` Warren Toomey

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=CAC20D2ObQq7fWmxHtTyBRvU-YN6acfAUFxHhH+pLXsazyWvWLQ@mail.gmail.com \
    --to=clemc@ccc.com \
    /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).