From: Phil Budne <phil@ultimate.com>
To: tuhs@tuhs.org
Subject: [TUHS] Re: Attempting To Build NOSC and BBN UNIXs + ARPANET code
Date: Fri, 14 Oct 2022 12:08:18 -0400 [thread overview]
Message-ID: <202210141608.29EG8I2j086740@ultimate.com> (raw)
In-Reply-To: <9AA075C9-995F-47F7-9758-2492407DC9FF@planet.nl>
Paul Ruizendaal <pnr@planet.nl> wrote:
> sys4.c: I think this is available in BBN V6:
> https://minnie.tuhs.org/cgi-bin/utree.pl?file=BBN-V6/ken <https://minnie.tuhs.org/cgi-bin/utree.pl?file=BBN-V6/ken>
> In this file the only real network addition is Jack Haverty’s user timer variable, I think. What else is missing?
Side question: What/when is the origin of the pty driver?
https://minnie.tuhs.org/cgi-bin/utree.pl?file=BBN-V6/dmr/pty.c
Has a revision history, but no date/author for its origin.
And
https://minnie.tuhs.org/cgi-bin/utree.pl?file=SRI-NOSC/dmr/pty.c
is simpler, and lacks the changes and history.
https://en.wikipedia.org/wiki/Pseudoterminal#History
claims:
"Unix pseudoterminals originated in 1983 during the
development of Eighth Edition Unix and were based on a similar
feature in TENEX."
But the above pty.c clearly predates that.
Wikipedia continues with further bogosity:
They were part of the 4.2 release of BSD, with a rather
cumbersome openpty() interface defined for use.
with a link to https://www.freebsd.org/cgi/man.cgi?query=openpty&sektion=3
which says
"The openpty() and forkpty() functions first appeared in 4.3BSD Reno."
ISTR in 4.2 days there wasn't any library code to open a ptyXX/ttyXX pair,
which was CERTAINLY cumbersome. forkpty is downright handy, and portable.
phil
next prev parent reply other threads:[~2022-10-14 16:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 11:55 Paul Ruizendaal
2022-10-14 16:08 ` Phil Budne [this message]
2022-10-14 16:37 ` Clem Cole
2022-10-14 19:06 ` Warner Losh
2022-10-14 18:47 ` Lars Brinkhoff
-- strict thread matches above, loose matches on Subject: below --
2022-10-14 20:30 Noel Chiappa
2022-10-12 19:38 Noel Chiappa
2022-10-13 5:50 ` Lars Brinkhoff
2022-10-11 15:08 Paul Ruizendaal
2022-10-10 18:33 [TUHS] " Michael Casadevall
2022-10-10 19:48 ` [TUHS] " Lars Brinkhoff
2022-10-10 20:31 ` Michael Casadevall
2022-10-11 5:31 ` Lars Brinkhoff
2022-10-11 12:57 ` Michael Casadevall
2022-10-11 13:57 ` Lars Brinkhoff
[not found] ` <CAJq=PCV7o_kMvRLXXK9prddmyvf0hAodX+NuqqVF=49iCYt63w@mail.gmail.com>
2022-10-11 19:58 ` Lars Brinkhoff
2022-10-10 20:31 ` Clem Cole
2022-10-10 20:48 ` Michael Casadevall
2022-10-10 21:37 ` Clem Cole
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=202210141608.29EG8I2j086740@ultimate.com \
--to=phil@ultimate.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).