The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Lars Brinkhoff <lars@nocrew.org>
To: Dan Cross <crossd@gmail.com>
Cc: TUHS <tuhs@tuhs.org>
Subject: [TUHS] Re: BSD talk program?
Date: Sat, 14 Dec 2024 07:20:58 +0000	[thread overview]
Message-ID: <7wplluloh1.fsf@junk.nocrew.org> (raw)
In-Reply-To: <CAEoi9W6rQwxQLg_SVTUc5_zNX8oprnhfQ=gj0MdjY2cWKt2j6A@mail.gmail.com> (Dan Cross's message of "Fri, 13 Dec 2024 09:28:38 -0500")

Dan Cross wrote:
> I'm curious if anyone has any history they can share about the BSD
> "talk" program.

Allow me to interject for a moment.  Apparently there's a ttylinkd
program that "is a simple daemon that allows incoming ttylink calls to
be routed through to Linux's normal talkd(8) system".  It's TCP port 87
in RFC 1060 "Assigned Numbers", but seems to have been dropped since.
Maybe someone can expand on this.

Apparently this protocol was known at MIT, because there's a Chaosnet
servic called TTYLINK.  The client side is implemented by the MINITS
Chaosnet router/terminal concentrator/etc.

  parent reply	other threads:[~2024-12-14  7:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-13 14:28 [TUHS] " Dan Cross
2024-12-13 15:14 ` [TUHS] " Clem Cole
2024-12-13 15:22   ` Clem Cole
2024-12-13 15:53     ` Larry McVoy
2024-12-13 16:00       ` Warner Losh
2024-12-13 16:04       ` Rich Salz
2024-12-13 16:58       ` Ronald Natalie
2024-12-14 18:04       ` arnold
2024-12-14 19:26         ` Warner Losh
2024-12-14 19:16       ` Marc Donner
2024-12-14  7:20 ` Lars Brinkhoff [this message]
2024-12-14 16:46   ` Dan Cross
2024-12-14 20:41   ` 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=7wplluloh1.fsf@junk.nocrew.org \
    --to=lars@nocrew.org \
    --cc=crossd@gmail.com \
    --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).