Linux 5.10 Solved Year 2038 Problem by 2486
Although units of time are simple 'things' for us to perceive, computers process data as 'bits'.
Although units of time are simple 'things' for us to perceive, computers process data as 'bits'.
Although time units are simple 'things' for us to perceive, since computers process data as 'bits', the operation performed by computers may not be the same as what they show us. For example, “My brother was born in 95” When you say, the other person may understand that your brother was born in 1995, but for the computer, your brother was really born in 1995 and is 1925 years old.
The way computers keep time, Problem of the Year 2038 A software bug known as will cause some 32-bit systems using POSIX time notation to crash in 2038, and Linux 5.10 has managed to fix this problem by 2486.
The operation of the meter that caused the Year 2038 Problem
Before moving on to the solution of Linux, we need to explain the Year 2038 Problem a little; In 32-bit UNIX and derivative systems, which have kept time in seconds since January 1, 1970, at 03:14:07 on Tuesday, January 19, 2038, the counter will return to the point where it started and the system date will show December 13, 1901 20:45:52. The simplest way to eliminate the error in question was seen as switching to 64-bit systems, which is exactly the solution found by Linux.
According to the statement made by Phoronix, “Coming with Linux 5.10Large Timestamp” rearranges timestamps and inode encoding functions to use a 64-bit nanosecond counter instead of the 32-bit time counter that introduced the Year 2038 Problem. The 64-bit counter can be used between December 1901 and July 2486, as opposed to the 32-bit time counter that can be used between December 1901 and January 2038.
Every business is unique. Let’s explore how we can tailor these ideas to your own digital project.
