Reply to thread

Message

<blockquote data-quote="Ranhiru" data-source="post: 1085274" data-attributes="member: 17748"> <img src="http://www.y2k38.info/Year_2038_problem.gif" alt="" class="fr-fic fr-dii fr-draggable " style="" />Y2K38&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp;
<ul>
<li data-xf-list-type="ul"><a href="http://www.y2k38.info/#" target="_blank">On January 19, 2038,&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; UNIX-based programs and UNIX-like operating systems will run out of&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; time. To be more precise, at 3:14:07 GMT, UNIX will be exactly 1 billion&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; seconds old. Many see this as a milestone, but from a technical point of&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; view, this can mean disaster for computer programs and systems around&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; the world.</a></li>
</ul>Explanation&nbsp; &nbsp; &nbsp; &nbsp;&nbsp; UNIX keeps track of time in a 4-byte integer that represents the&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; number of seconds after January 1, 1970 12:00:00. &nbsp; &nbsp; &nbsp; &nbsp; For example, a time of 60 represents the date January 1, 1970 12:01:00.&nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; A 4-byte integer has a maximum value of 2,146,483,547. This time (known&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; as maximum time) corresponds exactly to January 19, 2038 3:14:07. &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; This explains why UNIX programs in large, were pretty much unaffected by&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; the Y2K bug - since it kept track of time in units of seconds. However,&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; its own version of Y2K will occur a second past the maximum time.&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; Consequence&nbsp; &nbsp; &nbsp; &nbsp;&nbsp; At exactly January 19, 2038 3:14:08 (one second past the maximum UNIX&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; time), one of two things can happen to programs that keep track of time&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; with this format. It will either crash and stop functioning altogether,&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; or it will rollback time to the beginning of UNIX time: the first minute&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; of 1970. &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; What this means for computer programs and systems that haven't been&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; fixed depends on the program itself. The consequences can be similar&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; those predicted with the Y2K bug. &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Many pieces of software that involve future dates (i.e. Calendars,&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Investment calculators etc.) are already experiencing problems with the&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2038 bug, being unable to involve any dates past 2038. &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Also, some calculations that involve averaging dates have begun to fail&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; as well. For example, if an algorithm adds two dates together and then&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; divides by 2 to find the middle date, it would fail. Preparation&nbsp; &nbsp; &nbsp; &nbsp;&nbsp; Many popular software updates recently are already addressing this&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; issue. If your favourite software isn't, do not worry, the bug will&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; occur in over 30 years. During that time, it is very likely that most&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; systems will have gone to a 64-bit operating system (where this problem&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; is averted for over 290 billion years - much past the lifespan of the&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; sun). &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; For those systems or programs still on a 32-bit platform, the bug will&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; indeed cause problems, but fixing the problem will not be difficult due&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; to the nature of it. It will not require recoding how dates are stored&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; in a program as was the case with Y2K, dates will merely be required to&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; be stored in a primitive type with larger precision. &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; As for programs that involve averaging dates, the simplest solution&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; would be some basic alegebraic manipulation: to divide the dates by two&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; before adding them together.&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; Machines Affected&nbsp; &nbsp; &nbsp; &nbsp;&nbsp; Currently (March 1998) there are a huge number of machines affected.&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Most of these will be scrapped before 2038. However, it is possible that&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; some machines going into service now may still be operating in 2038.&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; These may include process control computers, space probe computers,&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; embedded systems in traffic light controllers, navigation systems etc.&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; etc. Many of these systems may not be upgradeable. For instance,&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Ferranti Argus computers survived in service longer than anyone&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; expected; long enough to present serious maintenance problems. &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Note: Unix time is safe for the indefinite future for referring&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; to future events, provided that enough bits are allocated. Programs or&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; databases with a fixed field width should probably allocate at least 48&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; bits to storing time values.Hardware, such as clock circuits, which has adopted the Unix time&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; convention, may also be affected if 32-bit registers are used. &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; In my opinion, the Y2K38 threat is more likely to result in&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; aircraft falling from the sky, glitches in life-support systems, and&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; nuclear power plant meltdown than the Y2K threat, which is more likely&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; to disrupt inventory control, credit card payments, pension plans etc.&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; The reason for this is that the Y2K38 problem involves the basic system&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; timekeeping from which most other time and date information is derived,&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; while the Y2K problem (mostly) involves application programs. &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Emulation and Megafunctions&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; While 32-bit CPUs may be obsolete in desktop computers and&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; servers by 2038, they may still exist in microcontrollers and embedded&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; circuits. For instance, the Z80 processor is still available in 1999 as&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; an Embedded Function within Altera programmable devices. Such embedded&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; functions present a serious maintenance problem for Y2K38 and similar&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; rollover issues, since the package part number and other markings&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; typically give no indication of the internal function. &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Software Issues&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Databases using 32-bit Unix time may survive through 2038.&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Care will have to be taken to avoid rollover issues.</blockquote>

[QUOTE="Ranhiru, post: 1085274, member: 17748"] [B] [IMG]http://www.y2k38.info/Year_2038_problem.gif[/IMG][/B] [B]Y2K38[/B] [LIST] [*][URL="http://www.y2k38.info/#"]On January 19, 2038, UNIX-based programs and UNIX-like operating systems will run out of time. To be more precise, at 3:14:07 GMT, UNIX will be exactly 1 billion seconds old. Many see this as a milestone, but from a technical point of view, this can mean disaster for computer programs and systems around the world.[/URL][/LIST] [B]Explanation[/B] UNIX keeps track of time in a 4-byte integer that represents the number of seconds after January 1, 1970 12:00:00. For example, a time of 60 represents the date January 1, 1970 12:01:00. A 4-byte integer has a maximum value of 2,146,483,547. This time (known as maximum time) corresponds exactly to January 19, 2038 3:14:07. This explains why UNIX programs in large, were pretty much unaffected by the Y2K bug - since it kept track of time in units of seconds. However, its own version of Y2K will occur a second past the maximum time. [B]Consequence[/B] At exactly January 19, 2038 3:14:08 (one second past the maximum UNIX time), one of two things can happen to programs that keep track of time with this format. It will either crash and stop functioning altogether, or it will rollback time to the beginning of UNIX time: the first minute of 1970. What this means for computer programs and systems that haven't been fixed depends on the program itself. The consequences can be similar those predicted with the Y2K bug. Many pieces of software that involve future dates (i.e. Calendars, Investment calculators etc.) are already experiencing problems with the 2038 bug, being unable to involve any dates past 2038. Also, some calculations that involve averaging dates have begun to fail as well. For example, if an algorithm adds two dates together and then divides by 2 to find the middle date, it would fail. [B] Preparation[/B] Many popular software updates recently are already addressing this issue. If your favourite software isn't, do not worry, the bug will occur in over 30 years. During that time, it is very likely that most systems will have gone to a 64-bit operating system (where this problem is averted for over 290 billion years - much past the lifespan of the sun). For those systems or programs still on a 32-bit platform, the bug will indeed cause problems, but fixing the problem will not be difficult due to the nature of it. It will not require recoding how dates are stored in a program as was the case with Y2K, dates will merely be required to be stored in a primitive type with larger precision. As for programs that involve averaging dates, the simplest solution would be some basic alegebraic manipulation: to divide the dates by two before adding them together. [B]Machines Affected[/B] Currently (March 1998) there are a huge number of machines affected. Most of these will be scrapped before 2038. However, it is possible that some machines going into service now may still be operating in 2038. These may include process control computers, space probe computers, embedded systems in traffic light controllers, navigation systems etc. etc. Many of these systems may not be upgradeable. For instance, Ferranti Argus computers survived in service longer than anyone expected; long enough to present serious maintenance problems. [I]Note[/I]: Unix time is safe for the indefinite future for referring to future events, provided that enough bits are allocated. Programs or databases with a fixed field width should probably allocate at least 48 bits to storing time values. Hardware, such as clock circuits, which has adopted the Unix time convention, may also be affected if 32-bit registers are used. In my opinion, the Y2K38 threat is more likely to result in aircraft falling from the sky, glitches in life-support systems, and nuclear power plant meltdown than the Y2K threat, which is more likely to disrupt inventory control, credit card payments, pension plans etc. The reason for this is that the Y2K38 problem involves the basic system timekeeping from which most other time and date information is derived, while the Y2K problem (mostly) involves application programs. [B]Emulation and Megafunctions [/B] While 32-bit CPUs may be obsolete in desktop computers and servers by 2038, they may still exist in microcontrollers and embedded circuits. For instance, the Z80 processor is still available in 1999 as an Embedded Function within Altera programmable devices. Such embedded functions present a serious maintenance problem for Y2K38 and similar rollover issues, since the package part number and other markings typically give no indication of the internal function. [B]Software Issues [/B] Databases using 32-bit Unix time may survive through 2038. Care will have to be taken to avoid rollover issues. [/QUOTE]

Verification

Dawasata paya keeyak thibeda?

Search

Latest ads

Reply to thread