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, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 27822 invoked from network); 20 May 2023 02:05:13 -0000 Received: from minnie.tuhs.org (2600:3c01:e000:146::1) by inbox.vuxu.org with ESMTPUTF8; 20 May 2023 02:05:13 -0000 Received: from minnie.tuhs.org (localhost [IPv6:::1]) by minnie.tuhs.org (Postfix) with ESMTP id 8562E41070; Sat, 20 May 2023 12:05:07 +1000 (AEST) Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by minnie.tuhs.org (Postfix) with ESMTPS id B72FC4106D for ; Sat, 20 May 2023 12:04:58 +1000 (AEST) Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id BA28718C074; Fri, 19 May 2023 22:04:57 -0400 (EDT) To: tuhs@tuhs.org Message-Id: <20230520020457.BA28718C074@mercury.lcs.mit.edu> Date: Fri, 19 May 2023 22:04:57 -0400 (EDT) From: jnc@mercury.lcs.mit.edu (Noel Chiappa) Message-ID-Hash: QORUSGG7NSAOZEJWGMR7XWYEOWWVU36M X-Message-ID-Hash: QORUSGG7NSAOZEJWGMR7XWYEOWWVU36M X-MailFrom: jnc@mercury.lcs.mit.edu X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; 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: A Census of /etc and /sys Prior to V4 List-Id: The Unix Heritage Society mailing list Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: > From: Matt G. > there is a "core" file included, I wonder if kernel text is swept up in > that. My _guess_ is perhaps not; the disks were really small (the UNIX people started with an RF11, which the first DEC machine I used - a RSTS system - also had; that was _really small - 512KB :-). Probably it did whatever V1 did. I was not up for going to look, since I wasn't familiar with the V1 code - but then I decided to break down and look at it, and also create a minimal index to say what's in each module. (Here: https://gunkies.org/wiki/UNIX_First_Edition#Source_index if anyone is interested. Made easier because the code is very well commented; it's very easy to read.) The code to take core dumps is in u1, at 'badsys:'. It dumps the user's entire possible memory space (i.e. not just up to the 'break'), and then (separately) the 'user' area. The system is not included. I doubt V2/V3 are different. > ac and mq EAE registers are still in use in s2-bits binaries Interesting. How did you work that out, BTW? Also, V1 seems to mandate use of a KE11-A (use is made of it throughout the kernel). > but have been replaced by s1-bits. Interesting; how did you work that out? V3's core (V): http://squoze.net/UNIX/v3man/man5/core doesn't give the format, just says "The actual format of the information is complicated because it depends on what hardware is present (EAE, floating-point option)". Do you have C3's db(I) source? Oh, wait, TUHS has what claims to be V2's db source: https://minnie.tuhs.org/cgi-bin/utree.pl?file=V2/cmd/db1.s but it actually seems to be later; it's conditionalized for having the FPP. So it must be for a machine running the -11/45 - which we seem to have decided is V3? The header for TUHS' V2 says: "The files in cmd/ are recreated from the text fragments found on the file s1-bits.gz." Which agrees with your take: > All in all that pegs the s1-bits fragments as being closer in character > to V3 That's all for the moment... Noel