From: lyndon@orthanc.ca (Lyndon Nerenberg)
Subject: [TUHS] 4.0 BSD confusion....
Date: Tue, 30 Aug 2011 11:37:44 -0700 [thread overview]
Message-ID: <8F0F32CC-B42B-4B26-B38B-11B9DFC01A62@orthanc.ca> (raw)
In-Reply-To: <20110830010440.GI2818@dereel.lemis.com>
>> : hp(0,0)vmunix
>> 87844+15464+130300 start 0x530
>> VM/UNIX (Berkeley Version 4.1) 11/10/80
>>
>> But the wiki page lists 4.1 being from June of 1981, and 4.0 being from
>> November of 1980.. Did 4.0 BSD ship reporting itself as 4.1? I guess there
>> is the possibility that the kernel may include patches to bring it up to
>> 4.1?
>
I did a bit of digging in the SCCS files on disk 4 of the CD-ROM set. That '4.1' version string was hardwired into vax/vax/machdep.c on November 10, 1980, as delta 4.1. The logs for Locore.c show a commit on November 9, also with delta 4.1, with the comment 'version 4.1 for distrib'.
next prev parent reply other threads:[~2011-08-30 18:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-29 21:16 Jason Stevens
2011-08-30 1:04 ` Greg 'groggy' Lehey
2011-08-30 18:37 ` Lyndon Nerenberg [this message]
2011-08-31 15:08 ` Jeremy C. Reed
[not found] ` <201108301459.p7UEx2Hr018173@chez.mckusick.com>
2011-09-08 13:10 ` Keith Bostic
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=8F0F32CC-B42B-4B26-B38B-11B9DFC01A62@orthanc.ca \
--to=lyndon@orthanc.ca \
/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).