shaba/ostree
1
0
Fork 0
mirror of https://github.com/ostreedev/ostree.git synced 2024-12-21 13:34:34 +03:00
Code Issues Projects Releases Wiki Activity

docs: Describe /boot/ostree

Browse Source 
People get confused by the sha256 here being different
from the ostree commit hash.
This commit is contained in:
Colin Walters 2024-05-30 09:42:24 -04:00
parent b605230635
commit f63b751225
1 changed files with 16 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
docs/atomic-upgrades.md
View File

@ -142,3 +142,19 @@ so just like `/boot`, it has a version of `0` or `1` appended.
Each bootloader entry has a special `ostree=` argument which refers to
one of these symbolic links. This is parsed at runtime in the
initramfs.
## The /boot/ostree directory
There is also a `/boot/ostree` directory which is where ostree will
install kernel data (including the initramfs). In order to
deduplicate across deployments, the kernel state is hashed (again
with sha256), resulting in a directory like `/boot/ostree/<stateroot>-<checksum>`;
this is what the bootloader entries will use.
However, this is an implementation detail and may change in the
future. As a tool which wants to find kernel for a given root, instead look
in `/usr/lib/modules/$kver`; this is how OSTree itself finds
the kernel to "deploy" by copying it into `/boot`.
Note that if `/boot` is on the same partition as `/`, then OSTree
will just hardlink instead of copying.