From: lm@bitmover.com (Larry McVoy)
Subject: [TUHS] wrong HISTORY in 4.4BSD manual pages?
Date: Wed, 5 May 2010 20:02:47 -0700 [thread overview]
Message-ID: <20100506030247.GI23511@bitmover.com> (raw)
In-Reply-To: <alpine.NEB.2.01.1005052030470.17000@t1.m.reedmedia.net>
2.9BSD, as I recall, was the last release for PDP-11's. Again, as I
recall, it did a pile of work to take advantage of the larger address
space (I think there was 64KI and 64KD).
I don't recall every seeing a 3BSD release.
On Wed, May 05, 2010 at 08:40:12PM -0500, Jeremy C. Reed wrote:
> > Or is this simply because "2BSD" is not a operating system release per
> > se, so "3.0BSD" is correct?
> >
> > But this makes me wonder if my 2BSD versions are newer than first
> > 2BSD, so really 3BSD is correct for some of this.
>
> I was asked off list what version of 2BSD as it may have been the 4.x
> stuff backported. So it is the 2bsd.tar.gz from the minnie.tuhs.org
> archive (which is near identical to the spencer_2bsd.tar.gz). Its TAPE
> file says: May 10, 1979. The READ_ME says: Thu Apr 19 23:25:43 PST 1979.
> And don't see any date stamps included in any files newer than May 1979.
> (So not a backport since is 8 months older than 3BSD and 17 months older
> than 4BSD.)
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs
--
---
Larry McVoy lm at bitmover.com http://www.bitkeeper.com
next prev parent reply other threads:[~2010-05-06 3:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 20:55 Jeremy C. Reed
2010-05-06 1:40 ` Jeremy C. Reed
2010-05-06 3:02 ` Larry McVoy [this message]
2010-05-06 5:56 ` John Cowan
2010-05-06 13:07 ` Milo Velimirovic
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=20100506030247.GI23511@bitmover.com \
--to=lm@bitmover.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).