The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: imp@bsdimp.com (Warner Losh)
Subject: [TUHS] V7 32V 3BSD dates
Date: Fri, 8 Dec 2017 21:44:47 -0700	[thread overview]
Message-ID: <CANCZdfpRrXqTuL6=Xgwdp1arB0h6cqKtBNfXtAAsPOrMG7EbZQ@mail.gmail.com> (raw)

OK. I'm confused. Maybe people here can help me understand.

Looking at the V7 sources, it looks for all the world like they were
released Jan 10, 1979. This release was PDP-11 only. So far, so good.

32V, a port to the VAX, is listed as 'early 1979'. Dates in the files in
the archive suggest March 26th, 1979 (though there are dates as late as May
3rd and April 30th on two files that are trivial). The tape we have in the
archive has a date Feb 22, 1980 written on it. Given the dates, that's only
3 months after V7 was released. This seems very fast, but maybe it's OK
since it's a swapping release....

3BSD, The Berkeley 32V has file dates as late as Mar 22, 1980... This seems
reasonable for turning V7 from swapping into paging... about a year is fast
but not crazy fast.

My question is: did these three events really happen in this quick
succession? Did USDL folks get started with a preliminary V7 for V32 or was
the port really done in 2 and a half months? Likewise with UCB and 3bsd:
did they start early?

Warner
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20171208/05b10765/attachment.html>


             reply	other threads:[~2017-12-09  4:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-09  4:44 Warner Losh [this message]
2017-12-09  7:00 ` Jeremy C. Reed
2017-12-09  7:14   ` Warner Losh

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='CANCZdfpRrXqTuL6=Xgwdp1arB0h6cqKtBNfXtAAsPOrMG7EbZQ@mail.gmail.com' \
    --to=imp@bsdimp.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).