From: George Michaelson <ggm@algebras.org>
To: tuhs@tuhs.org
Subject: [TUHS] Re: UNIX/TS 4.x Findings
Date: Fri, 10 Feb 2023 14:48:27 +1000 [thread overview]
Message-ID: <CAKr6gn3G5ZghMCZ8OKEU5DNyGt7f6xJwuBY+VsUP7Agbq7fvew@mail.gmail.com> (raw)
In-Reply-To: <2XyFQMdNqMtF1Mr0uR7953_hlXtegijahATtyjqGWWCLPbLmDGDJMVneA7OOB9TeY1ww6N5b7cJy8u4ceemZqdumwM4jrlzmd0KDJQuVMXA=@protonmail.com>
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
next prev parent reply other threads:[~2023-02-10 4:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 1:32 [TUHS] " 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 [this message]
2023-02-10 4:58 ` segaloco via TUHS
2023-02-10 17:47 ` [TUHS] Re: UNIX Release 4 Findings segaloco via TUHS
2023-02-10 3:07 ` [TUHS] Re: UNIX/TS 4.x Findings 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=CAKr6gn3G5ZghMCZ8OKEU5DNyGt7f6xJwuBY+VsUP7Agbq7fvew@mail.gmail.com \
--to=ggm@algebras.org \
--cc=tuhs@tuhs.org \
/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).