3 ms·

So that means the best tool is a 2038 test environment - which people then install their application(s) and test it e2e to see what the impacts are. However, I

So that means the best tool is a 2038 test environment - which people then install their application(s) and test it e2e to see what the impacts are. However, I’m not sure how you make a 2038 test environment It assumes that the OS/Kernel etc… are defacto frozen to 2025 or whatever increment until 2038 What was the y2k solution for the people that implemented those fixes in the 90s?

deleted 1y ago
[deleted]
TacticalCoder 1y ago
[dead]
jcul 1y ago
libfaketime is useful for testing these kinds of things. It intercepts system calls to get the time and reports a fake time to the application. https://github.com/wolfcw/libfaketime https://github.com/wolfcw/libfaketime