stupid math
On Tue, Oct 18, 2016 at 6:13 PM, Paul Stewart <p...@paulstewart.org> wrote:
> Yup so true …
>
> On Oct 18, 2016, at 7:06 PM, George Skorup <geo...@cbcast.com> wrote:
>
> Jan 19 2038 is yet another 32 bit problem.
>
> On 10/18/2016 3:35 PM, Paul Stewart wrote:
>
> Yeah but if it’s like IPv6 people will wait until it’s too late ;)
>
> Sorry - couldn’t resist throwing that in here ….
>
> On Oct 18, 2016, at 4:32 PM, Bill Prince <part15...@gmail.com> wrote:
>
> Once 2036, or even 2035 shows up, set a flag somewhere that we are
> preparing for rollover. Heck, do it now. Mark 1900 as "history" and 2036 as
> "future". When 2036-02-07 comes around, mark that one as history as well.
>
> Unfortunately, legacy programs won't be able to deal with it. Perhaps it's
> a good thing that we have almost 20 years to prepare for it.
>
>
> bp
> <part15sbs{at}gmail{dot}com>
>
>
> On 10/18/2016 1:26 PM, Chuck McCown wrote:
>
> Yep, this could be like Y2K. Once the clock rolls, I don’t think NTP yet
> has a field showing epoch number so how do you differentiate between 1900
> and 2036?
>
> *From:* Paul Stewart
> *Sent:* Tuesday, October 18, 2016 2:23 PM
> *To:* af@afmug.com
> *Subject:* Re: [AFMUG] OT DHCP update
>
> Clock rolls over …
>
>
>
> On Oct 18, 2016, at 4:13 PM, Chuck McCown <ch...@wbmfg.com> wrote:
>
> A few weeks ago I was requesting help in thinking through some DHCP lease
> issues. Turns out, we think, that there were some Calix system clock
> fruitiness.
>
> Anyone care to guess what is magic about February 7, 2036?
>
>
>
>
>
>
>
>
--
If you only see yourself as part of the team but you don't see your team as
part of yourself you have already failed as part of the team.
