The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: segaloco via TUHS <tuhs@tuhs.org>
To: segaloco <segaloco@protonmail.com>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: UNIX Release 4 Findings
Date: Fri, 10 Feb 2023 17:47:56 +0000	[thread overview]
Message-ID: <7weCqnTEIBgsU9T-WuEz5AJvNsb13t44eGSWu7rG27IcoT6oDkEYg0kHi1NGb9fZzVDTsvVC3fOXXlyMevdLZeAcpvDooMtBPNJbb38XBBM=@protonmail.com> (raw)
In-Reply-To: <lp90CIvVvUyCCVHlX_4IGCr9qHw_foD4f8uffzFbi494KQR36a2udVrOXhy1Uada44CdxaDeu44e3AUP6BEOffuP8jkjvJvxTzXk9E3_vFE=@protonmail.com>

So as of this morning less progress report-y messaging going forward.  Finally got access to the TUHS Wiki so I will be accumulating this and other info there, along with links to emails from the list illuminating various bits.  Clem and I will hopefully be talking nomenclature soon and can get a better handle on not potentially misrepresenting anything.

So without further ado, follow:https://wiki.tuhs.org/doku.php?id=systems:unixts4

Any updates will show up there.  Eventually will re-slug it as something different, but the page slug still reflects the TS nomenclature. The thread referenced in the article aligns more with reality.  Less email updates on discoveries going forward, you can probably RSS to the Wiki for any particular areas of interest.

- Matt G. 

------- Original Message -------
On Thursday, February 9th, 2023 at 8:58 PM, segaloco via TUHS <tuhs@tuhs.org> 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 charge of the manual had approved to live in /usr/man/u_man on the particular box they had hooked up to the typesetter when they cut the plates that eventually printed the book I hold. No amount of printed material will ever capture reality, but it does give a darn good window into it in a more precise way.
> 
> 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. So many branches...
> 
> - Matt G.
> 
> ------- Original Message -------
> On Thursday, February 9th, 2023 at 8:48 PM, George Michaelson ggm@algebras.org wrote:
> 
> 
> 
> > 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.
> > 
> > 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.
> > 
> > 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.
> > 
> > The version numbers were not mutable. What was stamped with them?
> > Perhaps it was.
> > 
> > G

  reply	other threads:[~2023-02-10 17:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-09  1:32 [TUHS] UNIX/TS 4.x Findings segaloco via TUHS
2023-02-10  2:54 ` [TUHS] " Jonathan Gray
2023-02-10  4:38   ` segaloco via TUHS
2023-02-10  4:48     ` George Michaelson
2023-02-10  4:58       ` segaloco via TUHS
2023-02-10 17:47         ` segaloco via TUHS [this message]
2023-02-10  3:07 ` Warner Losh
2023-02-10  3:15   ` Larry McVoy
2023-02-10  3:22     ` Warner Losh
2023-02-10  3:22   ` Jonathan Gray
2023-02-10  3:47     ` Jonathan Gray

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='7weCqnTEIBgsU9T-WuEz5AJvNsb13t44eGSWu7rG27IcoT6oDkEYg0kHi1NGb9fZzVDTsvVC3fOXXlyMevdLZeAcpvDooMtBPNJbb38XBBM=@protonmail.com' \
    --to=tuhs@tuhs.org \
    --cc=segaloco@protonmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).