mirror of
https://github.com/home-assistant/developers.home-assistant.git
synced 2025-07-24 17:56:31 +00:00
Document OS boot slot persistence when using GRUB (#2295)
* Document OS boot slot persistence when using GRUB Since home-assistant/supervisor#5276 boot slot will be persisted when user selects it in the GRUB menu. Document this behavior. * Grammar adjustment by coderabbit Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> --------- Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
This commit is contained in:
parent
a5662c1608
commit
3d6369b44c
@ -58,6 +58,8 @@ o [kernel.1] (/dev/disk/by-partlabel/hassos-kernel1, raw, inactive)
|
||||
|
||||
After an update, RAUC instructs the bootloader to boot into the other slot (e.g. with U-Boot by writing U-Boot environment variables). If the boot succeeds, the slot is marked good and the system will continue to boot into this boot slot. Typically, three attempts are made with each boot slot before reverting to the other boot slot, but the exact logic is dependent on the bootloader integration.
|
||||
|
||||
The boot slot can be changed using the `ha os boot-slot` command. On systems using the GRUB bootloader, the boot menu can also be used. In that case, the selected boot slot will be used for future boots, until it’s changed again manually or by an OS update.
|
||||
|
||||
## Security
|
||||
|
||||
The HAOS RAUC update bundles are signed. HAOS has its own PKI with development and release CAs. Currently, all public builds are signed with the release CA. The certificates are pre-installed on the OS in `/etc/rauc/keyring.pem`.
|
||||
@ -92,4 +94,4 @@ However, Home Assistant Operating System isn't a locked down platform. It uses t
|
||||
# systemctl restart rauc
|
||||
```
|
||||
|
||||
With this change, a local build can be installed. Installing an official update from a locally built OS is still possible, since the self-signed certificate is appended to the keychain. Meaning the official release certificates are still accepted even for a local build. This allows updating to an official release from a local development build.
|
||||
With this change, a local build can be installed. Installing an official update from a locally built OS is still possible, since the self-signed certificate is appended to the keychain. Meaning the official release certificates are still accepted even for a local build. This allows updating to an official release from a local development build.
|
||||
|
Loading…
x
Reference in New Issue
Block a user