Artwork

Content provided by David Kopec, Rebecca Kopec, David Kopec, and Rebecca Kopec. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by David Kopec, Rebecca Kopec, David Kopec, and Rebecca Kopec or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.
Player FM - Podcast App
Go offline with the Player FM app!

#105 The 2038 Problem

8:44
 
Share
 

Manage episode 346991614 series 2709740
Content provided by David Kopec, Rebecca Kopec, David Kopec, and Rebecca Kopec. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by David Kopec, Rebecca Kopec, David Kopec, and Rebecca Kopec or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

On January 19, 2038, certain non-updated legacy systems that use Unix time will roll their dates around to December 13, 1901. In Unix, time is recorded as the number of seconds since January 1, 1970. Because a signed 32-bit integer is used to record this value on many legacy systems, they will run out of seconds in 2038 (a signed 32-bit integer can record numbers up to 2,147,483,647, and that's the number of seconds between January 1 1970 at 12:00:00 AM and January 19, 2038 at 3:14:07 AM). Many legacy operating systems, programming languages, and databases that use signed 32-bit integers to record Unix time are still in use in non-updated embedded systems. In this episode we explain the problem and its potential implications.

Show Notes

Follow us on Twitter @KopecExplains.

Theme “Place on Fire” Copyright 2019 Creo, CC BY 4.0

Find out more at http://kopec.live

  continue reading

139 episodes

Artwork

#105 The 2038 Problem

Kopec Explains Software

11 subscribers

published

iconShare
 
Manage episode 346991614 series 2709740
Content provided by David Kopec, Rebecca Kopec, David Kopec, and Rebecca Kopec. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by David Kopec, Rebecca Kopec, David Kopec, and Rebecca Kopec or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

On January 19, 2038, certain non-updated legacy systems that use Unix time will roll their dates around to December 13, 1901. In Unix, time is recorded as the number of seconds since January 1, 1970. Because a signed 32-bit integer is used to record this value on many legacy systems, they will run out of seconds in 2038 (a signed 32-bit integer can record numbers up to 2,147,483,647, and that's the number of seconds between January 1 1970 at 12:00:00 AM and January 19, 2038 at 3:14:07 AM). Many legacy operating systems, programming languages, and databases that use signed 32-bit integers to record Unix time are still in use in non-updated embedded systems. In this episode we explain the problem and its potential implications.

Show Notes

Follow us on Twitter @KopecExplains.

Theme “Place on Fire” Copyright 2019 Creo, CC BY 4.0

Find out more at http://kopec.live

  continue reading

139 episodes

Alle episoder

×
 
Loading …

Welcome to Player FM!

Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.

 

Quick Reference Guide