Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs: Describe /boot/ostree #3258

Merged
merged 1 commit into from
May 30, 2024
Merged

docs: Describe /boot/ostree #3258

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions docs/atomic-upgrades.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Copy link
Member

@travier travier May 30, 2024 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's kernel + initramfs (in this order) from a quick test

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

and maybe other files for other architectures.

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.
Loading