From: Paul Ruizendaal <firstname.lastname@example.org>
To: The Eunuchs Hysterical Society <email@example.com>
Subject: [TUHS] Re: V8 4BSD or 32V Based? (was: Unix V8 Chaosnet, any takers?)
Date: Sat, 16 Jul 2022 21:27:12 +0200 [thread overview]
Message-ID: <4FE61203-9EDB-4984-B062-00D62215C248@planet.nl> (raw)
> Regarding select, I recall that Dennis implemented it and passed it to
> Berkeley*, but maybe not. He certainly had a hand in its design; I
> distinctly remember talking to him about it after one of his trips out
That is an interesting comment. DMR was on the steering committee for what would become 4.2BSD.
I once spoke with Kirk McKusick about the origins of the sockets API and I think he told me that there was a lot of debate in the committee whether descriptor readiness API should be stateful (like Haverty’s await() https://www.tuhs.org/cgi-bin/utree.pl?file=BBN-V6/ken/awaitr.c ) or stateless (like select). According to Sam Leffler (who I think added select() to 4.1c BSD) the select system call was somewhat modelled after the ADA select statement.
I am speculating now, but I would not be surprised if dmr favoured the stateless design and contributed to its design.
next reply other threads:[~2022-07-16 19:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-16 19:27 Paul Ruizendaal [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-15 17:15 [TUHS] " segaloco via TUHS
2022-07-15 17:50 ` [TUHS] " Warner Losh
2022-07-15 18:41 ` segaloco via TUHS
2022-07-16 9:31 ` Paul Ruizendaal
2022-07-16 10:31 ` Rob Pike
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).