From: Clem Cole <clemc@ccc.com>
To: Aron Insinga <aki@insinga.com>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: pseudo tty history
Date: Sat, 16 Aug 2025 07:57:18 -0700 [thread overview]
Message-ID: <CAC20D2MKY8a=MJ4jNMzLbokLzWtiuOds7zJM8VT=5372b7i2yA@mail.gmail.com> (raw)
In-Reply-To: <baf1fe40-0d34-4bd0-82dc-2298fc33dbc9@insinga.com>
[-- Attachment #1: Type: text/plain, Size: 3573 bytes --]
Right. What I do not know is what early machines Harvard had from DEC.
MIT had the 18 and 36 bit series which was what I was implying. The key
point though is that if Harvard was the root of the PTY tree it would have
been on one of those systems not a Unix system because Unix did not come to
Harvard until 1974 and RFC 89 was 1971 and RFC 46 in 1970
Sent from a handheld expect more typos than usual
On Fri, Aug 15, 2025 at 8:50 PM Aron Insinga <aki@insinga.com> wrote:
> The https://datatracker.ietf.org/doc/html/rfc89 mentions a PDP-6 and
> PDP-10s which are 36-bit twos complement machines, and a DEC PDP-1 which
> was an 18-bit one's complement machine. The "graphics-oriented" PDP-1
> probably had the well-known Type 30 display which used a large round
> radar-type CRT thanks to the Project SAGE tradition, but there were a
> couple of other graphics display options for the PDP-1.
> https://www.computerhistory.org/pdp-1/graphics/
>
>
> - Aron
>
>
> On 8/15/25 23:35, Clem Cole wrote:
>
> Watch the dates - that's not UNIX. In 1973, Version 4 Unix is first
> released outside of BTL, so the Harvard system being talked about in RFC 89
> is probably an 18 bit ??PDP6 maybe??.
>
> On Fri, Aug 15, 2025 at 8:24 PM Bakul Shah via TUHS <tuhs@tuhs.org> wrote:
>
>> From RFC 89 (dated 19 January 1971) titled "Some historic moments in
>> networking":
>>
>> Second, the Harvard system has temporarily implemented this remote
>> network console interface feature using a DEC style pseudo-teletype
>> (PTY).
>>
>> From RFC 46 (dated April 1970) titled "'ARPA Network Protocol Notes":
>>
>> 3. A standard way for a newly created process to initiate pseudo-
>> typewriter communication with the foreign process which requested
>> its creation.
>>
>>
>> On Aug 15, 2025, at 6:49 PM, ron minnich <rminnich@gmail.com> wrote:
>>
>> 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: 10233 bytes --]
next prev parent reply other threads:[~2025-08-16 14:57 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
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 [this message]
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='CAC20D2MKY8a=MJ4jNMzLbokLzWtiuOds7zJM8VT=5372b7i2yA@mail.gmail.com' \
--to=clemc@ccc.com \
--cc=aki@insinga.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).