View Single Post
  #3   (View Single Post)  
Old 4th April 2012
comet--berkeley comet--berkeley is offline
Real Name: Richard
Shell Scout
 
Join Date: Apr 2009
Location: California
Posts: 136
Default

Quote:
Originally Posted by J65nko View Post
This code is pretty funny!

You know there is trouble coming with a define like this:

Code:
+#define	KERN_EMULATEMAYANPROPHESY 79	/* int: prevent the first epoch */
And I was curious to see exactly what time the clock stops:

Code:
+#define END_13BAKTUN	1356069600
as the embedded documentation is a little confusing:
Code:
 /*
+ * Wikipedia: "The current (13th) b'ak'tun will end, or be completed, on
+ * 13.0.0.0.0 (December 21, 2012 using the GMT correlation".  GMT or
+ * Mexico/General? What's 6 hours between Mayans friends.. let's follow
+ * 'Mexican time' rules.  You might get 6 more hours of reading your
+ * mail, but don't count on it.
+*/
So I ran it through the date command:
Code:
$  date -r 1356069600            # OpenBSD
$  date --date='@1356069600'     # Linux
Thu Dec 20 22:00:00 PST 2012
But I'm more concerned with
date 2147483647
when it turns
into 2147483648 ...

On Linux no problem:
Code:
$ date --date='@2147483647'
Mon Jan 18 19:14:07 PST 2038
$ date --date='@2147483648'
Mon Jan 18 19:14:08 PST 2038
On OpenBSD:
Code:
$ date -r 2147483647
Mon Jan 18 19:14:07 PST 2038
$ date -r 2147483648 
Fri Dec 13 12:45:52 PST 1901
I"m not afraid of December 20, 2012 but just thinking about the day after January 18, 2038 gives me frightful
paraskevidekatriaphobia...

Last edited by comet--berkeley; 4th April 2012 at 04:23 AM. Reason: paraskevidekatriaphobia
Reply With Quote