Ref #03. Refactoring.
This commit is contained in:
1 parent
13a88b7270
commit
931efeabc7
4 files changed
+11
-178
No files matched your search
@@ -60,9 +60,6 @@ What if the network disappears? In this example, once the required files and ver
|
||||
|
||||
If the update itself is interrupted, the device needs enough saved information to work out what happened before continuing. We will look at storage, boot behavior, and recovery in later chapters.
|
||||
|
||||
Two ADRs explain the choices behind this example:
|
||||
|
||||
- [ADR-011: Device-Initiated Update Checks](../adr/ADR-011-device-initiated-update-checks.md) — how does a device find updates when its connection and settings allow it?
|
||||
- [ADR-012: Device-Controlled Update Execution](../adr/ADR-012-device-controlled-update-execution.md) — why let the device finish the update when the server is unreachable?
|
||||
[ADR-011: Device-Initiated Update Checks](../adr/ADR-011-device-initiated-update-checks.md) explains how a device checks for updates at power-on, on a schedule, or at the operator’s request.
|
||||
|
||||
Next, we will follow the boot process and see what happens before Linux and the OTA manager start.
|
||||
Reference in new issue
Block a user