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
---------- Forwarded message --------- From: Ted Pomeroy <ted.pome@gmail.com> Date: Wed, Feb 28, 2024 at 9:04 AM Subject: Time in a bottle? To: NMGLUG.org mailing list <nmglug@nmglug.org> 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
Should be there On 2/28/24 9:04 AM, Ted Pomeroy wrote:
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
_______________________________________________ nmglug mailing list nmglug@lists.nmglug.org http://lists.nmglug.org/listinfo.cgi/nmglug-nmglug.org
Glug Thursday occurs on Feb 29 only once in 56 years. Maybe we should celebrate this historic occasion. On 2/29/24 10:06 AM, Jonathan Haack wrote:
Should be there
On 2/28/24 9:04 AM, Ted Pomeroy wrote:
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
_______________________________________________ nmglug mailing list nmglug@lists.nmglug.org http://lists.nmglug.org/listinfo.cgi/nmglug-nmglug.org
_______________________________________________ nmglug mailing list nmglug@lists.nmglug.org http://lists.nmglug.org/listinfo.cgi/nmglug-nmglug.org
I’m here and no one else is I secured the best spot but some kids tried to jack it so please come soon Kindly, Jonathan Haack Math/CS Teacher, DSA/SFCC Director, Haack’s Networking
On Feb 29, 2024, at 10:16 AM, Geoff Chesshire <geoff@newmexico.com> wrote:
Glug Thursday occurs on Feb 29 only once in 56 years. Maybe we should celebrate this historic occasion.
On 2/29/24 10:06 AM, Jonathan Haack wrote: Should be there
On 2/28/24 9:04 AM, Ted Pomeroy wrote: 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
_______________________________________________ nmglug mailing list nmglug@lists.nmglug.org http://lists.nmglug.org/listinfo.cgi/nmglug-nmglug.org
nmglug mailing list nmglug@lists.nmglug.org http://lists.nmglug.org/listinfo.cgi/nmglug-nmglug.org
nmglug mailing list nmglug@lists.nmglug.org http://lists.nmglug.org/listinfo.cgi/nmglug-nmglug.org
participants (3)
-
Geoff Chesshire -
Jonathan Haack -
Ted Pomeroy