The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Dan Cross <crossd@gmail.com>
To: Lars Brinkhoff <lars@nocrew.org>
Cc: TUHS <tuhs@tuhs.org>
Subject: [TUHS] Re: BSD talk program?
Date: Sat, 14 Dec 2024 11:46:31 -0500	[thread overview]
Message-ID: <CAEoi9W4zWFBxT9sE0b2eOBUn235Q9h8-9epmoD7eTFzOUdj0Cw@mail.gmail.com> (raw)
In-Reply-To: <7wplluloh1.fsf@junk.nocrew.org>

On Sat, Dec 14, 2024 at 2:21 AM Lars Brinkhoff <lars@nocrew.org> wrote:
> 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".

The only `ttylinkd` that I'm aware of is the one that's part of the
Linux AX.25/NETROM/Rose suite. This lets a ham set up a service for
one of those protocols; I set this up for connected-mode AX.25 at my
QTH (`KZ2X-2` on 144.09 MHz in the Boston area).

In a nutshell, if someone uses AX.25 and connects to that SSID, the
system invokes the ttylinkd daemon, which knows enough about the
`talk` protocol to connect to a talk daemon and send an invitation to
a (fixed) user. That user can use any normal `talk` client to talk to
the user on the radio end, allowing keyboard-to-keyboard
communication. It's not character-by-character the way that normal
"talk" is because AX.25 is in the way and generally wants to batch up
keystrokes into lines/packets (it's slow), but it's kinda cool. Of
course, no one around here uses it. :-(

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

I suspect this is something different, and the name collision is just
an unfortunate coincidence.

        - Dan C.

  reply	other threads:[~2024-12-14 16:47 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
2024-12-14 16:46   ` Dan Cross [this message]
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=CAEoi9W4zWFBxT9sE0b2eOBUn235Q9h8-9epmoD7eTFzOUdj0Cw@mail.gmail.com \
    --to=crossd@gmail.com \
    --cc=lars@nocrew.org \
    --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).