The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Lars Brinkhoff <lars@nocrew.org>
To: Lawrence Stewart <stewart@serissa.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>,
	Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: [TUHS] BTL summer employees
Date: Mon, 10 Aug 2020 18:13:29 +0000	[thread overview]
Message-ID: <7w7du62wty.fsf@junk.nocrew.org> (raw)
In-Reply-To: <81311578-1C53-47F3-930C-8F0A950D4284@serissa.com> (Lawrence Stewart's message of "Mon, 10 Aug 2020 13:08:20 -0400")

Noel Chiappa wrote:
> It'd be interesting to look at the Dover spooler on ITS, and see
> if/how one got to the CHAOS network from C - and if so, how it
> identified the protocol translating box.

It uses the C version of ITS system calls: chaoso() to open I/O
channels, and pktiot() to send/receive packets.

This is now straying out of TUHS territory, but I wouldn't want people
to miss out on the Dover poem:

Dover, oh Dover, arisen from dead.
Dover, oh Dover, awoken from bed.
Dover, oh Dover, welcome back to the Lab.
Dover, oh Dover, we've missed your clean hand...

And now your toner's toney,
And your paper near pure white,
The smudges on your soul are gone
And your output's clean as light..

We've labored with your father,
The venerable XGP,
But his slow artistic hand,
Lacks your clean velocity.

Theses and papers
And code in a queue
Dover, oh Dover,
We've been waiting for you.

Disk blocks aplenty
Await your laser drawn lines,
Your intricate fonts,
Your pictures and signs.

Your amputative absence
Has made the Ten dumb,
Without you, Dover,
We're system untounged-

DRAW Plots and TEXage
Have been biding their time,
With LISP code and programs,
And this crufty rhyme.

Dover, oh Dover,
We welcome you back,
Though still you may jam,
You're on the right track.

-KWH 6/14/81

  reply	other threads:[~2020-08-10 18:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-10 14:02 Noel Chiappa
2020-08-10 17:08 ` Lawrence Stewart
2020-08-10 18:13   ` Lars Brinkhoff [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-08-10 12:53 Noel Chiappa
2020-08-10 13:21 ` Lars Brinkhoff
2020-08-02 13:40 Doug McIlroy
2020-08-02 13:57 ` arnold
2020-08-02 17:13   ` Doug McIlroy
2020-08-03  9:24     ` arnold
2020-08-02 15:12 ` Robert Diamond
2020-08-02 19:05   ` Jon Steinhart
2020-08-03  5:14     ` Heinz Lycklama
2020-08-03 12:55       ` John P. Linderman
2020-08-03 16:26         ` Jon Steinhart
2020-08-10  0:48 ` Dave Horsfall
2020-08-10  0:53   ` Larry McVoy
2020-08-10  6:33 ` Lars Brinkhoff

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=7w7du62wty.fsf@junk.nocrew.org \
    --to=lars@nocrew.org \
    --cc=jnc@mercury.lcs.mit.edu \
    --cc=stewart@serissa.com \
    --cc=tuhs@minnie.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).