From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <tuhs-bounces@minnie.tuhs.org>
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-1.0 required=5.0 tests=HEADER_FROM_DIFFERENT_DOMAINS,
	MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no
	version=3.4.2
Received: from minnie.tuhs.org (minnie.tuhs.org [45.79.103.53])
	by inbox.vuxu.org (OpenSMTPD) with ESMTP id 4ac6e049
	for <ml@inbox.vuxu.org>;
	Fri, 11 Jan 2019 15:34:05 +0000 (UTC)
Received: by minnie.tuhs.org (Postfix, from userid 112)
	id 7EBD99466D; Sat, 12 Jan 2019 01:34:04 +1000 (AEST)
Received: from minnie.tuhs.org (localhost [127.0.0.1])
	by minnie.tuhs.org (Postfix) with ESMTP id 710CE9466C;
	Sat, 12 Jan 2019 01:33:33 +1000 (AEST)
Received: by minnie.tuhs.org (Postfix, from userid 112)
 id D9C8694666; Sat, 12 Jan 2019 01:33:30 +1000 (AEST)
Received: from smtp-out-1.mxes.net (smtp-out-1.mxes.net [205.237.194.119])
 by minnie.tuhs.org (Postfix) with ESMTPS id 3E1CB93D29
 for <tuhs@minnie.tuhs.org>; Sat, 12 Jan 2019 01:33:30 +1000 (AEST)
Received: from Customer-MUA (mua.mxes.net [10.0.0.1])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by smtp.mxes.net (Postfix) with ESMTPSA id 75B5927577;
 Fri, 11 Jan 2019 10:33:28 -0500 (EST)
From: <ron@ronnatalie.com>
To: "'Paul Ruizendaal'" <pnr@planet.nl>,
	<tuhs@minnie.tuhs.org>
References: <39F862F7-7C4B-4A09-B838-942BE0FD2626@planet.nl>
In-Reply-To: <39F862F7-7C4B-4A09-B838-942BE0FD2626@planet.nl>
Date: Fri, 11 Jan 2019 10:33:26 -0500
Message-ID: <1581c01d4a9c2$ffed5340$ffc7f9c0$@ronnatalie.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQIF/SwDqIraLRMb+aIRW09equOABaVHiCMQ
Content-Language: en-us
X-Sent-To: <dHVoc0BtaW5uaWUudHVocy5vcmc=>
X-Sender: ronnatalie.com
Subject: Re: [TUHS] V6 networking & alarm syscall
X-BeenThere: tuhs@minnie.tuhs.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: The Unix Heritage Society mailing list <tuhs.minnie.tuhs.org>
List-Unsubscribe: <https://minnie.tuhs.org/cgi-bin/mailman/options/tuhs>,
 <mailto:tuhs-request@minnie.tuhs.org?subject=unsubscribe>
List-Archive: <http://minnie.tuhs.org/pipermail/tuhs/>
List-Post: <mailto:tuhs@minnie.tuhs.org>
List-Help: <mailto:tuhs-request@minnie.tuhs.org?subject=help>
List-Subscribe: <https://minnie.tuhs.org/cgi-bin/mailman/listinfo/tuhs>,
 <mailto:tuhs-request@minnie.tuhs.org?subject=subscribe>
Errors-To: tuhs-bounces@minnie.tuhs.org
Sender: "TUHS" <tuhs-bounces@minnie.tuhs.org>

> 
> 1. First of all: I understand that early Unix version numbers and dates
mostly
> refer to the manual editions, and that core users had more frequent
> snapshots of a constantly evolving code base.

Eh?  They primarily refer to the distributions (Research V6, V7, PWB, the
various BSD tapes).
I'm not sure what "core users" are referring to.   Most of us had many
versions as we hacked and merged the stock releasesx.

As Clem mentions, V7 had alarm (but simulated sleep in user mode).  PWB
predated that slightly and had both sleep() and alarm() as system calls.
This propagated through to System III and V.
I suspect this all is the result of the philosophy of the guys responsible
for those separate kernel developments rather than an evolution of one or
the other.

As he mentions, I'm fairly sure this has nothing to do with networking
directly.   Just too handy not to have.

A bigger networking issue was select() (or the like).    It used to be an
interesting kludge of running two processes inorder to do simoultaneous
read/write before that.