The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Brad Spencer <>
To: Larry McVoy <>
Subject: [TUHS] Re: forgotten versions
Date: Tue, 21 Jun 2022 22:55:38 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (message from Larry McVoy on Tue, 21 Jun 2022 17:13:11 -0700)

Larry McVoy <> writes:

> On Tue, Jun 21, 2022 at 05:56:02PM -0600, Jacob Moody wrote:
>> I recently stumbled across the existence of datakit
>> when going through the plan9foundation source archives.
>> Would be curious to hear more about its involvement
>> with plan9.
> Pretty sure datakit predated Plan 9, didn't Greg Chesson work on that?
> He was my mentor at SGI, my memory is datakit was sort of early on in
> his career and then he did XTP, which nobody knows about but I believe
> is still used by the military.
> Unless the early Bell Labs datakit and the Plan 9 datakit are different
> things.

When I was at AT&T in the early to mid '90s Datakit could manifest in a
couple of ways.  The simplest was as a tty ..  that is you had a serial
terminal and used a dial string with bangs in it to get somewhere.  This
method would have used some number of copper pairs into a RJ45 to DB25
adaptor connected to the terminal.  The terminals were usually 730s or
6xx (630s maybe).  They had some graphics ability, sort of, with some
windowing support.  The version of SVR3 we had running on the Vaxs had a
program in it that would be able to take advantage of the windowing
features of the 730 over a serial tty line (multiple windows, X-Windows
like sort of).  I have totally forgotten what that was called, however.
These terminals also had a mouse with them.  The second way that Datakit
would show itself was as a fiber pair tied directly to a computer
system.  There were Datakit fiber boards for nearly all of the platforms
that the group I was in used...  Vax (via a companion box), Tandem, Sun
Sparc, at the very least.  There was, usually, a third party kernel
driver required that would sometimes be a bit messy and/or have a
personality to it.  This set up sometimes provided a dkcu command and/or
a modified cu command and you could use a bang path dial string from the
system to get somewhere else using the Datakit network and act like a
tty.  Or, you could do native Datakit in your user land code.  This is
what the product I worked on did to talk to a Datakit network at the
RBOCs to get access to the switches in the telco network for monitoring
purposes.  Often in those cases, Datakit would be transported over a
X.25 network.  Later, as ethernet and TCP/UDP/IP became the thing, the
switches learned how to speak TCP/IP, although sometimes indirectly
though a translator box in front of the switch.  A number of the telco
switches we talked to spoke a dialect of X.25 called BX.25 (Bell X.25 or
some such) and the translator boxes would exist on the switch side and
our side and basically tunnel BX.25 over TCP/IP.  This was a bit
different then using the Datakit network to get to the switch, but I
seem to remember that some RBOCs did something where BX.25 was sent via
Datakit which in the wider area network was transported over X.25 to the
monitoring system.

There were things called Datakit switches that was a cabinet a few feet
tall and a couple of feet wide.  It housed a bunch of boards of your
choosing depending on how you wanted to use Datakit.  Our group had
their own switch at the site I was at run by the persons dealing with
our development lab.  There was also a number of Datakit switches for
the site itself run by the general IT organization.  I seem to remember
those switches having hot pluggable boards with an embedded 3B system
inside (although I may be misremembering that a bit).

Brad Spencer - - KC8VKS -

  parent reply	other threads:[~2022-06-22  2:56 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-16 23:06 [TUHS] " Rob Pike
2022-06-16 23:17 ` [TUHS] " Earl Baugh
2022-06-16 23:18 ` George Michaelson
2022-06-16 23:44   ` George Michaelson
2022-06-17  0:10     ` Larry McVoy
2022-06-17 16:23     ` [TUHS] Sockets vs Streams (was " Bakul Shah
2022-06-17 17:43       ` [TUHS] " Paul Winalski
2022-06-17 22:52       ` Dan Stromberg
2022-06-17  7:20 ` [TUHS] " Diomidis Spinellis
2022-06-17  7:33   ` Rob Pike
2022-06-17  8:34   ` arnold
2022-06-17 10:52 ` arnold
2022-06-18  7:05 ` Angelo Papenhoff
2022-06-19  7:50   ` Rob Pike
2022-06-19  8:17     ` Angelo Papenhoff
2022-06-19  8:53       ` Rob Pike
2022-06-19  9:02         ` Angelo Papenhoff
2022-06-19  9:14           ` arnold
2022-06-19  9:19             ` Angelo Papenhoff
2022-06-19  9:23               ` arnold
2022-06-19 11:37                 ` Matthias Bruestle
2022-06-19 14:47         ` Kenneth Goodwin
2022-06-19 16:27           ` Al Kossow
2022-06-19 18:32           ` Theodore Ts'o
2022-06-19 18:38             ` Dan Cross
2022-06-21 23:56               ` Jacob Moody
2022-06-22  0:13                 ` Larry McVoy
2022-06-22  0:48                   ` Rob Pike
2022-06-22  1:55                     ` George Michaelson
2022-06-22  2:10                       ` Bakul Shah
2022-06-22  2:14                       ` Jon Steinhart
2022-06-22  2:19                         ` Andrew Hume
2022-06-22  2:58                           ` Rob Pike
2022-06-22  3:09                             ` George Michaelson
2022-06-22  2:16                   ` Andrew Hume
2022-06-22  2:55                   ` Brad Spencer [this message]
2022-06-17 14:50 Paul Ruizendaal
2022-06-18  0:35 Douglas McIlroy
2022-06-18  5:00 ` Kevin Bowling
2022-06-18  5:13   ` Adam Thornton
2022-06-18 16:58     ` Clem Cole
2022-06-18 17:18       ` Warner Losh
2022-06-18 17:57         ` Clem Cole
2022-06-18 19:55 Paul Ruizendaal
2022-06-22 12:06 Noel Chiappa
2022-06-23  0:02 ` Dan Cross
2022-06-23  2:18 Noel Chiappa
2022-06-24  6:47 Paul Ruizendaal
2022-06-25 19:16 ` Anthony Martin
2022-06-25 20:45   ` Paul Ruizendaal
2022-06-27  0:57     ` Kevin Bowling

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).