From: Will Senn <will.senn@gmail.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>, tuhs@minnie.tuhs.org
Subject: Re: [TUHS] v7, adb, and fcreat
Date: Thu, 6 Aug 2020 13:36:27 -0500 [thread overview]
Message-ID: <3781fab6-705c-f877-97fd-c1c2dfe5afb6@gmail.com> (raw)
In-Reply-To: <20200806165519.740A418C097@mercury.lcs.mit.edu>
Noel,
Funny how some things take a while to sink in. I've been messing around
with my v6 instance for so long now, that I got to thinking it was v6
:). Sheesh, between you and Clem clueing me in, it finally clicked that
it is just one (of many) bit buckets out there with the moniker v6.
What confused me initially was that these were built from tapes - never
mind that the tapes aren't gold standards, it never occurred to me that
they weren't. I am coming from a world where OS version floppy/cd/dvd
images are copies of a single master (or very small set of masters).
Sure, there are OEM disks out there, but for the most part, if I say,
grab OS X 10.14 and burn it, I'll get the same OS X 10.14 as pretty much
everybody everywhere. These tape things could be snapshots of the
systems they originate from at very different times and with different
software/sources etc. I know I'm basically repeating what y'all said,
but I'm still in shock :).
Will
On 8/6/20 11:55 AM, Noel Chiappa wrote:
> > From: Will Senn
>
> > I don't think adb was in v6, where the fcreat function and buf struct
> > are used... Were Maranzano and Bourne using some kind of hybrid 6+ system?
>
> In addition to the point about skew between the released and internal development,
> it's worth remembering just how long it was between the V6 and V7 releases, and
> how much ground was covered technically during that period.
>
> A lot of that stuff leaked out: we've talked about the upgraded 'Typesetter C'
> (and compilers), which a lot of people had, and the V6+ system at MIT
> (partially sort of PWB1) had both 'adb' and the stdio library. The latter also
> made its way to lots of places; in my 'improved V6 page':
>
> http://www.chiappa.net/~jnc/tech/ImprovingV6.html
>
> it talks about finding the standard I/O stuff in several later V6 repositories,
> including a UNSW tape. But it and typsetter C, also on the Shoppa pack, were
> clearly quite widespread.
>
> Noel
--
GPG Fingerprint: 68F4 B3BD 1730 555A 4462 7D45 3EAA 5B6D A982 BAAF
next prev parent reply other threads:[~2020-08-06 18:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-06 16:55 Noel Chiappa
2020-08-06 18:36 ` Will Senn [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-08-06 19:25 Noel Chiappa
2020-08-06 4:49 Will Senn
2020-08-06 5:00 ` John Cowan
2020-08-06 12:15 ` Will Senn
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=3781fab6-705c-f877-97fd-c1c2dfe5afb6@gmail.com \
--to=will.senn@gmail.com \
--cc=jnc@mercury.lcs.mit.edu \
--cc=tuhs@minnie.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).