Repository navigation
Building OOS
How to build the kernel, choose a signing key and build the image, on macOS or Linux. You need Rust with the aarch64-unknown-linux-musl target
and Docker: see You will need.
Download linux-6.12.115-base.tar.xz from the releases into kernel/src/
(kernel/README.md), then:
kernel/build-base.sh # in Docker, 5-30 minutes depending on the machine, result in kernel/out/baseYou only have to repeat this when the kernel changes.
Update packages must be signed with this project's release key (id 5b293adb4389dc84). Builds from this
repository trust only that key, listed in keys/update.pub; the upstream maintainer and former public community
keys are not trusted. The secret release key is kept outside the repository.
The image build never signs. Select the secret seed with --key FILE or OOS_SIGNING_KEY; --key takes precedence.
Signing requires one of these explicit selections. Keep the secret key outside the repository,
back it up and never publish it. Details:
docs/update.md.
These paths use the default target directory. Set CARGO_TARGET_DIR to select
another directory inside this worktree, and use its image/ directory below.
See the output contract.
boot/build-dev-image.sh
boot/sign-dev-image.sh --key /path/to/signing.key
boot/build-gel.pyThese separate steps produce target/image/oos-dev.img for the card, target/image/oos-dev.oosupd, the signed
update package, and target/image/DHO800_DHO900_OOS_Install.GEL for the USB stick. Signing and packaging verify
build receipts before consuming these local artifacts.
The kernel, the key and the image on Linux, here with Debian or Ubuntu, on an ordinary x86-64 PC as well as on arm64. On x86-64:
- the kernel and
oos-hware cross-compiled with Ubuntu'sgcc-aarch64-linux-gnuinside the build container; you install no cross compiler yourself, - the Rust programs are cross-compiled by rustup's
aarch64-unknown-linux-musltarget andrust-lld, - busybox, wpa_supplicant and e2fsck come from arm64 containers, which run through QEMU (the
binfmtline below).docker run --rm --platform linux/arm64 alpine:3.22 uname -mprintsaarch64when that works.
Run everything as yourself, not with sudo.
sudo apt install docker.io git python3 curl
sudo usermod -aG docker $USER # then log out and in again, so that docker runs without sudo
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh # Rust from rustup, not from apt
rustup target add aarch64-unknown-linux-musl
# x86-64 only: arm64 containers through QEMU, for busybox, wpa_supplicant and e2fsck (again after a reboot)
docker run --privileged --rm tonistiigi/binfmt --install arm64
git clone https://github.com/yottabytesolutions/oos.git && cd oos
mkdir -p kernel/src
curl -fL -o kernel/src/linux-6.12.115-base.tar.xz \
https://github.com/yottabytesolutions/oos/releases/latest/download/linux-6.12.115-base.tar.xz
kernel/build-base.sh
boot/build-dev-image.shThe scripts say what is missing before they start: Docker not reachable, no rustup or no target, no arm64 containers.
On x86-64 the first build takes longer than on arm64, mostly for wpa_supplicant and e2fsck under QEMU; they are built
once. A finished build leaves the same files as on macOS. The workflow .github/workflows/image.yml builds on arm64
and on x86-64 for every release and compares the kernel, the DTB and the files inside the image of the two. CI publishes unsigned images; sign and package them offline with the project release key. To install them on a second card from Linux, see
Install on a second card, with /dev/sdX for the card.
This wiki is generated from wiki/ in the repository; propose changes with a pull request.