Re: [time-nuts] A milestone approaches

2017-07-14 Thread Tom Van Baak
> OpenVMS also has something to say about time:

http://h41379.www4.hpe.com/openvms/products/year-2000/leap.html

... one of the most quoted classic bug report replies of all time.

/tvb

___
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.


[time-nuts] A milestone approaches

2017-07-14 Thread Mark Sims
Lady Heather has the date marked on her calendar  (with a note to wear a clean 
pocket protector).  

Speaking of eventful dates...  Trimble Thunderbolt dates rollover on 30 Jul 
2017.Heather's automatic date rollover compensation should fix the date 
after 15 seconds... hopefully
___
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.


Re: [time-nuts] A milestone approaches

2017-07-14 Thread Peter Vince
Good morning all - I hope you enjoyed the Unix 1.5 billion parties?  An
ex-colleague who used to work on VAX computers has just sent me this
related message:


OpenVMS also has something to say about time:

.
OpenVMS represents system time as the 64-bit number of 100ns intervals
 since midnight preceding November 17, 1858, which is the start of Modified
Julian Day numbering.
.
.
This 100 nanosecond granularity implemented within OpenVMS and the 63-bit
absolute time representation (the sign bit indicates *absolute time* when
clear and *relative time* when set) should allow OpenVMS trouble-free time
computations up to 31-JUL-31086 02:48:05.47. At this instant, all clocks
and time-keeping operations in OpenVMS will suddenly fail, since the
counter will overflow and start from zero again.
.
.
You may have to reset your oven timer after this point . . .


 Peter
___
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.


[time-nuts] A milestone approaches

2017-07-13 Thread Mark Sims
I told Heather to display the time as Unix seconds and to do a screen dump at 
the Magic Moment...  which was duly captured for posterity...   Some poor souls 
are easily amused by such things...  

OK, there was a 1 millisecond delay for the dump to trigger.  Receiver was a 
Thunderbolt.___
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.

Re: [time-nuts] A milestone approaches

2017-07-13 Thread Bob kb8tq
Hi

I’ll put that on my calendar right away :)

Yet another potential bug to check for in MJD code ….

Bob

> On Jul 13, 2017, at 1:51 PM, Peter Vince  wrote:
> 
> 2038 could be an "interesting" year - on the 22nd of April, the MJD hits
> 65535  (2^16-1) !
> 
> 
> On 12 July 2017 at 13:19, Tom Van Baak  wrote:
> 
>> Thanks for the notice. Add these to your list:
>> 
> 
> 
> 
>> 2147483648 0x8000 Tue Jan 19 03:14:08 2038 GMT (you survived)
>> 
>> While we're at it, we have a rare T&F MJD event coming in 2023:
>> 
>> 1968-05-24 00:00:00 UTC (DOY = 145, Fri) = JD 244.5 = MJD 4.0
>> 1995-10-10 00:00:00 UTC (DOY = 283, Tue) = JD 245.5 = MJD 5.0
>> 2023-02-25 00:00:00 UTC (DOY =  56, Sat) = JD 246.5 = MJD 6.0
>> 
>> /tvb
>> 
>> 
> ___
> time-nuts mailing list -- time-nuts@febo.com
> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.

___
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.


Re: [time-nuts] A milestone approaches

2017-07-13 Thread Peter Vince
2038 could be an "interesting" year - on the 22nd of April, the MJD hits
65535  (2^16-1) !


On 12 July 2017 at 13:19, Tom Van Baak  wrote:

> Thanks for the notice. Add these to your list:
> 



> 2147483648 0x8000 Tue Jan 19 03:14:08 2038 GMT (you survived)
>
> While we're at it, we have a rare T&F MJD event coming in 2023:
>
> 1968-05-24 00:00:00 UTC (DOY = 145, Fri) = JD 244.5 = MJD 4.0
> 1995-10-10 00:00:00 UTC (DOY = 283, Tue) = JD 245.5 = MJD 5.0
> 2023-02-25 00:00:00 UTC (DOY =  56, Sat) = JD 246.5 = MJD 6.0
>
> /tvb
>
>
___
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.


Re: [time-nuts] A milestone approaches

2017-07-12 Thread Bill Riches
Hi Tom

I passed this along to two of my old time computer gurus - I am sure they will 
want to celebrate!!

73,

Bill, WA2DVU
Cape May

-Original Message-
From: time-nuts [mailto:time-nuts-boun...@febo.com] On Behalf Of Tom Van Baak
Sent: Wednesday, July 12, 2017 8:19 AM
To: Discussion of precise time and frequency measurement 
Subject: Re: [time-nuts] A milestone approaches

Hi Bill,

> Got this from a friend whose MN license plate is UNIX.

Join the club! There's ~50 of us in the US: http://leapsecond.com/pages/unix/


> At that instant, billions of Linux and Unix computers and devices

Plus embedded devices, such as Arduino, where 31-bit time_t C libraries are 
also used...


> return time() == 15.  It will not be until 2033 when that number 
> reaches 2 Billion.

Thanks for the notice. Add these to your list:

1414213562 0x544b2fba Sat Oct 25 06:06:02 2014 GMT (sqrt 2)
1415926535 0x54655307 Fri Nov 14 00:55:35 2014 GMT (pi)
1420405752 0x54a9abf8 Sun Jan 04 21:09:12 2015 GMT (H-maser Hz)
15 0x59682f00 Fri Jul 14 03:40:00 2017 GMT (1.5 billion)
1616161616 0x6054ab50 Fri Mar 19 13:46:56 2021 GMT (pretty in dec)
1616928864 0x60606060 Sun Mar 28 10:54:24 2021 GMT (pretty in hex)
1717171717 0x6659f605 Fri May 31 17:08:37 2024 GMT (dec looking like oct)
1886417008 0x70707070 Thu Oct 11 13:43:28 2029 GMT (pretty in hex)
1985229328 0x76543210 Sun Nov 28 04:35:28 2032 GMT (hex digit countdown)
20 0x77359400 Wed May 18 04:33:20 2033 GMT (2 billion)
2004318071 0x Thu Jul 07 04:01:11 2033 GMT (pretty in hex)
2147483647 0x7fff Tue Jan 19 03:14:07 2038 GMT (end of time)
2147483648 0x8000 Tue Jan 19 03:14:08 2038 GMT (you survived)

While we're at it, we have a rare T&F MJD event coming in 2023:

1968-05-24 00:00:00 UTC (DOY = 145, Fri) = JD 244.5 = MJD 4.0
1995-10-10 00:00:00 UTC (DOY = 283, Tue) = JD 245.5 = MJD 5.0
2023-02-25 00:00:00 UTC (DOY =  56, Sat) = JD 246.5 = MJD 6.0

/tvb

___
time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to 
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.

___
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.


Re: [time-nuts] A milestone approaches

2017-07-12 Thread William H. Fite
My spouse's license plate is BEFUNGE.


On Wednesday, July 12, 2017, Tom Van Baak  wrote:

> Hi Bill,
>
> > Got this from a friend whose MN license plate is UNIX.
>
> Join the club! There's ~50 of us in the US: http://leapsecond.com/pages/
> unix/
>
>
> > At that instant, billions of Linux and Unix computers and devices
>
> Plus embedded devices, such as Arduino, where 31-bit time_t C libraries
> are also used...
>
>
> > return time() == 15.  It will not be until 2033 when that number
> reaches 2 Billion.
>
> Thanks for the notice. Add these to your list:
>
> 1414213562 0x544b2fba Sat Oct 25 06:06:02 2014 GMT (sqrt 2)
> 1415926535 0x54655307 Fri Nov 14 00:55:35 2014 GMT (pi)
> 1420405752 0x54a9abf8 Sun Jan 04 21:09:12 2015 GMT (H-maser Hz)
> 15 0x59682f00 Fri Jul 14 03:40:00 2017 GMT (1.5 billion)
> 1616161616 0x6054ab50 Fri Mar 19 13:46:56 2021 GMT (pretty in dec)
> 1616928864 0x60606060 Sun Mar 28 10:54:24 2021 GMT (pretty in hex)
> 1717171717 0x6659f605 Fri May 31 17:08:37 2024 GMT (dec looking like oct)
> 1886417008 0x70707070 Thu Oct 11 13:43:28 2029 GMT (pretty in hex)
> 1985229328 0x76543210 Sun Nov 28 04:35:28 2032 GMT (hex digit countdown)
> 20 0x77359400 Wed May 18 04:33:20 2033 GMT (2 billion)
> 2004318071 0x Thu Jul 07 04:01:11 2033 GMT (pretty in hex)
> 2147483647 0x7fff Tue Jan 19 03:14:07 2038 GMT (end of time)
> 2147483648 0x8000 Tue Jan 19 03:14:08 2038 GMT (you survived)
>
> While we're at it, we have a rare T&F MJD event coming in 2023:
>
> 1968-05-24 00:00:00 UTC (DOY = 145, Fri) = JD 244.5 = MJD 4.0
> 1995-10-10 00:00:00 UTC (DOY = 283, Tue) = JD 245.5 = MJD 5.0
> 2023-02-25 00:00:00 UTC (DOY =  56, Sat) = JD 246.5 = MJD 6.0
>
> /tvb
>
> ___
> time-nuts mailing list -- time-nuts@febo.com 
> To unsubscribe, go to https://www.febo.com/cgi-bin/
> mailman/listinfo/time-nuts
> and follow the instructions there.
>


-- 
William H Fite, PhD
Independent Consultant
Statistical Analysis & Research Methods
___
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.


Re: [time-nuts] A milestone approaches

2017-07-12 Thread Tom Van Baak
Hi Bill,

> Got this from a friend whose MN license plate is UNIX.

Join the club! There's ~50 of us in the US: http://leapsecond.com/pages/unix/


> At that instant, billions of Linux and Unix computers and devices

Plus embedded devices, such as Arduino, where 31-bit time_t C libraries are 
also used...


> return time() == 15.  It will not be until 2033 when that number 
> reaches 2 Billion.

Thanks for the notice. Add these to your list:

1414213562 0x544b2fba Sat Oct 25 06:06:02 2014 GMT (sqrt 2)
1415926535 0x54655307 Fri Nov 14 00:55:35 2014 GMT (pi)
1420405752 0x54a9abf8 Sun Jan 04 21:09:12 2015 GMT (H-maser Hz)
15 0x59682f00 Fri Jul 14 03:40:00 2017 GMT (1.5 billion)
1616161616 0x6054ab50 Fri Mar 19 13:46:56 2021 GMT (pretty in dec)
1616928864 0x60606060 Sun Mar 28 10:54:24 2021 GMT (pretty in hex)
1717171717 0x6659f605 Fri May 31 17:08:37 2024 GMT (dec looking like oct)
1886417008 0x70707070 Thu Oct 11 13:43:28 2029 GMT (pretty in hex)
1985229328 0x76543210 Sun Nov 28 04:35:28 2032 GMT (hex digit countdown)
20 0x77359400 Wed May 18 04:33:20 2033 GMT (2 billion)
2004318071 0x Thu Jul 07 04:01:11 2033 GMT (pretty in hex)
2147483647 0x7fff Tue Jan 19 03:14:07 2038 GMT (end of time)
2147483648 0x8000 Tue Jan 19 03:14:08 2038 GMT (you survived)

While we're at it, we have a rare T&F MJD event coming in 2023:

1968-05-24 00:00:00 UTC (DOY = 145, Fri) = JD 244.5 = MJD 4.0
1995-10-10 00:00:00 UTC (DOY = 283, Tue) = JD 245.5 = MJD 5.0
2023-02-25 00:00:00 UTC (DOY =  56, Sat) = JD 246.5 = MJD 6.0

/tvb

___
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.


Re: [time-nuts] A milestone approaches

2017-07-11 Thread Poul-Henning Kamp

In message , "Bill Hawkins" writes:

>On Thursday night, 21:40 PM CST, it will be exactly 1.5 billion seconds
>since Jan 1, 1970 UT, the Unix EPOCH.

We threw a big "uptime(1)" party for the entire UNIX ecosystem
here in Denmark back when 1e9 seconds rolled around :-)

-- 
Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer   | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.


[time-nuts] A milestone approaches

2017-07-11 Thread Bill Hawkins
Got this from a friend whose MN license plate is UNIX.

Begin copy of note

I'm curious if your friends on the time wizards mailing list have
noticed that an important moment in computer history approaches.

On Thursday night, 21:40 PM CST, it will be exactly 1.5 billion seconds
since Jan 1, 1970 UT, the Unix EPOCH.  At that instant, billions of
Linux and Unix computers and devices, everywhere on the planet, will all
return time() == 15.  It will not be until 2033 when that number
reaches 2 Billion.  The Thursday date is computed as follows:

% cat >epoch.c
#include 
#include 
#include 

int main(int argc, char **argv) {
const time_t gsec = 1.5e9;
struct tm thursday = *localtime(&gsec);
char buf[100];

strftime(buf, sizeof(buf), "%m/%d/%y %H:%M:%S", &thursday);
printf("Epoch + 1.5B seconds = %s\n", buf);
return 0;
}
% gcc -Wall epoch.c
% ./a.out
Epoch + 1.5B seconds = 07/13/17 21:40:00
%

And if they haven't noticed, it might be a good time to point it out.

End copy of note

Some of us are impressed by long strings of zeros, so here I am,
pointing it out.

Bill Hawkins

___
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.