3 ms·

Good for Debian! Related links: https://en.wikipedia.org/wiki/Year_2038_problem https://en.wikipedia.org/wiki/Year_2038_problem https://www.theregister.com/202

by gregw2 3y ago

Good for Debian! Related links: https://en.wikipedia.org/wiki/Year_2038_problem https://en.wikipedia.org/wiki/Year_2038_problem https://www.theregister.com/2020/01/30/linux_5_6_2038/ https://www.theregister.com/2020/01/30/linux_5_6_2038/ https://opensource.com/article/19/1/year2038-problem-linux-kernel https://opensource.com/article/19/1/year2038-problem-linux-k... https://www.gnu.org/software/gnulib/manual/html_node/Avoiding-the-year-2038-problem.html https://www.gnu.org/software/gnulib/manual/html_node/Avoidin... https://ariadne.space/2021/12/29/glibc-is-still-not-y2038-compliant-by-default/ https://ariadne.space/2021/12/29/glibc-is-still-not-y2038-co... Are manufacturers of IOT devices using Linux whose devices have a lifespan of 15 years thinking about this yet? I doubt it. Where is the startup for a consumer-visible certification body that ensures my device will fully function during Y2038?

wolrah 3y ago
> Are manufacturers of IOT devices using Linux whose devices have a lifespan of 15 years thinking about this yet? I doubt it. Considering how many of the IoT devices I tinker with have kernels and major userspace tools that are so out of date they make Debian Stable look bleeding-edge I feel like most of the vendors in that space will start caring about it somewhere around a week or two AFTER the rollover, and will have been confidently blaming their customers' networks for any issues up to that point.