From: imp@bsdimp.com (M. Warner Losh)
Subject: [TUHS] Whence the 2.x BSD numbering?
Date: Thu, 25 Jun 2009 20:27:53 -0600 (MDT) [thread overview]
Message-ID: <20090625.202753.-1665546165.imp@bsdimp.com> (raw)
In-Reply-To: <20090626014427.GA35098@minnie.tuhs.org>
The FreeBSD (similar in the other BSDs) family tree file shows:
Sixth Edition (V6) -----*
\ |
\ |
\ |
Seventh Edition (V7) |
\ |
\ 1BSD
32V |
\ 2BSD---------------*
\ / |
\ / |
\/ |
3BSD |
| |
4.0BSD 2.7.9BSD
| |
4.1BSD --------------> 2.8BSD
| |
so if the 2.7.9 is really 2.79, I'd like to know about it.
And the chronology lists:
2BSD mid 1978 [QCU]
75 2BSD tapes shipped
2.7.9BSD ?? [SMS]
2.8BSD 1981-07-xx [KSJ]
2.8.1BSD 1982-01-xx [QCU]
set of performance improvements
[KSJ] Michael J. Karels, Carl F. Smith, and William F. Jolitz.
Changes in the Kernel in 2.9BSD. Second Berkeley Software
Distribution UNIX Version 2.9, July, 1983.
[QCU] Salus, Peter H. A quarter century of UNIX.
[SMS] Steven M. Schultz. 2.11BSD, UNIX for the PDP-11.
Googling for [KSJ] is beyond my humble abilities... The numbers from
[QCU] are about right for 2.7.9 to really be 2.79, eg the 79th tape
that left Berkeley before they switched... But that's wild
speculation based on little more than whimsy and knowing how geeks
sometimes think...
Warner
prev parent reply other threads:[~2009-06-26 2:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-26 1:44 Warren Toomey
2009-06-26 2:27 ` M. Warner Losh [this message]
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=20090625.202753.-1665546165.imp@bsdimp.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).