![\"Unix](\"\/wp-content\/uploads\/2020\/01\/1b3a3bdeb0400f3b34d5cd6964a48010.jpg\")
<\/p>\nThe year 2020 is significant for Unix: at the very beginning of the year, the original operating system turned 50 years old. Unix time, also known as \"epoch time,\" is the number of seconds that have elapsed since January 1, 1970. But what concerns kernel developers regarding the half-century anniversary of Unix?<\/p>\n
<\/p>\n
Although some of the early Unix developments predate the official start of its \"epoch,\" January 1, 1970, remains the zero point in time for POSIX. Therefore, as of January 1, 2020, the platform officially turned exactly 50 years old.<\/p>\n
Time <\/strong>Unix versus human time<\/strong><\/p>\n From a human perspective, 50 years is a long period. From the Unix time perspective, there is nothing special about 50 years; even 43 years would be equally significant. Unix systems (including Linux) store date and time values as the number of seconds that have passed since 1970-01-01 00:00:00 UTC, recorded in 32 bits. To determine how many seconds have elapsed since that time, and thus the current Unix time value, you can execute the command:<\/p>\n $ date +%s<\/p>\n 1576883876<\/p>\n The %s argument after the date command specifies the display of the current date and time as the number of seconds since the beginning of 1970-01-01.<\/p>\n What is the maximum date that Unix systems can store? <\/strong>Unix?<\/strong><\/p>\n To understand how much time a Unix system can accommodate, you need to assess the capacity of a 32-bit field. This can be calculated as follows:<\/p>\n $ echo '2^32' | bc<\/p>\n 4294967296<\/p>\n However, since Unix accommodates negative numbers, one bit is reserved for the sign, thus reducing the time value to:<\/p>\n $ echo '2^31' | bc<\/p>\n 2147483648<\/p>\n And since Unix numbering starts from 0, this means we have 2,147,483,648 values, but the largest one is 2,147,483,647 \u2014 Unix date and time values cannot exceed this number. Just as the odometer in a car cannot show more than 999,999 kilometers \u2014 add 1, and the value resets.<\/p>\n How long is a year in seconds?<\/strong><\/p>\n The number of seconds in a year can be calculated as follows:<\/p>\n $ expr 24 * 60 * 60 * 365<\/p>\n 31536000<\/p>\n In a leap year, an additional day is added:<\/p>\n $ expr 24 * 60 * 60 * 366<\/p>\n 31622400<\/p>\n How does Unix display its 50th birthday?<\/strong><\/p>\n On January 1, 2020, at 12:00 AM, the time will be 1577836800. The calculation is somewhat complicated because leap years must be taken into account. Since the Unix epoch, there have been 12 such years, starting from 1972 and ending in 2016. This means that 38 ordinary years have passed.<\/p>\n Here is how the expr command looks to count seconds over the past 50 years:<\/p>\n $ expr 24 * 60 * 60 * 365 * 38 + 24 * 60 * 60 * 366 * 12<\/p>\n 1577836800<\/p>\n Or like this, taking into account previous calculations:<\/p>\n $ expr 31536000 * 38 + 31622400 * 12<\/p>\n 1577836800<\/p>\n This method of recording time made Unix systems immune to the Y2K problem, which worried people at the end of 1999 that the transition to the year 2000 might damage computer systems. The difficulties turned out to be much less than expected. In fact, only applications that recorded years in two-digit format encountered date rollovers. Many developers did extra work to ensure that their applications would not be affected by the Y2K problem.<\/p>\n When will time <\/strong>Unix face problems?<\/strong><\/p>\n Similar difficulties are expected for Unix systems no earlier than 2038, when dates stored in the format described above will exceed 32-bit space. There are still 18 years left, but kernel developers are already working to avoid the upcoming crashes.<\/p>\n The year 2038 problem is sometimes referred to as the Y2K38 issue. If it is not resolved by Tuesday, January 19, 2038, after this date, systems may think it is the year 1901. One way to address this problem is to shift to a 64-bit representation of date and time information. Some believe this will be much more complex than it may seem.<\/p>\n![\"Unix](\"\/wp-content\/uploads\/2020\/01\/aba69e769edb987923b060b6e32f9a00.jpg\")
<\/p>\n![\"Unix](\"\/wp-content\/uploads\/2020\/01\/a720be1bfca58df09540785bf66f556d.jpg\")
<\/p>\n