From: wkt@tuhs.org (Warren Toomey)
Subject: [TUHS] Validating the s2-bits tape epoch
Date: Sat, 24 Dec 2016 05:25:08 +1000 [thread overview]
Message-ID: <20161223192508.GA2831@minnie.tuhs.org> (raw)
In-Reply-To: <5f63c34a-aa66-f462-8a39-cce86348aa27@aueb.gr>
On Fri, Dec 23, 2016 at 07:15:04PM +0200, Diomidis Spinellis wrote:
> "Finally, the date(1) a.out on the tape uses 1971 as its archive. How
> annoying! After a bit of discussion, Dennis and Warren have agreed that 1972
> is the most probable epoch for s2-bits."
>
> I thought I could validate the epoch by looking at the distribution of
> weekdays for the three alternative years (1971 to 1973). Here are the
> results.
...
> As you can see, unless weekends at the Bell Labs were highly atypical, 1972
> has the most probable distribution of work among the days of the week.
Thanks Diomidis, that helps to confirm the 1972 date for the s2-bits tape.
Cheers, Warren
prev parent reply other threads:[~2016-12-23 19:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-23 17:15 Diomidis Spinellis
2016-12-23 19:25 ` Warren Toomey [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=20161223192508.GA2831@minnie.tuhs.org \
--to=wkt@tuhs.org \
/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).