The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: ron minnich <rminnich@gmail.com>
To: Tom Lyon <pugs78@gmail.com>
Cc: Bakul Shah <bakul@iitbombay.org>,
	The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: pseudo tty history
Date: Fri, 15 Aug 2025 18:49:16 -0700	[thread overview]
Message-ID: <CAP6exY+_w4E=XZMfaWAMEWwGziHByQYiQ7HYR93OXxziByJRtQ@mail.gmail.com> (raw)
In-Reply-To: <CANxB0bRew6HheSGW3Dkv+e+-79D35Cw-MOVcRwUr6-bd5e9eaQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1554 bytes --]

was there ever a telnet or other remote access program that predated ptys
on Unix? Was telnet the driving force for ptys? Did the folks implementing
Unix networking bring in ptys before, or as part of, or after networking,
i.e. did folks building networking for Unix realize they needed ptys once
they started working on telnet, or did they plan for ptys from the get go?
I was an observer for some of this stuff, but as a 20-year-old at UDEL I
was also quite out of the loop.

 I also realize there were multiple Unix networking efforts, so this
question is somewhat simplistic.

I'm assuming rsh came a bit later.

On Fri, Aug 15, 2025 at 4:19 PM Tom Lyon <pugs78@gmail.com> wrote:

> Yeah, I was thinking that 4.1c BSD must've had them for rlogin and telnet.
>
> Which got me looking for Fabry and Bill Joy's design/planning documents
> for 4.2, which are not in the TUHS archives.
> Anyone got them??
>
> On Fri, Aug 15, 2025 at 4:15 PM Warner Losh <imp@bsdimp.com> wrote:
>
>> At the very least, 4.2BSD had them for telnet and rlogin. They were
>> static, though. You had to MAKEDEV enough units.
>>
>> Warner
>>
>> On Fri, Aug 15, 2025, 5:00 PM ron minnich <rminnich@gmail.com> wrote:
>>
>>> That was my guess. I figured the people who did the work are on this
>>> list, and primary sources rule.
>>>
>>> On Fri, Aug 15, 2025 at 3:56 PM Ron Natalie <ron@ronnatalie.com> wrote:
>>>
>>>> I think that wikipedia history is somewhat garbled when it comes to the
>>>> UNIX implementations.
>>>>
>>>>
>>>>

[-- Attachment #2: Type: text/html, Size: 3048 bytes --]

  parent reply	other threads:[~2025-08-16  1:49 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-15 22:28 [TUHS] pseudo tty history ron minnich
2025-08-15 22:33 ` [TUHS] " Bakul Shah via TUHS
2025-08-15 22:56   ` Ron Natalie
2025-08-15 23:00     ` ron minnich
2025-08-15 23:15       ` Warner Losh
2025-08-15 23:19         ` Tom Lyon
2025-08-16  0:53           ` Jonathan Gray
2025-08-16  1:49           ` ron minnich [this message]
2025-08-16  2:48             ` Ron Natalie
2025-08-16  3:23             ` Bakul Shah via TUHS
2025-08-16  3:35               ` Clem Cole
2025-08-16  3:50                 ` Aron Insinga
2025-08-16 14:57                   ` Clem Cole
2025-08-17  0:21                     ` Aron Insinga
2025-08-17  1:05                       ` Larry McVoy
2025-08-17  1:13                         ` Al Kossow
2025-08-17  1:16                           ` Al Kossow
2025-08-17  1:25                             ` Al Kossow
2025-08-17  2:02                           ` Larry McVoy
2025-08-17  1:25                         ` Lawrence Stewart
2025-08-17  1:56                         ` [TUHS] Re: magic, was " John Levine
2025-08-18  3:07                           ` Aron Insinga
2025-08-16  3:20           ` [TUHS] " Clem Cole
2025-08-16  3:19     ` Clem Cole
2025-08-16  1:19 ` Jeremy C. Reed

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='CAP6exY+_w4E=XZMfaWAMEWwGziHByQYiQ7HYR93OXxziByJRtQ@mail.gmail.com' \
    --to=rminnich@gmail.com \
    --cc=bakul@iitbombay.org \
    --cc=pugs78@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).