Will MorphOS have a Y2K or 2038 type problem?
  • Just looking around
    stvcmty
    Posts: 3 from 2025/1/6
    Will MorphOS have a Y2K or 2038 type problem?

    Is there a maximum date/time for MorphOS? Y2K was a problem for software that used two digits for the year. 2038 is a problem for operating systems that use a 32-bit number to track seconds since 1 January 1970. How does MorphOS track time?

    I have a couple apple G4 based systems I enjoy using from time to time and MorphOS looks like a good option, but I hope it will not have any date problems in the next few decades.

    Thanks,

    -Stv
    Mac Mini G4 1.42 GHz
    eMac G4 1.25 GHz
  • »14.01.25 - 18:52
    Profile
  • MorphOS Developer
    Piru
    Posts: 588 from 2003/2/24
    From: finland, the l...
    MorphOS tracks the time as unsigned 32-bit seconds since 1-jan-1978 00:00:00. Thus MorphOS itself is fine until Tuesday, February 7, 2114. This is for about 88 years (as of writing this).

    Any application using the C standard library "time_t" and "struct timeval" will currently have the time wrap in 2038. There are plans to address this issue, and changes toward this are in motion, but they will require careful planning to maintain backward compatibility with runtimes, shared libraries and similar that expose time_t or "struct timeval". Parts of this work have already started. While there is no firm schedule set for this work it should be completed way before 2038.

    [ Edited by Piru 14.01.2025 - 22:05 ]
  • »14.01.25 - 20:02
    Profile
  • Just looking around
    stvcmty
    Posts: 3 from 2025/1/6
    Piru, thank you for the reply. I am glad the OS on my eMac and mac mini G4 are good for longer than I am likely to be alive.
    Mac Mini G4 1.42 GHz
    eMac G4 1.25 GHz
  • »14.01.25 - 20:22
    Profile