Jul 15, 2020 · The start date for computer calendars is January 1, 1970, and the idea is they *theoretically* count down in seconds to infinity. However, 32-bit processors are only physically capable of counting up to 2,147,483,647. So the idea is that, at 03:14:07 UTC On Jan 19, 2038, these processor will reach max capacity. No Mercy: The Year 2038 Problem · in UNIX time, two billion seconds after Jan 1, 1970 is Jan 19, 2038 · in UNIX time, two billion seconds before Jan 1, 1970 is ....18 years from now, when the clock strikes 14 minutes and seven seconds past three on the morning of Tuesday 19 January 2038 UTC, a bug known as the Year 2038 Problem is expected to occur. Any computer, program, server or embedded system that store time using 32-bit signed integer will go haywire unless they are upgraded in advance.The Year 2038 problem with Unix time has wider ranges of repercussions than a phone that will obsolete in 2038. Considering that most software and the libraries they're built on rely on unixtime mean applications, scripts, etc., will need to be rewritten. Then there's issues with embedded systems where such a software fix might not even …Sixty-eight years after 1970, Zimmie said, is 2038. Anyone who deals with UNIX time should recognize the year 2038, which has its own website warning of troubles ahead. "The latest time which can ...Jan 23, 2019 · “The Year 2038 problem is where the Unix time can no longer be stored in a signed 32-bit integer and thus after 19 January 2038 will begin wrapping around as a negative number for representing the number of seconds since 1 January 1970.” Insight: Linux Kernel 5.6 To Fix the Year 2038 Issue Common problems associated with the Honda Passport include transmission failure and the frame rotting completely through in the back. The most-common problems with the vehicle vary...8. Time conversion routines would "simply" have to use 2038-01-19:03:14:07Z as the base for Unix Epoch time if the timestamp is below a certain value. I.e. if your system goes productive in 2010-01-01, you can assume that no timestamp, which is not overflown, is below 1262300400 (which is unix epoch time for that date).The Year 2038 problem is an issue for computing and data storage situations in which time values are stored or calculated as a signed 32bit integer, and this number is interpreted as the number of seconds since 000000 UTC on 1 January 1970 (the epoch).Jan 23, 2019 · “The Year 2038 problem is where the Unix time can no longer be stored in a signed 32-bit integer and thus after 19 January 2038 will begin wrapping around as a negative number for representing the number of seconds since 1 January 1970.” Insight: Linux Kernel 5.6 To Fix the Year 2038 Issue A new ‘millenium bug’ could hit computers in January 2038, wipe out computers and programs that rely on outdated internal clocks.The Year 2038 problem affect...Because of the way time is represented in Linux, a signed 32-bit number can't support times beyond January 19, 2038 after 3:14:07 UTC. This Year 2038 (Y2038 …On January 19, 2038 03:14:08 GMT all computers that still use 32 bit Unix Time will overflow. This is known as the "Year 2038 problem". Some believe this will be a more significant problem than the "Year 2000 problem". The fix for the Year 2038 problem is to store Unix Time in a 64 bit integer.The Year 2038 problem with Unix time has wider ranges of repercussions than a phone that will obsolete in 2038. Considering that most software and the libraries they're built on rely on unixtime mean applications, scripts, etc., will need to be rewritten. Then there's issues with embedded systems where such a software fix might not even …In the year 2038... Imagine, it is the 19th of January 2038 and as you get up, you find that your mariadb does not start, your python2 programs stop compiling, memcached is misbehaving, your backups have strange timestamps and rsync behaves weird . And all of this, because at some point, UNIX devs declared the time_t type to be a signed 32-bit ...To test, compile the above code as ftime_check and run the following from an admin command prompt (note your numbers will vary due to the time of day on your clock): date 1/18/2038 && ftime_check. 2147474668. date 1/20/2038 && ftime_check. -2147319812. For reference, here is the (expected) output as seen under vc120: date 1/18/2038 && ftime_check.“The Year 2038 problem is where the Unix time can no longer be stored in a signed 32-bit integer and thus after 19 January 2038 will begin wrapping around as a negative number for representing the number of seconds since 1 January 1970.” Insight: Linux Kernel 5.6 To Fix the Year 2038 Issue.This now allows XFS to run well past the Year 2038 problem (where storing the time since 1970 in seconds will no longer fit in a signed 32-bit integer and thus wraparound) to now the Year 2486. Making a new XFS file-system with bigtime enabled allows a timestamp range from December 1901 to July 2486 rather than December 1901 to January 2038.ปัญหาปี ค.ศ. 2038 (อังกฤษ: Year 2038 problem) ... สากลเชิงพิกัด ในวันอังคารที่ 19 มกราคม ค.ศ. 2038 (พ.ศ. 2581) ...Feb 17, 2024 · The year 2038 problem (also known as Y2038, Y2K38, Y2K38 superbug or the Epochalypse) is a time computing problem that leaves some computer systems unable to represent times after 03:14:07 UTC on 19 January 2038. What exactly is the year 2038 problem The problem of the year 2038 is due to the maximum bit capacity of 32-bit systems . They store memory and execute their processes using 32 binary digits, which can be represented by a 1 or a 0, allowing a total of 4,294,967,296 possible combinations.In this video I discuss the Y2K38 bug, also known as the end of Unix time and the year 2038 problem, software that is currently affected by the bug, and what...Jan 23, 2019 · “The Year 2038 problem is where the Unix time can no longer be stored in a signed 32-bit integer and thus after 19 January 2038 will begin wrapping around as a negative number for representing the number of seconds since 1 January 1970.” Insight: Linux Kernel 5.6 To Fix the Year 2038 Issue Common problems with the Kia Optima include steering issues and engine failure, as of 2015. The 2006 and 2007 year Optima have a large number of engine failure issues, while the 20...This time will be Friday, December 1901 and is called the wrap-around date. Applications written in C in many operating system will also be affected as the POSIX presentation of time is widely used there. The animation below visualizes actual scenario in an easier manner. This bug is often denoted as "Y2038", …May 21, 2008 · If you use a Unix- or Linux-based system, there's one more date-related bug you'll need to worry about -- in the year 2038. All 32-bit Unix/Linux-based systems store the system clock time internally as the number of seconds since the Epoch, or 00:00:00 on January 1, 1970. This internal data type, time_t, is in most cases a 32-bit (4-byte ... Jan 26, 2023 · In this video I discuss the Y2K38 bug, also known as the end of Unix time and the year 2038 problem, software that is currently affected by the bug, and what... The Year 2000 problem, also known as the Y2K problem, the Millennium bug, the Y2K bug, or Y2K, is a class of computer bugs related to the formatting and storage of calendar data for dates beginning in the year 2000. New!!: Year 2038 problem and Year 2000 problem · See more ».A full investigation of the Ariane incident found that a process left over from software in the previous generation of rockets, Ariane 4, had captured an … The Year 2038 problem (also known as Y2038, Y2K38, Y2K38 superbug, or the Epochalypse) is a time formatting bug in computer systems with representing times after 03:14:07 UTC on 19 January 2038. The problem exists in systems which measure Unix time – the number of seconds elapsed since the Unix epoch (00:00:00 UTC on 1 January 1970) – and store it in a signed 32-bit integer. The data type ... The Year 2038 Problem, or Y2038, specifically affects software using a 32-bit integer system and has been theorised for years. 32-bit systems use four bytes, which mean they can use 4GB of memory ...This is called the Year 2038 Problem." Noting that the certificate authority signs its own certificate to be valid for a ten-year period, Zimmie concluded it ran into the 2038 problem when ...2038 will be a common year starting on Friday of the Gregorian calendar, the 2038th year of the Common Era (CE) and Anno Domini (AD) ... At January 19 2038 at 3:14:07 UTC, due to the year 2038 problem, Signed 32-bit unix time will overflow and revert to December 13 1901 at 20:45:52 UTC.The Year 2038 problem could cause disruptions in many aspects of life that rely on computer systems, including transportation, finance, and utilities. It could also cause problems with historical data, since many computer systems will no longer be able to accurately represent dates from before 2038.The Year 2038 problem is a date problem that occurs when computing dates beyond the year 2038 in 32-bit operating systems. It is caused by the overflow of the …The year 2038 problem, as it’s known, affects the C programming language, which was first released in 1972 but forms the bulk of tons of things we all still use every …the 2038 problem is orders of magnitude more severe than Y2K ever could have been. Neither of these statements is true. Y2K is the result of some programmers deciding to store year values in the range 00-99 while 2038 is the result of programmers deciding to store time values as 0-2.1 billion seconds after Jan. 1, …The 2038 problem is rooted in the classic UNIX time epoch. UNIX and UNIX-like operating systems, ... Unlike the Year 2000 problem, the 2038 and 2042 problems probably will not cause many difficulties before the wraps actually happen. That’s …Because of the way time is represented in Linux, a signed 32-bit number can't support times beyond January 19, 2038 after 3:14:07 UTC. This Year 2038 (Y2038 …Jan 12, 2024 · nsaspook. Joined Aug 27, 2009. 12,632. Jan 12, 2024. #7. You can't fix stupid. Sensible systems and codebases have used 64-bit integer to hold Unix time for a long time. The problem is utterly trivia, with known solutions and fixes in general use for a long time. If you're alive in 2038 and get bit by this on some ancient W95 era system still ... The Year 2038 problem. The Y2K problem threatened to bring down computers worldwide twenty-one years ago. In another seventeen years, the Year 2038 problem may do the same. R. D. Ward, Public domain, via Wikimedia Commons. Today I had a conversation with someone too young to remember the Y2K problem. Apart from …105. XFS timestamp tweak extends Unix time for a few centuries. Simon Sharwood, APAC Editor. Mon 19 Oct 2020 // 05:01 UTC. The forthcoming Linux 5.10 …Because of the way time is represented in Linux, a signed 32-bit number can't support times beyond January 19, 2038 after 3:14:07 UTC. This Year 2038 (Y2038 …Aug 31, 2011 · I have only seen a mere handful of operating systems that appear to be unaffected by the year 2038 bug so far. For example, the output of this script on Debian GNU/Linux (kernel 2.4.22): # ./2038.pl. Tue Jan 19 03:14:01 2038. Tue Jan 19 03:14:02 2038. Tue Jan 19 03:14:03 2038. Tue Jan 19 03:14:04 2038. Tue Jan 19 03:14:05 2038. Tue Jan 19 03:14 ... The Year 2038 bug is a predicted problem in some computer systems that might cause problems at that time. Contents. 1 What is the year 2038 bug? 2 What causes the Year 2038 Bug? 3 What operating systems, platforms, and applications are affected by it? 4 Detractors and critics;Linux was facing a big problem with keeping time . getty. A looming problem with Linux-based computers being unable to handle dates beyond the year 2038 appears to have been solved - or at least ...In today’s fast-paced world, stress and anxiety have become common problems for many people. While there are many ways to manage these issues, one method that has gained popularity...May 21, 2008 · If you use a Unix- or Linux-based system, there's one more date-related bug you'll need to worry about -- in the year 2038. All 32-bit Unix/Linux-based systems store the system clock time internally as the number of seconds since the Epoch, or 00:00:00 on January 1, 1970. This internal data type, time_t, is in most cases a 32-bit (4-byte ... At this point, most of the kernel work to avoid the year-2038 apocalypse has been completed. Said apocalypse could occur when time counted in seconds since 1970 overflows a 32-bit signed value (i.e. time_t). Work in the GNU C Library (glibc) and other C libraries is well underway as well. But the "fun" is just …Oct 19, 2020 ... XFS timestamp tweak extends Unix time for a few centuries ... The forthcoming Linux 5.10 looks like it will include further fixes for the Year ...A számítástechnikában a 2038-as év problémája néhány szoftver meghibásodását okozhatja 2038 -ban vagy akörül. A probléma a POSIX időábrázolást használó programokat érinti elsősorban, amely az időt az 1970. január 1. óta eltelt másodpercek számával ábrázolja. Ez az ábrázolási mód számít szabványnak a …ปัญหาปี ค.ศ. 2038 (อังกฤษ: Year 2038 problem) ... สากลเชิงพิกัด ในวันอังคารที่ 19 มกราคม ค.ศ. 2038 (พ.ศ. 2581) ...The problem with this kind of optimism is the same root problem >behind most of the Year 2000 concerns that plagued the software industry in >previous years: Legacy Code. Even if every PC in the year 2038 has a 64-bit >CPU, there will be a lot of older 32-bit programs running on them. > >The …Use 64-bit time_t on 32-bit architectures to avoid the 'year 2038 problem' when the existing 32-bit signed int rolls over (potentially setting time back to 1900). ... This is a problem for Debian as in a normal transition we expect that simply building against the new library will get you the new ABI. Something (glibc, dpkg, ...Any program written in C/C++ could suffer from the Year 2038 problem. This is because most C programs use a standard time library that provides a number of functions for converting, displaying and calculating time values (usually via a variable of type time_t which was a 32-bit signed integer on 32-bit systems, and 64-bit signed integer on 64-bit systems).We were upgrading to 10.4.12 recently and found an year 2038 issue in the integration tests. This is a regression from 10.4.0 which is known good. ... Report a problem; Powered by a free Atlassian Jira open source license for MariaDB Corporation Ab. Try Jira ...“The Year 2038 problem is where the Unix time can no longer be stored in a signed 32-bit integer and thus after 19 January 2038 will begin wrapping around as a negative number for representing the number of seconds since 1 January 1970.” Insight: Linux Kernel 5.6 To Fix the Year 2038 Issue.Mac2K: The Years’ 2038 and 2040 Problems WikiPost struck: 31 January 2023 Last edited: 31 January 2023 OVERVIEW For folks who use PowerPC and even Intel Macs (prior to, say, macOS 10.15 Catalina), it’s never too soon or too late to start planning for the impending, dual Y2K-like hard limits of the POSIX-based “Year 2038” — or …The fix is simple, just add another digit. For Y2K the problem was dates were represented with 2 digits. 75, 84, 99. It was presumed that the date was 1975, 1984, and 1999. Add 1 to 99 and you get 00 so the year is 1900. Well fuck. To fix this we now use 4 digits so we now store 1984, 2003, 2015.THE YEAR 2038 PROBLEM relates to representing time in many digital systems as the number of seconds passed since 00:00:00 UTC on 1 January 1970 and storing it as a signed 32-bit integer. Such implementations cannot encode times after 03:14:07 UTC on 19 January 2038. At that time, systems might crash and will be unable to restart when the time ...It's a problem that could impact a variety of computer systems in the year 2038, but why is this such a big deal? Unix Time Stamp: The Basics ... The Unix Time Stamp issue has been likened to the Y2K bug, which was a problem that occurred in the year 2000. The Y2K bug occurred because many computer systems used a two-digit …The start date for computer calendars is January 1, 1970, and the idea is they *theoretically* count down in seconds to infinity. However, 32-bit processors are only physically capable of counting up to 2,147,483,647. So the idea is that, at 03:14:07 UTC On Jan 19, 2038, these processor will reach max capacity.År 2038-problemet. År 2038-problemet refererer til et problem med at repræsentere tiden i mange computer systemer - specielt UNIX og UNIX lignende systemer. Tiden repræsenteres i disse systemer som antal sekunder efter 1. januar 1970. Hvis systemet bruger 32- bit til at repræsentere tiden som et heltal med fortegn, er det …The 64-bit timestamps used by NTP consist of a 32-bit part for seconds and a 32-bit part for fractional second, giving NTP a time scale that rolls over every 2 32 seconds (136 years) and a theoretical resolution of 2-32 seconds (233 picoseconds). NTP uses an epoch of 1 January 1900. The first rollover occurs in 2036, prior to the …image · Year 2038 date problem.png 999 × 323; 23 KB ; video · Year 2038 problem.gif 400 × 130; 59 KB ; point in time. 19 January 2038 ; has cause · integer&nbs...The problem with this kind of optimism is the same root problem >behind most of the Year 2000 concerns that plagued the software industry in >previous years: Legacy Code. Even if every PC in the year 2038 has a 64-bit >CPU, there will be a lot of older 32-bit programs running on them. > >The …"OpenBSD is one of the first operating systems to be safe from the “Year 2038 Problem”. 64-bit time was introduced in 2013, so you don’t have to worry about the Unix Epoch 32-bit issue." https: ... but Wine suffers from the Year 2038 bug and can't access directories with an access time past 2038 ...Year 2038 problem. Animation showing how the date would reset, represented as a signed 32-bit integer (at 03:14:08 UTC on 19 January 2038). The Year 2038 problem could …The Y2K bug was an issue when years were stored as ‘00’ instead of ‘2000’ whereas the year 2038 problem is the problem with the underlying structure not being big enough to hold the date after 2038. Will This Cause The End Of The World? Probably not. By the year 2038 most software should be updated to use at least a 64 bit ... The year 2038 problem (also known as Y2038, Y2K38, Y2K38 superbug or the Epochalypse) is a time computing problem that leaves some computer systems unable to represent times after 03:14:07 UTC on 19 January 2038. May 16, 2019 ... The problem is this: A 32 bit signed binary integer can count up to 2,147,483,647. That's a lot of seconds, but there are a lot of seconds in a ...Apr 7, 2009 · The year 2038 problem (also known as Unix Millennium bug, or Y2K38 by analogy to the Y2K problem, known as the millennium bug) may cause some computer software to fail before or in the year 2038. The problem affects all software and systems that store system time as a signed 32-bit integer, and interpret this number as the number of seconds ... The Year 2038 problem with Unix time has wider ranges of repercussions than a phone that will obsolete in 2038. Considering that most software and the libraries they're built on rely on unixtime mean applications, scripts, etc., will need to be rewritten. Then there's issues with embedded systems where such a software fix might not even …This now allows XFS to run well past the Year 2038 problem (where storing the time since 1970 in seconds will no longer fit in a signed 32-bit integer and thus wraparound) to now the Year 2486. Making a new XFS file-system with bigtime enabled allows a timestamp range from December 1901 to July 2486 rather than December 1901 to January 2038.Feb 19, 2024 · The 2038 bug, also known as the Unix Millennium Bug or Y2K38, is a problem that arises from the way some systems store and represent date and time values using a number called a timestamp. A timestamp is the number of seconds that have passed since January 1, 1970, which is called the Unix epoch. The year 2038 problem is an issue for computing and data storage situations in which time values are stored or calculated as a signed 32 bit integer, this number is interpreted as the number of seconds since 00:00:00 1st Jan 1970, (also known as the epoch). This is absolutely unavoidable.Linux was facing a big problem with keeping time . getty. A looming problem with Linux-based computers being unable to handle dates beyond the year 2038 appears to have been solved - or at least ... Another date problem, which results from computing dates into the year 2038 and beyond in 32-bit operating systems. Unix and other C applications represent time as the number of seconds from ... WIP: bpo-34990: year 2038 problem in compileall.py #9892; bpo-34990: Change pyc headers to use 64-bit timestamps #19651; bpo-34990: Treat the pyc header's mtime in compileall as an unsigned int #19708 [3.10] bpo-34990: Treat the pyc header's mtime in compileall as an unsigned int (GH-19708) #27928No Mercy: The Year 2038 Problem · in UNIX time, two billion seconds after Jan 1, 1970 is Jan 19, 2038 · in UNIX time, two billion seconds before Jan 1, 1970 is .... The year 2038 problem (also known as Y2038, Y2K38, Y2K38 superbug or the Epochalypse) is a time computing problem that leaves some computer systems unable to represent times after 03:14:07 UTC on 19 January 2038. codeverse-chronicles.vercel.appOct 19, 2020 · The forthcoming Linux 5.10 looks like it will include further fixes for the Year 2038 problem, aka Y2K38. The flaw means that many systems can’t conceive of dates beyond 03:14:07 UTC on 19 January 2038. Y2K was caused by systems representing years with two digits and assuming that a year ending with two zeroes would be 1900. WIP: bpo-34990: year 2038 problem in compileall.py #9892; bpo-34990: Change pyc headers to use 64-bit timestamps #19651; bpo-34990: Treat the pyc header's mtime in compileall as an unsigned int #19708 [3.10] bpo-34990: Treat the pyc header's mtime in compileall as an unsigned int (GH-19708) #27928Jun 20, 2011 · This value is 0.The maximum value of time before it rolls over to a negative (and invalid) value is 2,147,483,647, which translates into January 19, 2038. On this date, any C programs that use the standard time library will start to have problems with date calculations.To correct it simply recompile the programs with a new version of the ... An estimated three out of four people wear some form of corrective lenses, according to the Vision Impact Institute. Even though so many people wear glasses and contacts, correctiv... The Network Time Protocol has an overflow issue related to the Year 2038 problem, which manifests itself at 06:28:16 UTC on 7 February 2036, rather than 2038. The 64-bit timestamps used by NTP consist of a 32-bit part for seconds and a 32-bit part for fractional second, giving NTP a time scale that rolls over every 2 32 seconds (136 years) and ... The year-2038 problem will ultimately affect all code that uses 32 bits for time values. Over the past year, the Linux kernel community has begun formally hashing out its plan to transition to 64-bit time support. As a result, other development teams have been observing the kernel discussion and have started to plan their own approaches.Sixty-eight years after 1970, Zimmie said, is 2038. Anyone who deals with UNIX time should recognize the year 2038, which has its own website warning of troubles ahead. "The latest time which can ...Is the 2038 problem solved? There is no universal solution to the problem, though many modern systems have been upgraded to measure Unix time with signed 64-bit integers which will not overflow for 292 billion years, which is approximately 21 times the estimated age of the universe.
In this video I discuss the Y2K38 bug, also known as the end of Unix time and the year 2038 problem, software that is currently affected by the bug, and what.... Site watch anime
The Year 2038 problem (also known as Y2038, [1] Y2K38, or the Epochalypse [2] [3]) is a time formatting bug in computer systems with representing …Use 64-bit time_t on 32-bit architectures to avoid the 'year 2038 problem' when the existing 32-bit signed int rolls over (potentially setting time back to 1900). ... This is now less that 15 years away and plenty of system that will have problems have already been shipped. We should stop adding to the problem. Most computing, especially ...The 64-bit timestamps used by NTP consist of a 32-bit part for seconds and a 32-bit part for fractional second, giving NTP a time scale that rolls over every 2 32 seconds (136 years) and a theoretical resolution of 2-32 seconds (233 picoseconds). NTP uses an epoch of 1 January 1900. The first rollover occurs in 2036, prior to the …The Year 2038 problem (also known as Y2038, [1] Y2K38, or the Epochalypse [2] [3]) is a time formatting bug in computer systems with representing …2038 will be a common year starting on Friday of the Gregorian calendar, the 2038th year of the Common Era (CE) and Anno Domini (AD) ... At January 19 2038 at 3:14:07 UTC, due to the year 2038 problem, Signed 32-bit unix time will overflow and revert to December 13 1901 at 20:45:52 UTC.In this digital age, having a reliable email service provider is essential for staying connected with friends, family, and colleagues. AOL has been a popular choice for many users ...The Year 2038 problem is an issue for computing and data storage situations in which time values are stored or calculated as a signed 32-bit integer, and this number is interpreted as the number of seconds since 00:00:00 UTC on 1 January 1970 ("the epoch").The start date for computer calendars is January 1, 1970, and the idea is they *theoretically* count down in seconds to infinity. However, 32-bit processors are only physically capable of counting up to 2,147,483,647. So the idea is that, at 03:14:07 UTC On Jan 19, 2038, these processor will reach max capacity.All press is good press — until that press goes too well. Although the Netherlands’ beautiful, canal-filled city of Amsterdam garners about $91.5 billion a year through tourism, th...We were upgrading to 10.4.12 recently and found an year 2038 issue in the integration tests. This is a regression from 10.4.0 which is known good. ... Report a problem; Powered by a free Atlassian Jira open source license for MariaDB Corporation Ab. Try Jira ... The year 2038 problem (also known as Y2038, Y2K38, Y2K38 superbug or the Epochalypse) is a time computing problem that leaves some computer systems unable to represent times after 03:14:07 UTC on 19 January 2038. If you use a Unix- or Linux-based system, there's one more date-related bug you'll need to worry about -- in the year 2038. All 32-bit Unix/Linux-based systems store … The year 2038 problem is a time computing problem that leaves some computer systems unable to represent times after 03:14:07 UTC on 19 January 2038. It is intended to be dropped into C projects as a replacement for time.h. It is being used in Perl and I intend to fix Ruby and Python's 2038 problems with it as well. This gives you a safe range of +/- 292 million years. You can find the code at the y2038 project.May 5, 2015 · A full investigation of the Ariane incident found that a process left over from software in the previous generation of rockets, Ariane 4, had captured an unexpectedly high reading for the sideways... I was wondering if Postgres will be handling the unix epoch problem coming in 2038? I have read about this and am wondering. ... Completed item: Extend timezone code to allow 64-bit values so we can represent years beyond 2038 . Share. Improve this answer. Follow edited Mar 25, 2019 at 23:30. answered Mar 25, 2019 at 23:24. ... 而且事实上 2038 年问题的范围远不止于此。. 前面谈到的问题都还是操作系统运行时表示数据的溢出，但还有一些数据是静静在躺在某个磁盘上，当时间走到 2038 之后再把它它们翻读出来，一样会出现问题。. 我们知道文件都有几种时间属性，比如创建时间，最后 ... .