Announcement

Collapse
No announcement yet.

The Linux Kernel Is Still Rectifying The Year 2038 Problem

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • L_A_G
    replied
    Definitely something that needs to be addressed, but it's not like the panic a lot of people got into in 1999...

    Originally posted by cen1 View Post
    Could you simulate software bugs by setting the OS time to 2039? Might be a good idea to make a test case in CI.
    My understanding is that this is exactly what they did to find Y2K bugs in software. However the main difference between Y2K and the 2038 problem is that the Y2K problem was an issue for applications and not the underlying OSs while the 2038 problem is exactly the other way around. In other words you just need to fix the OS and you're fine and don't have to go for the massive application bug hunting that took place with the Y2K problem.
    Last edited by L_A_G; 20 November 2017, 06:37 AM.

    Leave a comment:


  • cen1
    replied
    A lot of software probably won't be fixed and funny stuff will happen in 2038. I hope to live and see that day. Hopefully no nuclear meltdowns tho.

    Could you simulate software bugs by setting the OS time to 2039? Might be a good idea to make a test case in CI.

    Leave a comment:


  • timofonic
    replied
    I would love to know when Real Time Linux patches will get merged upstream/vanilla. Please make it happen!

    Leave a comment:


  • Guest
    Guest replied
    Originally posted by oldgaro View Post
    "If the Linux Kernel was written in Rust that would not happen"

    sqn!
    It's integer overflow, how would Rust have helped with that?

    Leave a comment:


  • F.Ultra
    replied
    Originally posted by smitty3268 View Post

    Just kicking the can down the road. Now we have a Y292B problem.

    Clearly the only real solution is to come up with a variable length date structure.
    Beats Windows with their Y28K problem though :-)

    Leave a comment:


  • smitty3268
    replied
    Originally posted by JustRob View Post
    64 Bits will get us to the year 292,471,208,630.
    Just kicking the can down the road. Now we have a Y292B problem.

    Clearly the only real solution is to come up with a variable length date structure.
    Last edited by smitty3268; 19 November 2017, 03:36 PM.

    Leave a comment:


  • andrei_me
    replied
    Originally posted by oldgaro View Post
    sqn!
    Like in portuguese "só que não"?

    Leave a comment:


  • doublez13
    replied
    Originally posted by oldgaro View Post
    "If the Linux Kernel was written in Rust that would not happen"

    sqn!
    I can't see it taking more than a cycle or two to rewrite everything in Rust.

    Leave a comment:


  • c117152
    replied
    Quick! Before it's too late!

    Leave a comment:


  • JustRob
    replied
    64 Bits will get us to the year 292,471,208,630.

    Leave a comment:

Working...
X