4 ms·
Note that this device is currently using a 32-bit ARM processor, so it will likely be affected by the Y2038 issue, unless OpenWRT and other distros end up fixin
by pabs3 5y ago
Note that this device is currently using a 32-bit ARM processor, so it will likely be affected by the Y2038 issue, unless OpenWRT and other distros end up fixing that issue. In addition support for 32-bit in general and 32-bit ARM in particular in the Linux distro space is waning, for example Fedora is talking about retiring ARMv7 support. Presumably OpenWRT and TurrisOS will retain support for as long as possible though. Other Turris devices (MOX etc) use newer 64-bit processors and aren't affected by those issues.
https://fedoraproject.org/wiki/Changes/RetireARMv7 https://fedoraproject.org/wiki/Changes/RetireARMv7
- ginko 5y agoWhat does the used architecture have to do with the Y2038 issue? You can use 64 bit integers in a 32-bit system you know..
- pabs3 5y agoMost 32-bit architectures are affected by Y2038, because they use 32-bit time_t, which is part of the ABI for an architecture. So if you want 64-bit time_t, you need to either have a new ABI (and recompile the world against it), or introduce new functions using the 64-bit time_t (similar to the transition to 64-bit file sizes).
- pantalaimon 5y agoOpenWRT uses musl which has 64 bit time_t. It also compiles the whole system to a single image, so you don’t have the problem with ABI incompatibilities because you typically don’t run random third party binaries.
- pabs3 5y agoTurrisOS (OpenWRT based) is more like a normal Linux distro, it uses BTRFS, you can install packages with opkg, even run other distros with LXC.
- somat 5y agoor use openbsd which made the transition to a 64-bit time_t for all architectures. https://marc.info/?l=openbsd-cvs&m=137637321205010&w=2 https://marc.info/?l=openbsd-cvs&m=137637321205010&w=2 in 2013...
- ginko 5y agoThat's just a software issue. OpenBSD has been using 64-bit time_t on all their architectures for almost a decade now: https://marc.info/?l=openbsd-cvs&m=137637321205010&w=2 https://marc.info/?l=openbsd-cvs&m=137637321205010&w=2
- yrro 5y agoIt's worth noting that this was possible because OpenBSD are happy to break their ABI in order to improve their operating system. Linux values ABI stability highly, and prefers to introduce new interfaces that applications have to opt into (e.g., as was done with support for 64-bit file offsets on 32-bit architectures).
- Deukhoofd 5y agoLinux 5.6+ made time_t 64 bit in kernelspace. musl 1.2+ and glibc 2.32+ made it 64 bit in userspace as well.
- yrro 5y agoI think you mean glibc 2.34: https://sourceware.org/pipermail/libc-alpha/2021-August/129718.html https://sourceware.org/pipermail/libc-alpha/2021-August/1297... You opt-in by building with -D_TIME_BITS=64: https://www.gnu.org/software/libc/manual/html_node/Feature-Test-Macros.html#index-_005fTIME_005fBITS https://www.gnu.org/software/libc/manual/html_node/Feature-T... An approach not without its problems: 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... - but then again software that relies on time_t being 32 bits has been broken on 64-bit architectures for a very long time already, surely? I suppose I could have written that "GNU/Linux values ABI stability" in my comment, instead of plain "Linux"... ;)
- Deukhoofd 5y agoAh yes you're right, I was going by the Linux 5.6 release notes, which gave 2.32 as version. I personally fully expect TIME_BITS to default to 64 soon, but looking at the 2.35 fixed bugs, they were right in not immediately switching it over. I see at least 2 bugs related to it.
- mkj 5y agoDev OpenWRT appears to have already updated to a recent musl which supports time64 syscalls, so it will work fine. https://forum.openwrt.org/t/error-with-libc-so-gettimeofday-time64-symbol-not-found/113211/5 https://forum.openwrt.org/t/error-with-libc-so-gettimeofday-... That Fedora page doesn't mention anything about time?
- pabs3 5y agoFedora is talking about dropping support for all 32-bit ARM CPUs (ARMv7), so it won't run on the Turris Omnia after that. Nothing to do with time_t or Y2038, but I guess that factors into it.
- pantalaimon 5y agoFedora and OpenWRT have very different use cases
- pabs3 5y agoFedora is a general distro, suitable for all use-cases. For example the Fedora IoT spin has a similar use-case to OpenWRT.
- pantalaimon 5y agoDoes Fedora IoT fit into 16 MiB Flash?
- yjftsjthsd-h 5y agoIn 16 years, will the hardware still be working anyways? That's longer than any other network device I've ever used has lived.
- johnklos 5y agoYes. Sixteen years is not a long time at all. My full time laptop is from 2008, for instance, and I have hardware which has run continuously since the '90s that are still running perfectly fine.
- cassianoleal 5y agoI suspect in 16 years the internal flash will have worn out. I'm not sure the device can boot from external storage but if it does it might still be a decent router then.
- pantalaimon 5y agoWhy would it write to internal flash at all? The flash on my OpenWRT router is mounted read-only.
- cassianoleal 5y agoThis is TurrisOS, not vanilla OpenWRT. Root is a read-write btrfs volume. You can install packages, you can change whatever you want. You can even run containers on it, although it's highly discouraged precisely to prevent it from wearing out too soon. In any case, on vanilla OpenWRT the overlay is rw and also gets written to the flash. It sees a lot less activity than on TurrisOS but it exists, otherwise it couldn't persist your config between reboots.
- pabs3 5y agoYou can plugin new storage to the internal mSATA slot if needed.
- darkwater 5y ago15 years of life for a home router is pretty good anyway, no?
- johnklos 5y agoThere's always BSD for when (mostly commercial) Linux distros decide to end support for perfectly good, modern hardware, and the BSDs already started using 64 bit time on 32 bit architectures ages ago.
- LargoLasskhyfv 5y agoDo you really think somebody will still use that at the time? Are you using anything that old now? I mean networked electronic gadgetery, not kitchen appliances.