Fwd: Time in a bottle?

--===============0474581777549368836==
Content-Type: multipart/alternative; boundary="00000000000000b9ce061287ca14"

--00000000000000b9ce061287ca14
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

---------- Forwarded message ---------
From: Ted Pomeroy <[email protected]>
Date: Wed, Feb 28, 2024 at 9:04=E2=80=AFAM
Subject: Time in a bottle?
To: NMGLUG.org mailing list <[email protected]>


NMGLUGers,  Just caught up with this interesting issue on the brief history
of time: debian-takes-proactive-steps-to-address-y2k38
<https://linuxiac.com/debian-takes-proactive-steps-to-address-y2k38/>
It seems as if January 1, 1970 will cause a counting error in 2038. An
interesting thought, as many of us deal with time and counting and who can
forget the Windows issue on Y2K? It was a fun night, New Year's Eve
1999-2000. I never had so many supervisors attending my midnight hours as
on that night. A real "Night Manager" only has the power to declare when a
property moves to the next day. (It's based on when all the bills are
ready.) Luckily there was no system failure back then.
Looks like people won't have to worry in 2038, but you never know.
See you at Glug this week? There may be other reasons some of us are
"marking time." Thank you, Ted P

--00000000000000b9ce061287ca14
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:large"><br=
></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr"=
>---------- Forwarded message ---------<br>From: <b class=3D"gmail_senderna=
me" dir=3D"auto">Ted Pomeroy</b> <span dir=3D"auto">&lt;<a href=3D"mailto:t=
[email protected]">[email protected]</a>&gt;</span><br>Date: Wed, Feb 28, =
2024 at 9:04=E2=80=AFAM<br>Subject: Time in a bottle?<br>To: NMGLUG.org mai=
ling list &lt;<a href=3D"mailto:[email protected]">[email protected]</a>&gt=
;<br></div><br><br><div dir=3D"ltr"><div style=3D"font-size:large">NMGLUGer=
s,=C2=A0 Just caught up with this interesting issue on the brief history of=
 time: <a href=3D"https://linuxiac.com/debian-takes-proactive-steps-to-addr=
ess-y2k38/" target=3D"_blank">debian-takes-proactive-steps-to-address-y2k38=
</a></div><div style=3D"font-size:large">It seems as if January 1, 1970 wil=
l cause a counting error in 2038. An interesting thought, as many of us dea=
l with time and counting and who can forget the Windows issue on Y2K? It wa=
s a fun night, New Year&#39;s Eve 1999-2000. I never had so many supervisor=
s attending my midnight hours as on that night. A real &quot;Night Manager&=
quot; only has the power to declare when a property moves to the next day. =
(It&#39;s based on when all the bills are ready.) Luckily there was no syst=
em failure back then.</div><div style=3D"font-size:large">Looks like people=
 won&#39;t have to worry in 2038, but you never know.</div><div style=3D"fo=
nt-size:large">See you at Glug this week? There may be other reasons some o=
f us are &quot;marking time.&quot; Thank you, Ted P<br></div></div>
</div></div>

--00000000000000b9ce061287ca14--

--===============0474581777549368836==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
nmglug mailing list
[email protected]
http://lists.nmglug.org/listinfo.cgi/nmglug-nmglug.org

--===============0474581777549368836==--