The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] Last officially distributed and currently available BSD version
Date: Sun, 22 Oct 2017 19:44:15 +0200	[thread overview]
Message-ID: <CAC20D2MEz9CdMFxwtrNhXpMsWHcL_weP5Lbby9vXzitPzkLhYw@mail.gmail.com> (raw)
In-Reply-To: <CAEoi9W5BqLzf-6ZU=WtYzhYgGMj3RTi8hvfb_j3jmXGDsdkT6w@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 3073 bytes --]

On Sun, Oct 22, 2017 at 6:51 PM, Dan Cross <crossd at gmail.com> wrote:

> On Oct 22, 2017 1:39 AM, "Will Senn" <will.senn at gmail.com> wrote:
>
> [...]
> What is the last bootable and installable media, officially distributed by
> Berkeley?
>
> Is that image currently publicly accessible?
>
> What is the closest version, that is currently available, that would match
> the os described in "The Design and Implementation of the 4.4 BSD Operating
> System"?
>
>
> Probably one of the best ways to get questions about installation media
> answered is to simply email Kirk McKusick. He's a really nice guy and will
> probably give you an answer pretty quickly.
>
> That said, of the three distributions you mentioned, bootable/installable
> media only existed for 4.4BSD (also called the "encumbered" distribution).
> -Lite and -Lite2 were "reference distributions."
>
​Right.....​





> It didn't take *too* much work to get -Lite working, but it wasn't
> something that ran out of the box (or more properly, off of the tape).
>
​Pretty much, the idea was that if you have 4.3tahoe or reno system
somewhere, it could build 4.4lite assuming you supplied the few missing
files (which were generally available/findable/reasonably easy to intuit.​




> The original idea was to release 4.4BSD-encumbered to Unix source
> licensees, and at the same time publish 4.4BSD-Lite sans the redacted bits
> as an open source distribution.
>
​Exactly....​  And *lite* would fork off the Academic oriented NetBSD
releases with the academic community doing the support for each system.

My understanding was that the reference hardware at Berkeley was 68030- and
> 68040-based HP 9000 machines,
>
​Sounds right... I thought the encumbered bits worked on CCI, Vaxen (and
possibly SUN1s with the *10 upgrade boards), although might not have been
tested as thoroughly as earlier CSRG releases.


​The 386 bits were the sources of a great deal of issue between CSRG and
Jolitiz.  I was friends with all of the protagonists in that drama so I'm
going to try to be careful what I say here.

There was an 'encumbered' 386 distribution on the ftp site for a long time
although installation was definitely experts only (as I said, I helped with
the original disk support if you read the DDJ articles).  And the spurce of
my previous comments on this mailing list that if you knew about it, you
could get it

These bits are basically the pre-FreeBSD starting point.  FWIW: back in the
day, I had it the running on a Wyse 32:16 for a number of years, and might
still have a backup of it on 1/4" QIC tape; but the HW started to get flaky
and FreeBSD superseded it on other HW and it was not supported.​ I had kept
the boot image around as a reference for a book I was working on at the
time; but eventually just switched to using FreeBSD as the 4.4 'definition'
as it was good enough for what we were doing then.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20171022/32e22ba8/attachment.html>


  parent reply	other threads:[~2017-10-22 17:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-22  5:38 Will Senn
2017-10-22 15:18 ` Michael Parson
2017-10-22 15:31   ` Warner Losh
2017-10-22 16:02     ` Steve Mynott
     [not found] ` <CAEoi9W4L2fwV3ukXh+7TGy8y5rwT3Rt4hhTYQxBDyMi1WJg1XQ@mail.gmail.com>
     [not found]   ` <CAEoi9W55N8sP-Wnkrq=JCi1kuzYfLY8xp_95uhihOFV_xHKO7A@mail.gmail.com>
     [not found]     ` <CAEoi9W7zgGWjbn3V--by+C0XvnYfMEUWj=ieF6bFeKxEgRuFJQ@mail.gmail.com>
     [not found]       ` <CAEoi9W4B9TQj+Wfm8MXq-VW=qE5WW999HT1hNye=vaAU+YZHSw@mail.gmail.com>
     [not found]         ` <CAEoi9W61+WciC=1+kT+vht+krhrHyWRGJfbmTtYb8h6X_SQUCQ@mail.gmail.com>
     [not found]           ` <CAEoi9W5bjmB4Xw8vVEu4kDYELtuc8ciGABNNERoBtzwqnJj+ew@mail.gmail.com>
2017-10-22 16:51             ` Dan Cross
2017-10-22 17:00               ` emanuel stiebler
2017-10-24 18:53                 ` Henry Bent
2017-10-24 19:15                   ` Cory Smelosky
2017-10-22 17:44               ` Clem Cole [this message]
2017-10-22 17:26 Noel Chiappa

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=CAC20D2MEz9CdMFxwtrNhXpMsWHcL_weP5Lbby9vXzitPzkLhYw@mail.gmail.com \
    --to=clemc@ccc.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).