3 things to know about planning for OTA updates in your homelab
Alan Smithee
Mon, 09/05/2022 – 03:00

1 reader likes this
1 reader likes this

Updates to a system used to be relatively straightforward. When a developer needed to revise something that they’d already distributed to the public, an updater would be released for people to run. Users would run the updater, allowing old files to be replaced by new files and new files to be added. Even with these “relatively straightforward” updates, though, there was a catch. What happens when a user’s installation is in an unexpected state? What happens when an upgrade is interrupted? These questions are just as relevant now when all kinds of devices are online, and sometimes in need of important security updates. Many updates today are delivered wirelessly, over-the-air (OTA), and the potential for poor connections, sudden loss of signal, or loss of power, … // Read more: original article.

Previous post Using a Raspberry Pi as a Bluetooth speaker with PipeWire
Next post Arducam launches $30 ToF depth camera for Raspberry Pi devices