On Sat, Dec 14, 2024 at 2:21 AM Lars Brinkhoff <lars(a)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.