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.0 required=5.0 tests=MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 24251 invoked from network); 22 Dec 2022 17:27:44 -0000 Received: from minnie.tuhs.org (50.116.15.146) by inbox.vuxu.org with ESMTPUTF8; 22 Dec 2022 17:27:44 -0000 Received: from minnie.tuhs.org (localhost [IPv6:::1]) by minnie.tuhs.org (Postfix) with ESMTP id 29A9141C54; Fri, 23 Dec 2022 03:27:06 +1000 (AEST) Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by minnie.tuhs.org (Postfix) with ESMTPS id 9C7B241BD7 for ; Fri, 23 Dec 2022 03:26:55 +1000 (AEST) Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 965D618C079; Thu, 22 Dec 2022 12:26:54 -0500 (EST) To: tuhs@tuhs.org Message-Id: <20221222172654.965D618C079@mercury.lcs.mit.edu> Date: Thu, 22 Dec 2022 12:26:54 -0500 (EST) From: jnc@mercury.lcs.mit.edu (Noel Chiappa) Message-ID-Hash: BHBJG5XGJWGTYELEPPVHHHKAG4X7ZQ7X X-Message-ID-Hash: BHBJG5XGJWGTYELEPPVHHHKAG4X7ZQ7X X-MailFrom: jnc@mercury.lcs.mit.edu 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: jnc@mercury.lcs.mit.edu X-Mailman-Version: 3.3.6b1 Precedence: list Subject: [TUHS] Re: UNIX on (not quite bare) System/370 List-Id: The Unix Heritage Society mailing list Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: > From: Bakul Shah > There is a further para: > Reducing external memory fragmentation to zero by utilizing the VAX- > 11/780 memory mapping hardware for scatter loading is high on the list > of things to do in the second implementation pass. I'm curious as to exactly what is meant by "external memory"? They must mean memory on the Synchronous Backplane Interconnect: http://gunkies.org/wiki/Synchronous_Backplane_Interconnect I.e. what most of us would call 'main memory'. If this code didn't even allocate main memory by pages, instead of in process-size blocks, it sounds like it's much like 32V (or is it 32V that's being discussed; I thought this thread had moved on to the Reiser demand paging version - my apologies it I've gotten lost). Also, this note: http://gunkies.org/wiki/Talk:CB-UNIX from Dale DeJager (which he kindly gave me permission to post) gives a fair amount of detail on the relationship between the Research and CB/UNIX versions, with a brief mention of USG - precisely the era, and relationships, that are so poorly documented. Interestingly, he indicates that the early versions of what later became CB/UNIX used something in the V1/V3 range (V4 was the first one in C), so it dates back earlier than most people apparently assume. If anyone else has any first-hand notes (i.e.from people who were there at the time), about the relationship between all the early systems, for which the author has given permiosssion to post it, please send it to me and I will add it to the appropriate article on the CHWiki. Probably the most needed is more about the roots of USG; Dale has filled in CB/UNIX, and the roots of PWB are covered fairly well in the BSTJ article on it: https://archive.org/details/bstj57-6-2177 at least, for PWB1. Anything that covers the later PWBs would likewise be gratefully receied. I suppose I should also write up the relationships of the later UNIXen - 32V and its descendants too - any material sent to me about them will be most gratefully received. (If anyone want a CHWiki account, to write it up themselves, please let me know). Noel