Listen "#105 The 2038 Problem"
Episode Synopsis
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
Episode 45: Two Software Disasters
Episode 32: What is Unix?
Episode 3: What is a Byte?
Follow us on Twitter @KopecExplains.
Theme “Place on Fire” Copyright 2019 Creo, CC BY 4.0
Find out more at http://kopec.live
Show Notes
Episode 45: Two Software Disasters
Episode 32: What is Unix?
Episode 3: What is a Byte?
Follow us on Twitter @KopecExplains.
Theme “Place on Fire” Copyright 2019 Creo, CC BY 4.0
Find out more at http://kopec.live
More episodes of the podcast Kopec Explains Software
#135 Hacking the Classic Mac OS
20/03/2025
#134 The CrowdStrike Incident
12/08/2024
#133 Ad Blockers
21/07/2024
#132 What is Machine Learning?
02/06/2024
#131 Abandonware
19/04/2024
#130 Grace Hopper
18/03/2024
#129 BASIC
01/02/2024
#128 Copyright & Machine Learning Models
11/12/2023
#127 The Google Search Antitrust Lawsuit
13/11/2023
#126 How Does Google Make Money?
30/10/2023