• zik@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    8 months ago

    It’s already been addressed in Linux - not sure about other OSes. They doubled the size of time data so now you can keep using it until after the heat death of the universe. If you’re around then.

    • dev_null@lemmy.ml
      link
      fedilink
      English
      arrow-up
      0
      ·
      8 months ago

      Obviously new systems are unaffected, the question is how many industrial controllers checking oil pipeline flow levels or whatever were installed before the fix and never updated.

      • CLOTHESPlN@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        8 months ago

        Being somewhat adjacent to that with my work, there is a good chance anything in a critical area (hopefully fields like utilities, petroleum, areas with enough energy to cause harm) have decently hardened or updated equipment where it either isn’t an issue, will stop reporting tread data correctly, or roll over to date “0” which depending on the platform with industrial equipment tends to be 1970 in my personal experience. That said, there is always the case that it will not be handled correctly and either run away or stop entirely.

    • Matombo@feddit.de
      link
      fedilink
      English
      arrow-up
      0
      ·
      8 months ago

      debian for example is atm at work recompiling everything vom 32bit to 64bit timestamps (thanks to open source this is no problem) donno what happens to propriarary legacy software

    • AdrianTheFrog@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      8 months ago

      I think everything works in windows but the old windows media player. You can test it by setting the time in a windows VM to 2039.