Zak :1password:<p>My biggest issue with <a href="https://infosec.exchange/tags/OpenWRT" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenWRT</span></a> so far is the upgrade process. As in, keeping the OS up to date. The package manager's upgrade functionality, which is fully baked into the OS and its GUI web interface, prominently displays a warning at the top that tells you not to use it. Don't upgrade packages, it can and will break your system: <a href="https://openwrt.org/meta/infobox/upgrade_packages_warning" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">openwrt.org/meta/infobox/upgra</span><span class="invisible">de_packages_warning</span></a></p><p>Okay, then why is that feature baked into the OS at all?</p><p>Meanwhile, the sysupgrade feature, which is the recommended way to keep the OS up to date, is also baked into the OS, but only at the cli level. If you want to use the GUI web interface, you need to manually install the attended-sysupgrade package, after which point you can manually re-flash the OS whenever you want to using up to date packages, provided that you also (somehow) keep up to date about their releases without the use of a real tool to check for updates using the GUI. Why isn't that baked into the OS instead?</p><p>The whole thing is just very confusing.</p><p><a href="https://infosec.exchange/tags/FOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FOSS</span></a> <a href="https://infosec.exchange/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Linux</span></a></p>