From: tfb@tfeb.org (Tim Bradshaw)
Subject: [TUHS] UNIX turns forty
Date: Wed, 20 May 2009 09:21:34 +0100 [thread overview]
Message-ID: <3B54F918-4B51-465A-B70D-94A6B72359B6@tfeb.org> (raw)
In-Reply-To: <20090519215610.A10612@eskimo.com>
On 20 May 2009, at 05:56, Derek Peschel wrote:
> Interesting question! And related questions -- When did the current
> start of the epoch get chosen? Were there any false starts or early
> changes? (I seem to recall reading about one change, moving forward
> by a year.) And were there ever any dates in the system that couldn't
> be correctly recorded, because the epoch started too late?
I'm not sure of the case in very early Unix, but I think in recent
(4BSD and later is all I know well) history, time has always been a
signed quantity, so you have as long before the epoch as you do
after. My wife has an amusing (in retrospect) story about someone who
decided it would be interesting to see what happened if you set the
clock on a system (these would have been Suns (definitely) running
SunOS 4.x (I think, might have been 3)) close to the end of time and
see what happens when it wraps: the result was a lot of files with
dates in the long distant past, and a lot of work to fix this (which
she forced the perpetrator to undertake I think).
However I have some memory that really early Unix (a) had a different
epoch and (b) counted in different units related to some clock
interrupt - 60ths of a second? - which gave a rather short wraparound.
--tim
next prev parent reply other threads:[~2009-05-20 8:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 16:48 Tim Newsham
2009-05-15 17:27 ` Jason Stevens
2009-05-15 18:09 ` Al Kossow
2009-05-19 2:20 ` Rafael R Obelheiro
2009-05-19 21:31 ` Warren Toomey
2009-05-19 21:49 ` John Cowan
2009-05-20 0:43 ` Jason Stevens
2009-05-20 4:56 ` Derek Peschel
2009-05-20 5:16 ` Jason Stevens
2009-05-20 8:21 ` Tim Bradshaw [this message]
2009-05-19 4:42 Aharon Robbins
2009-05-19 6:13 ` Jason Stevens
2009-05-19 15:12 ` M. Warner Losh
2009-05-19 15:28 ` Michael Kerpan
2009-05-19 15:21 ` John Cowan
2009-05-21 20:39 Brian S Walden
2009-06-05 3:48 Brian S Walden
2009-06-05 4:18 ` Larry McVoy
2009-06-05 11:42 ` Jim Capp
2009-06-05 14:40 ` John Cowan
2009-06-05 16:06 ` Ian King
2009-06-05 18:29 ` John Cowan
2009-06-06 5:20 ` Ian King
2009-06-05 18:40 ` Jason Stevens
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=3B54F918-4B51-465A-B70D-94A6B72359B6@tfeb.org \
--to=tfb@tfeb.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).