From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 28229 invoked from network); 24 Dec 2022 08:58:33 -0000 Received: from minnie.tuhs.org (50.116.15.146) by inbox.vuxu.org with ESMTPUTF8; 24 Dec 2022 08:58:33 -0000 Received: from minnie.tuhs.org (localhost [IPv6:::1]) by minnie.tuhs.org (Postfix) with ESMTP id 9B39E4238C; Sat, 24 Dec 2022 18:58:25 +1000 (AEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tuhs.org; s=dkim; t=1671872305; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-owner:list-unsubscribe:list-subscribe:list-post; bh=z09yoChk9b0xkGGS5taTq7SrMtU96ycEG7dpZB0hd3M=; b=pJ97SraLI8i/cf2VRbL8uZAozwdbKtEBZeGaDzFprZuAH+QrFtzTaAg3fcCX1Bdn/VAqtg P4fLASI7H9ccqzo9no+K8I7UZI9q1C2HMtCS0JgRDQIUJGz+T0cxfgWDWSKrjK8yWH6B27 hpJNbv6hrvv5VAp1texJ86NFQUgPNNE= Received: from mail-40132.protonmail.ch (mail-40132.protonmail.ch [185.70.40.132]) by minnie.tuhs.org (Postfix) with ESMTPS id 51B1342364 for ; Sat, 24 Dec 2022 18:58:19 +1000 (AEST) Date: Sat, 24 Dec 2022 08:58:06 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1671872297; x=1672131497; bh=z09yoChk9b0xkGGS5taTq7SrMtU96ycEG7dpZB0hd3M=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=dRhxxw8WOGo23cr/MjcayUhRrXLp3fk5Y4GmaFwNVP8LipiqlAEjvz/yI1FldLXuC yIpa60PDxRwGf69fCkaTfBWsOydMeoZgpUKLdh9CA08mA3sQbxSpToEzWD07k9CqU2 hZ6ltZMqW2vgnpNeLxgc41A+UKJI7rZteEFc/4T8RTsLuNu5k7y8E1GsP087Eke4kH LgmFGVrYJkUHLxMB5XsQZ6R3OwS6nyvcErGuYK0Zx5wjCcfooouWyr0vjd5DPXNkdN 91rHt1PalWOqisKwIMB5clUtZBSeIdIE69Fk/Dgj8Gc75ZtlVP+bXSpSVf1L2Rhw5I CXA3A2qimqaJQ== To: Jonathan Gray Message-ID: <08n94qOTX7MtEldV_R4HpFjZ1ar4em7foXpHnK659iYVp7cv-ewgjx6nywuiRNladfhaeB2vg0U2nyN1DY3KLggUZDQqvuEpTaWQpvHiEOk=@protonmail.com> In-Reply-To: References: <202212221852.2BMIqMRk003859@ultimate.com> <2PV-DjW5M0eYObQ5MSA_2OzpT0t9A6VXbljYr-F4VfM375f26IygWqKx5bTLQXGM-RaNsNCnaL-Ato2u4dyavj7fgOakY-e5y_2S1uUPJMA=@protonmail.com> <202212222144.2BMLiWHk007731@ultimate.com> Feedback-ID: 35591162:user:proton MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Message-ID-Hash: PDOHJ7FIMTHMTALKEOW42ELHLCQ6IJ5D X-Message-ID-Hash: PDOHJ7FIMTHMTALKEOW42ELHLCQ6IJ5D X-MailFrom: segaloco@protonmail.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tuhs.tuhs.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: tuhs@tuhs.org X-Mailman-Version: 3.3.6b1 Precedence: list Subject: [TUHS] Re: Early supported UNIX manual List-Id: The Unix Heritage Society mailing list Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: From: segaloco via TUHS Reply-To: segaloco Your reference to sema(2) in CB-UNIX prompted me to go check the source and= curiously, that isn't in sysent.c: https://www.tuhs.org/Archive/Distribut= ions/USDL/CB_Unix/SourceCode/cbunix6.pdf (p. 50). However, there is a sys5= .c with some semaphore stuff in it. Not how the code gets from the sigcall= entry to that file, maybe there's a CB-specific syscall aggregator like th= e sys3b systemcall for 3B20-specific stuff. It had never actually occurred= to me that the semaphores in SVR1 weren't the ones from CB-UNIX, I thought= they just forklifted all the IPC into 4.0 from CB. That then means the se= maphores that carried through in System V originated at least in UNIX/TS 4.= 0, but not by way of CB. Minor trivia, but that's news to me. Maybe the s= ysV modification request logs can shed some light, I remember seeing severa= l IPC mentions in there. - Matt G. ------- Original Message ------- On Friday, December 23rd, 2022 at 7:30 PM, Jonathan Gray wr= ote: > On Thu, Dec 22, 2022 at 04:44:32PM -0500, Phil Budne wrote: >=20 > > Matt G wrote: > >=20 > > > One area of immediate curiosity for me is the init system, whether th= e pages suggest it is more in line with research (rc and ttys files) or TS = (inittab, runlevels). > >=20 > > The init (VII) page mentions /etc/rc and refers to ttys (V) which says = the file > > consists of lines with three characters (enable, tty name, getty arg) > >=20 > > getty (VII) describes behaviors for 0, -, 1, 2 > >=20 > > The one interesting bit in section (II) is lock (system call 62.) that > > implements semaphores with subfunctions lock/unlock/tlock, all of > > which take a non-negative semaphore ID called a flag. >=20 >=20 > used by MERT: >=20 > https://www.tuhs.org/Archive/Documentation/Manuals/MERT_Release_0/Unix Pr= ogrammer Manual - UPM - White Tabs/System Calls - man2/lock.2.pdf >=20 > "The semaphores provided in the MERT/UNIX supervisor are identical to > those provided by the USG-UNIX Generic 3 system [8]. > [8] Brandt, R. B., Implementation of Semaphores and Messages in UNIX, MF-= 76-8234-076." > https://www.tuhs.org/Archive/Documentation/TechReports/Heinz_Tech_Memos/T= M-78-3114-4_The_MERT-UNIX_Supervisor_19780420.pdf >=20 > "Make (a program for maintaining other programs) was launched at the > CSRC towards the end of the year and was immediately adopted by USG for > the next generic release (PG-1C300 issue 2). This was a snapshot of the > USG system at mod level 3.33 (January 1976) indicating at least three > distinct levels of evolution: the generic releases, major and minor USG > mod levels." >=20 > "Generic 3.0 was released in spring 1977 (delayed from January)." >=20 > Pirzada, A Statistical Examination of The Evolution of the UNIX System >=20 > "I do remember a conversation with Dennis about semaphores, though. > He mentioned that no less than five groups inside of Bell Labs had > hacked semaphores into the kernel. Each group did it differently." > Steve Johnson > https://minnie.tuhs.org/pipermail/tuhs/2017-February/009748.html >=20 > In CB-UNIX there was sema(2): > https://www.tuhs.org/Archive/Distributions/USDL/CB_Unix/cbunix_man2_04.pd= f >=20 > In System V Release 1, semctl(2), semget(2), semop(2) > http://www.bitsavers.org/pdf/att/unix/System_V_Release_1/301-905_UNIX_Sys= tem_V_Release_1_Users_Manual_Jan83.pdf >=20 > xenix creatsem(2), opensem(2), sigsem(2), waitsem(2) > http://www.bitsavers.org/pdf/intel/system3xx/xenix-286/174385-001_Overvie= w_of_the_XENIX_286_Operating_System_Nov84.pdf