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 6642 invoked from network); 10 Feb 2023 17:48:19 -0000 Received: from minnie.tuhs.org (2600:3c01:e000:146::1) by inbox.vuxu.org with ESMTPUTF8; 10 Feb 2023 17:48:19 -0000 Received: from minnie.tuhs.org (localhost [IPv6:::1]) by minnie.tuhs.org (Postfix) with ESMTP id 5B2BB41C10; Sat, 11 Feb 2023 03:48:13 +1000 (AEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tuhs.org; s=dkim; t=1676051294; 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=r95Io5eEY3QV4a1xEmELcqeCzC2Xuvkevb4YEAE1hM8=; b=0NY4/hBLUgFz2NBWt9/7buktg5V3Z7yDEBLiTqIv3jOBxYM8F0VpWnkHeP6aYMmiri3GoZ PeRI/D3XCNAAJ32re77JHwvQIiyPQgCL76T0YANvk4qx786TwKk2naAP8p4YSlrwX95sXH ubjvQ9S2bj2SNvm5YgHaKp4YEKkR/sw= Received: from mail-4325.protonmail.ch (mail-4325.protonmail.ch [185.70.43.25]) by minnie.tuhs.org (Postfix) with ESMTPS id EB33641C0F for ; Sat, 11 Feb 2023 03:48:05 +1000 (AEST) Date: Fri, 10 Feb 2023 17:47:56 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1676051282; x=1676310482; bh=r95Io5eEY3QV4a1xEmELcqeCzC2Xuvkevb4YEAE1hM8=; 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=zW6om9tZsNLiJ1tIp+cBHrvtAj7z5n3d2edaT0KjAzt4QVjCGTYn0tx1s72QoFG3U 1nK3rN1i0Z5TTbJZauoM07UNBVDM1LmoNjNxBJzazrcSaBY2Ym9YxEkHsMxCy+Zrl9 CJzTN10GrGMEXq968epArvSuflV2GMqEmmaFuw2LUhf1HnqoJz4v9EDiBJSfZ9L6Eu ZS/SX6X3ZkKrWx31Amt9G9KR/8f3DcUL/Mm+HcjOOlbpT2i6u3o+3okVGl4FZyELDy VWQKUiN9Kb2RiiSMcmdAByqK8ij/spUMOiQfRc5Fg8qnQe863lKXU720ojwnGPhQz1 rD/IUntVB5xEA== To: segaloco Message-ID: <7weCqnTEIBgsU9T-WuEz5AJvNsb13t44eGSWu7rG27IcoT6oDkEYg0kHi1NGb9fZzVDTsvVC3fOXXlyMevdLZeAcpvDooMtBPNJbb38XBBM=@protonmail.com> In-Reply-To: References: <2XyFQMdNqMtF1Mr0uR7953_hlXtegijahATtyjqGWWCLPbLmDGDJMVneA7OOB9TeY1ww6N5b7cJy8u4ceemZqdumwM4jrlzmd0KDJQuVMXA=@protonmail.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: X374JNOQF4FGXUAKTST75ONFHQUFFRB7 X-Message-ID-Hash: X374JNOQF4FGXUAKTST75ONFHQUFFRB7 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: UNIX Release 4 Findings 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 X-Spam: Yes So as of this morning less progress report-y messaging going forward. Fina= lly got access to the TUHS Wiki so I will be accumulating this and other in= fo there, along with links to emails from the list illuminating various bit= s. Clem and I will hopefully be talking nomenclature soon and can get a be= tter handle on not potentially misrepresenting anything. So without further ado, follow:https://wiki.tuhs.org/doku.php?id=3Dsystems:= unixts4 Any updates will show up there. Eventually will re-slug it as something di= fferent, but the page slug still reflects the TS nomenclature. The thread r= eferenced in the article aligns more with reality. Less email updates on d= iscoveries going forward, you can probably RSS to the Wiki for any particul= ar areas of interest. - Matt G.=20 ------- Original Message ------- On Thursday, February 9th, 2023 at 8:58 PM, segaloco via TUHS wrote: > That's all the more reason to be precise, with all the uncertainty there = is at least the fact that I can say this is what the documentarian in charg= e of the manual had approved to live in /usr/man/u_man on the particular bo= x they had hooked up to the typesetter when they cut the plates that eventu= ally printed the book I hold. No amount of printed material will ever captu= re reality, but it does give a darn good window into it in a more precise w= ay. >=20 > On the note of precision, to add fuel to the USG fire, there is also the = USG Program Generic line, which has numbers distinct from this stuff too. S= o many branches... >=20 > - Matt G. >=20 > ------- Original Message ------- > On Thursday, February 9th, 2023 at 8:48 PM, George Michaelson ggm@algebra= s.org wrote: >=20 >=20 >=20 > > I hesitate to throw this into the mix, but I would observe in those > > days, people were a bit less formal about release versions and I have > > a suspicion (but only a suspicion) that from time to time what shipped > > on a 1200bpi tape was not some canonical 'this is the release as of 3 > > months ago' but more 'this is a sh scripted product of the checked out > > state as I understood it, on the box I had available to me, to cut a > > tape. > >=20 > > The tape had to have boot blocks up front. You got told to do mt fsf > > stuff. So.. I accept some of the tape structure was a bit more > > formally policed: giving people the wrong architecture and bootblocks > > would be bad. > >=20 > > But when it comes to what was unpacked for runtime? I think it wasn't > > quite as 'reproducible build' formal as it is now, for some people. > >=20 > > The version numbers were not mutable. What was stamped with them? > > Perhaps it was. > >=20 > > G