From: Jason Stevens <jsteve@superglobalmegacorp.com>
To: The Unix Heritage Society <tuhs@tuhs.org>,
Nigel Williams <nw@retrocomputingtasmania.com>
Subject: Re: [TUHS] a possible source for 4.1BSD tapes
Date: Tue, 12 Mar 2019 06:32:24 +0000 [thread overview]
Message-ID: <ADFDF14544A65F35.2cccdb47-39d7-46c3-bbff-d01c7332b3c1@mail.outlook.com> (raw)
In-Reply-To: <CACCFpdwCG4khRgSgfG3nifoJMjUOa30t1dMFMbR-D9USRjLHHA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1257 bytes --]
I would also add that 4.1 also ties into research UNIX v8.
On the VAX (via SIMH) its bootstrapped from a 4.1 system.
David du Colombier's guide uses the 4.1 image I found and modified with some 4.2 to get running on SIMH
http://9legacy.org/9legacy/doc/simh/v8
Not having 4.1 would have made this far more involved. 4.2 is no doubt a major Internet milestone on the way to SunOS & 4.3 while 4.0/4.1 are important in a pre-tcpip focused world.
Naturally I'm biased into thinking they are all important, but I know resources /time are limited.
On Tue, Mar 12, 2019 at 2:22 PM +0800, "Nigel Williams" <nw@retrocomputingtasmania.com> wrote:
On Tue, Mar 12, 2019 at 4:39 AM Larry McVoy wrote:
> Other than for history's sake, I don't see the value of 4.1
On the history side, I found having 4.1 BSD important when we were
recovering the build of a programming language on this version. As we
had the binary we wanted to be sure that when we re-compiled we could
confirm that the result was identical to the original. This was to
ensure that we had recovered the build environment as it was
originally. For that reason, I would urge preservationists to always
try to recover as many incremental versions as possible.
[-- Attachment #2: Type: text/html, Size: 2477 bytes --]
next prev parent reply other threads:[~2019-03-12 6:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-10 7:31 Mike Haertel
2019-03-09 23:24 ` Nigel Williams
2019-03-10 11:18 ` Lars Brinkhoff
2019-03-10 20:55 ` Warner Losh
2019-03-10 22:53 ` Mike Haertel
2019-03-11 0:25 ` Al Kossow
2019-03-11 1:15 ` Mike Haertel
2019-03-11 5:46 ` Jason Stevens
2019-03-11 17:28 ` Mike Haertel
2019-03-11 17:38 ` Larry McVoy
2019-03-11 18:33 ` Lars Brinkhoff
2019-03-11 18:41 ` Clem Cole
2019-03-12 6:21 ` Nigel Williams
2019-03-12 6:32 ` Jason Stevens [this message]
2019-03-12 12:44 ` arnold
2019-03-11 21:47 ` Al Kossow
2019-03-23 17:50 ` reed
2019-03-24 4:19 ` Lars Brinkhoff
2019-03-10 8:20 ` arnold
2019-03-10 15:50 ` Mike Haertel
2019-03-10 19:54 ` arnold
2019-03-10 20:33 ` Warner Losh
2019-03-25 17:19 Richard Tobin
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=ADFDF14544A65F35.2cccdb47-39d7-46c3-bbff-d01c7332b3c1@mail.outlook.com \
--to=jsteve@superglobalmegacorp.com \
--cc=nw@retrocomputingtasmania.com \
--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).