YK- 2038 Bug

Vikash Chandra Sharma

Abstract


This paper talks about the problem we all will be facing precisely   on 19th Jan.   2038.Digital world has been vulnerable by several bugs however, solely a couple of looked as if it would cause a good danger. The bug that got most famed was Y2K. Somehow, we tend to got over it, then, there was Y2K10. It too was resolved and currently we tend to have Y2K38. The Y2K38 bug, if not resolved, will make sure that the predictions that were created for the Y2K bug come true this point. On 19th Jan. 2038 within all UNIX supported Operating system Time and Date would began to work incorrectly. This    produces a big problem which is critical for all Software’s and basically a threat   to embedded systems. Hence afterwards   it   basically shows possible solutions   which we can take to avoid Unix Millennium 2038 problem. By doing research I have developed a patch. Now I have moved this    patch to GitHub. This patch can enable the 32bit S/W to use   64bit   time_t   on   a 32bit computer.  This  patch  is still under development but it is  current  state  has been shown in this paper along with  all  the  codes  and brief description of each and every function and files. I think to  quickies  way to solve this problem is by using patch which  Software  developers   who   are having 32bit S/w simply  needs  to  include  all  header   files   and implementation files within their software and use  the function I along with other open source community  has   made. Coding has been done in C language.


Full Text:

PDF

Refbacks

  • There are currently no refbacks.