[cassianoleal]

The Turris Omnia does update automatically but it runs an insanely old version of OpenWRT. Once TurrisOS 4 comes out it should fix that but it's taking a very long time to happen.

Auto-updating a plain OpenWRT installation is not hard to implement and allows you to stay up-to-date.

That said, the Omnia's hardware is pretty great and the fact that you can plug eMMC storage to run LXC containers is absolutely fantastic.

You can also install plain OpenWRT on it these days.

[dredmorbius]

Auto-updating if you have storage space for opkg installs is reasonably sane, via opkg. Building a new firmware image is not. Updating via stock builds (LuCI or sysupgrade) leaves the matter of local configurations and package installs ... at best unclear.

A major set of problems are:

- Minuscule rewriteable storage on consumer networking kit.

- The need to create a firmware image, and not merely select and configure packages on disk.

- Bootloader fuckwittedness.

None of these are OpenWRT's fault. They do define the operating theatre, however. Unfortunately, in light of this, OpenWRTs tools and documentation are not up to the task. Yes, free software, volunteer project, etc., etc. I'm hoping my criticisms may be useful.

Many consumer devices (my ADSL modem comes to mind) have nanoscopic writable storage: 8 MB is not atypical.

OpenWRT's other upgrade opions are ... neither clearly stated nor readily achieved.

One of the higher-ranked HN OpenWRT submissions concerns why there is no autoupdate:

https://web.archive.org/web/20160206204329/http://prpl.works... (https://news.ycombinator.com/item?id=10870294)

The OpenWRT user guide does not clearly address system upgrades, though there's otherwise good coverage of many topics:

https://openwrt.org/docs/guide-user/start

The most applicable section appears to be "Installing Additional Software", with sections:

- Beginners guide to building your own firmware

- Extroot configuration

- Managing packages

- Opkg Package Manager

- Saving firmware space

- Show available package upgrades after SSH login

- Using the Image Builder

Only the last directly addresses upgrading. A dedicated "System UpgradinG" document would be extremely useful.

The sysupgrade docs are not in the user guide but the technical reference:

https://openwrt.org/docs/techref/sysupgrade

I've tried compiling from source. There's a hell of a lot of menuconfig, and my build failed after 9+ hours. Not newbie-friendly at all. (FWIW I don't consideer mysef a newbie.)

I've not yet tried the imagebuilder.

I'm very familiar (20+ years) with Febian, and both the familiarity and its APT package management make the process highly predictable (with much help from ample storage and open bootloader standards). OpenWRTx is a long way from that, yet.

If you've any illumination or advice to add beyond "Auto-updating a plain OpenWRT installation is not hard to implement and allows you to stay up-to-date", I'm all ears.