we just released Turris OS 3.8.6. This release is quite limited and fixes just one but nevertheless very important bug. Unfortunately solution is currently available only for Omnia users, we have no solution for old Turris routers yet.
What is the bug about? Since the dawn of time, our routers were able to run software compiled just for them. Quite some users complained that they can’t run they favorite text editor their friend wrote and that we don’t have it in repositories and cross-compilation using SDK is not end-user friendly. And that we should have used MS-DOS 6.22 to avoid all those problems. With 3.8.6, we finally at least partially address those complains and now you can finally run statically linked 386 (and x86_64) Linux binaries on your router. All you need to do is install qemu package that is now available in your repositories.
Enjoy and let us know any interesting use-cases you will find
An observation with this release: I had automatic updates/automatic installation enabled this time. I rebooted the router manually through foris immediately after the notice that a reboot was required a couple of days ago.
Last night, however, the router still unnecessarily auto-rebooted at the auto-install designated time (3:30AM).
Ah yes! /tmp is still tmpfs but I did make /var persistent a long time ago. I presume that’s where it stores some kind of flag indicating a reboot is needed, assuming it’ll be automatically lost after a reboot.
I think I could probably change /var back to tmpfs and just make the logs persist on ssd.
