Skip to content

EmiBSD 2026.11 (pre-release)

Pre-release
Pre-release

Choose a tag to compare

View all tags
@enavarre-cl enavarre-cl released this 06 Nov 11:40
· 28 commits to main since this release
2026.11
6396276

The first EmiBSD release, for arm64, as a pre-release: the install media install EmiBSD in
QEMU and the installed system boots to login:; it has not yet been compared with a real
OpenBSD (diff-openbsd, step 5 of the checklist).

Not for production. EmiBSD is an experiment. It runs only in QEMU, and its crypto,
network and storage code is unaudited.

The media

  • emibsd-2026.11-arm64-install.iso: for QEMU and VMs; cd9660 with an EFI El Torito image.
  • emibsd-2026.11-arm64-install.img: a USB stick image, laid out as OpenBSD's arm64 install80.img.
  • SHA256: the sums of both.

Both carry the sets, so the install needs no network. How to run it in QEMU, step by step:
README.

V=2026.11
U=https://github.com/EmiBSD/OS/releases/download/$V
curl -fLO $U/emibsd-$V-arm64-install.iso -fLO $U/SHA256 &&
  shasum -a 256 --ignore-missing -c SHA256

What it assembles

Pin
Kernel release 20261106-ac41e133: bsd.mp, bsd.RAMDISK, BOOTAA64.EFI
Userland release 2026.11.1: the base80, comp80, game80 and man80 sets (.tar.zst), miniroot80.fs, INSTALL.arm64
DevTools 63830d2c63c4: LLVM 23.1.4, Rust 1.99.1 (the toolchains the others were built with)
OpenBSD 3ce1f3f79392, the pin Kernel, Userland and LandingZone share

unsafe in Kernel at the pin (cargo xtask unsafe-report at 51acd8f5, the pin's parent with
the same crates): kernel 0, abi 0, hal 194, bsd 8897.

Checked

  • just check, just fetch, just smoke: the pins exist and match their sums; the released kernel boots.
  • just media twice from the manifest commit: the same SHA256 for both images.
  • just smoke-media: each image installs all four sets onto a fresh disk in QEMU virt
    (EDK2, cortex-a72), and the installed disk boots alone to login:; uname -a gives
    EmiBSD emibsd.my.domain 8.0 GENERIC#1744 arm64.

Known gaps

  • No diff-openbsd yet: the installed system has not been compared with a real OpenBSD.
  • The comp set has no cc, ld or ar yet (DevTools' T3), so reorder_libs, the
    ssh-agent relink and reorder_kernel fail at boot, without harm.
  • /etc/motd still names the base system's old name; /usr/libexec/vi.recover is missing.
  • ISO installs print newfs_msdos: /dev/r0000000000000000.i: No such file or directory
    during disk setup: OpenBSD 8.0 prints the same line with a CD attached; the install is not affected.
  • Tested only in QEMU's virt machine; real hardware is untried.
  • arm64 only; amd64 waits for Kernel's N10.
Assets 5
Loading