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.

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

Merge upstream docs #105

Merged
merged 2 commits into from
Dec 18, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ endif::[]
== OSTree


link:http://ostree.readthedocs.io/en/latest/[OSTree] is an open-source tool that combines a "git-like" model for committing and downloading bootable filesystem trees, along with a layer for deploying them and managing the bootloader configuration. It is actively developed and support by Red Hat, and used in link:http://flatpak.org/[flatpak] and link:https://github.com/projectatomic/[Project Atomic].
link:https://ostreedev.github.io/ostree/[OSTree] is an open-source tool that combines a "git-like" model for committing and downloading bootable filesystem trees, along with a layer for deploying them and managing the bootloader configuration. It is actively developed and support by Red Hat, and used in link:http://flatpak.org/[flatpak] and link:https://github.com/projectatomic/[Project Atomic].

For more on why OSTree is the best tool for the job of doing embedded device updates, you can also jump straight to xref:comparing-full-filesystem-update-strategies.adoc[Comparing full-filesystem update strategies].

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ NOTE: If you don't want OTA Connect to issue your device certificates, you can a

== Building the image

The way OTA Connect does full-filesystem updates is unique, and offers xref:ostree-and-treehub.adoc#_comparing_full_filesystem_update_strategies[significant benefits over other systems]. OTA Connect makes use of link:http://ostree.readthedocs.io/en/latest/[libOSTree] to store the whole filesystem in a git-like repository (content-addressed object store). File objects in the repository are then hardlinked into their place in the filesystem at boot time by a specially configured boot loader.
The way OTA Connect does full-filesystem updates is unique, and offers xref:ostree-and-treehub.adoc#_comparing_full_filesystem_update_strategies[significant benefits over other systems]. OTA Connect makes use of link:https://ostreedev.github.io/ostree/[libOSTree] to store the whole filesystem in a git-like repository (content-addressed object store). File objects in the repository are then hardlinked into their place in the filesystem at boot time by a specially configured boot loader.

When you do a Yocto build integrating our open-source link:https://github.com/advancedtelematic/meta-updater[meta-updater] layer, you get two different artifacts:

Expand Down
2 changes: 1 addition & 1 deletion scripts/test.sh
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ TEST_TESTSUITE_EXCLUDE=${TEST_TESTSUITE_EXCLUDE:-}
TEST_PKCS11_MODULE_PATH=${TEST_PKCS11_MODULE_PATH:-/usr/lib/softhsm/libsofthsm2.so}
# note: on Ubuntu bionic, use /usr/lib/engines/engine_pkcs11.so on xenial
TEST_PKCS11_ENGINE_PATH=${TEST_PKCS11_ENGINE_PATH:-/usr/lib/x86_64-linux-gnu/engines-1.1/libpkcs11.so}

git config --global --add safe.directory /home/runner/work/aktualizr/aktualizr
# Build CMake arguments
CMAKE_ARGS=()
CMAKE_ARGS+=("-G$TEST_CMAKE_GENERATOR")
Expand Down
Loading