Repository navigation

Releases

EmiBSD 2026.11.4 (pre-release, signed) Pre-release

Pre-release

enavarre-cl released this 09 Nov 03:46

2026.11.4

38b8290

The fifth EmiBSD release for arm64, signed, again a pre-release. It replaces
2026.11.3, whose ISO cannot be rebuilt
from its tag; the system it installs is the same. The install media install
EmiBSD in QEMU, the installer verifies the sets against the medium's signature, 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.

What changed since 2026.11.3

Reproducible again. 2026.11.3's ISO was made with a host makefs built at the previous
Userland pin, so its tag rebuilds another ISO (its .img and the sets' tree are the same).
This release's media are made with the pinned Userland's makefs, and OS's just media now
refuses a makefs built at another commit than the pin.
DevTools llvm-23.1.4+emibsd.4 and rust-1.99.1+emibsd.2: the target's C++ runtime is
shared, with the system's sonames (libc++.so.13.0, libc++abi.so.10.0). OS's host makefs
is the same with them; Userland's base will carry the two libraries once it builds with them.
Kernel 20261108-b99aedaf and Userland 2026.11.4 are as in 2026.11.3: the socket layer and
the socket system calls in the new kernel; a base built against that kernel's ABI headers.

The media

emibsd-2026.11.4-arm64-install.iso: for QEMU and VMs; cd9660 with an EFI El Torito image.
emibsd-2026.11.4-arm64-install.img: a USB stick image, laid out as OpenBSD's arm64 install80.img.
SHA256 and SHA256.sig: the sums of both, and their signature with emibsd-80-base
(keys/emibsd-80-base.pub,
RWR7BZgzESUf6vppLWNF/Q83e1OvjRIDJ4kNBtzh0gPMW889JsfGSjU3).

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

V=2026.11.4
U=https://github.com/EmiBSD/OS/releases/download/$V
curl -fLO $U/emibsd-$V-arm64-install.iso -fLO $U/SHA256 -fLO $U/SHA256.sig &&
  shasum -a 256 --ignore-missing -c SHA256
# with signify and the public key above:
signify -C -p emibsd-80-base.pub -x SHA256.sig emibsd-$V-arm64-install.iso

What it assembles

	Pin
Kernel	pre-release `20261108-b99aedaf`: `bsd.mp` and `bsd.RAMDISK`, with the ABI linked in; `BOOTAA64.EFI`
Userland	release `2026.11.4`, signed: the `base80`, `comp80`, `game80` and `man80` sets (`.tar.zst`), `miniroot80.fs`, `INSTALL.arm64`
DevTools	`a677d16bb3bb`, `llvm-23.1.4+emibsd.4`; Rust `1.99.1+emibsd.2`
OpenBSD	`3ce1f3f79392`, the pin Kernel, Userland and LandingZone share

Checked

just check, just fetch, just smoke: the pins exist and match their sums, Userland's
signature verifies, the released kernel boots.
just media twice from the manifest commit: the same images and the same SHA256.sig.
just smoke-media: each image installs all four sets onto a fresh disk in QEMU virt
(EDK2, cortex-a72), the installer reports Signature Verified, and the installed disk boots
alone to login:; uname -a gives EmiBSD emibsd.my.domain 8.0 GENERIC#1900 arm64
(ISO: install 158 s, boot 49 s; stick: install 104 s, boot 49 s).

Known gaps

No diff-openbsd yet: the installed system has not been compared with a real OpenBSD.
The kernel's network smokes run at Kernel's N6 close; this kernel has not been through it.
The comp set has no cc, ld or ar yet (Userland's comp, with DevTools' native
toolchain, T3b), so reorder_libs and the ssh-agent relink fail at boot, without harm.
reorder_kernel fails at boot without a kernel.tgz (Kernel's and Userland's), without harm.
Network installs and sysupgrade from the mirror are untested; the media install from local sets.
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 6

EmiBSD 2026.11.3 (pre-release, signed) Pre-release

Pre-release

enavarre-cl released this 09 Nov 00:08

2026.11.3

38772e5

Superseded by 2026.11.4. This release's ISO was made with a host makefs built at the previous Userland pin, so its tag rebuilds another ISO; its .img and the sets are reproducible. 2026.11.4 installs the same system.

The fourth EmiBSD release for arm64, signed, again a pre-release: the install media install
EmiBSD in QEMU, the installer verifies the sets against the medium's signature, 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.

What changed since 2026.11.2

Kernel 20261108-b99aedaf: the mbuf (N6.1) and the socket layer (N6.2a: sockets, socket
buffers, domains, protocols, UNIX domain sockets with descriptor passing) are the new
kernel's, with the inherited code's call sites as adapters over them; the 19 socket system
calls are native (N6.2b), and the boot line reads abi: 331 syscalls, 189 native. A wg(4)
ordering fix. Built with DevTools llvm-23.1.4+emibsd.2.
Userland 2026.11.4: /usr/include takes the kernel ABI's headers from the Kernel
release; the build checks every system call against the kernel's MANUAL.toml; the manual
leaves out what this kernel lacks (section 9, the pages of absent system calls and of devices
the kernel does not configure, other architectures' man4, config(8)).
The mirror lists its directories: https://cdn.emibsd.org/ can be browsed down to the
sets like a web server's listing, and each set directory has the index.txt the installer
reads. This release's tree is on https://cdn.emibsd.org/pub/EmiBSD/8.0/arm64/ and kept as
pub/EmiBSD/releases/2026.11.3/arm64/.

The media

emibsd-2026.11.3-arm64-install.iso: for QEMU and VMs; cd9660 with an EFI El Torito image.
emibsd-2026.11.3-arm64-install.img: a USB stick image, laid out as OpenBSD's arm64 install80.img.
SHA256 and SHA256.sig: the sums of both, and their signature with emibsd-80-base
(keys/emibsd-80-base.pub,
RWR7BZgzESUf6vppLWNF/Q83e1OvjRIDJ4kNBtzh0gPMW889JsfGSjU3).

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

V=2026.11.3
U=https://github.com/EmiBSD/OS/releases/download/$V
curl -fLO $U/emibsd-$V-arm64-install.iso -fLO $U/SHA256 -fLO $U/SHA256.sig &&
  shasum -a 256 --ignore-missing -c SHA256
# with signify and the public key above:
signify -C -p emibsd-80-base.pub -x SHA256.sig emibsd-$V-arm64-install.iso

What it assembles

	Pin
Kernel	pre-release `20261108-b99aedaf`: `bsd.mp` and `bsd.RAMDISK`, with the ABI linked in; `BOOTAA64.EFI`
Userland	release `2026.11.4`, signed: the `base80`, `comp80`, `game80` and `man80` sets (`.tar.zst`), `miniroot80.fs`, `INSTALL.arm64`
DevTools	`832bb279392f`, `llvm-23.1.4+emibsd.2`; Rust `1.99.1+emibsd.1`
OpenBSD	`3ce1f3f79392`, the pin Kernel, Userland and LandingZone share

Checked

just check, just fetch, just smoke: the pins exist and match their sums, Userland's
signature verifies, the released kernel boots.
just media twice from the manifest commit: the same images and the same SHA256.sig.
just smoke-media: each image installs all four sets onto a fresh disk in QEMU virt
(EDK2, cortex-a72), the installer reports Signature Verified, and the installed disk boots
alone to login:; uname -a gives EmiBSD emibsd.my.domain 8.0 GENERIC#1900 arm64
(ISO: install 157 s, boot 49 s; stick: install 105 s, boot 47 s).

Known gaps

No diff-openbsd yet: the installed system has not been compared with a real OpenBSD.
The kernel's network smokes run at Kernel's N6 close; this kernel has not been through it.
The comp set has no cc, ld or ar yet (Userland's comp, with DevTools' native
toolchain, T3b), so reorder_libs and the ssh-agent relink fail at boot, without harm.
reorder_kernel fails at boot without a kernel.tgz (Kernel's and Userland's), without harm.
Network installs and sysupgrade from the mirror are untested; the media install from local sets.
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 6

EmiBSD 2026.11.2 (pre-release, signed) Pre-release

Pre-release

enavarre-cl released this 08 Nov 03:04

2026.11.2

935669e

The third EmiBSD release for arm64 and the first signed one, again a pre-release: the
install media install EmiBSD in QEMU, the installer verifies the sets against the medium's
signature, 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.

What changed since 2026.11.1

Signed. EmiBSD has its own signify keys. The medium's 8.0/arm64/SHA256 and this
release's SHA256 are signed with emibsd-80-base into SHA256.sig; the installer checks
the sets against it (Signature Verified) and no longer asks Continue without verification?.
The public key: keys/emibsd-80-base.pub,
RWR7BZgzESUf6vppLWNF/Q83e1OvjRIDJ4kNBtzh0gPMW889JsfGSjU3.
Userland 2026.11.3: the base system is OpenBSD's renamed EmiBSD at build time (messages,
manuals, URLs, contact addresses at emibsd.org); its binaries carry the ELF note name EmiBSD
and .emibsd.* sections; /etc/signify and the installer carry only EmiBSD's keys; the
installer finds its mirror list at ftplist1.emibsd.org through DNS.
Kernel 20261107-b2a15ba6: it accepts the ELF note name EmiBSD, which those binaries need.
DevTools llvm-23.1.4+emibsd.2: lld maps the .emibsd.* sections as the .openbsd.* ones.
The mirror: the release's 8.0/arm64/ tree is also on https://cdn.emibsd.org/pub/EmiBSD/8.0/arm64/,
and kept as pub/EmiBSD/releases/2026.11.2/arm64/.

The media

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

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

V=2026.11.2
U=https://github.com/EmiBSD/OS/releases/download/$V
curl -fLO $U/emibsd-$V-arm64-install.iso -fLO $U/SHA256 -fLO $U/SHA256.sig &&
  shasum -a 256 --ignore-missing -c SHA256
# with signify and the public key above:
signify -C -p emibsd-80-base.pub -x SHA256.sig emibsd-$V-arm64-install.iso

What it assembles

	Pin
Kernel	release `20261107-b2a15ba6`: `bsd.mp` and `bsd.RAMDISK`, with the ABI linked in; `BOOTAA64.EFI`
Userland	release `2026.11.3`, signed: the `base80`, `comp80`, `game80` and `man80` sets (`.tar.zst`), `miniroot80.fs`, `INSTALL.arm64`
DevTools	`832bb279392f`, `llvm-23.1.4+emibsd.2`; Rust `1.99.1+emibsd.1`
OpenBSD	`3ce1f3f79392`, the pin Kernel, Userland and LandingZone share

unsafe in Kernel (cargo xtask unsafe-report at d2107de6, the close of N6.0, one commit
before the pin): kernel 0, abi 0, hal 205, bsd 8825.

Checked

just check, just fetch, just smoke: the pins exist and match their sums, Userland's
signature verifies, the released kernel boots.
just media twice from the manifest commit: the same images and the same SHA256.sig.
just smoke-media: each image installs all four sets onto a fresh disk in QEMU virt
(EDK2, cortex-a72), the installer reports Signature Verified, and the installed disk boots
alone to login:; uname -a gives EmiBSD emibsd.my.domain 8.0 GENERIC#1827 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.
Network installs and sysupgrade from the mirror are untested; the media install from local sets.
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 6

EmiBSD 2026.11.1 (pre-release) Pre-release

Pre-release

enavarre-cl released this 07 Nov 23:52

2026.11.1

aadb9a6

The second EmiBSD release, for arm64, again 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.

What changed since 2026.11

Kernel 20261107-d2107de6: the ABI is linked into the kernel; abi_openbsd.ko is gone and
boot(8) no longer loads it. The system calls programs see are unchanged. 82 Kernel commits
over ac41e133, among them N5.9 (tmpfs and fuse) and N6.0 (the net lock and SMR in hal).
Userland 2026.11.2: base's /usr/mdec/BOOTAA64.EFI is that Kernel release's loader, the
same one the media boot from.

The media

emibsd-2026.11.1-arm64-install.iso: for QEMU and VMs; cd9660 with an EFI El Torito image.
emibsd-2026.11.1-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.1
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 `20261107-d2107de6`: `bsd.mp` and `bsd.RAMDISK`, with the ABI linked in; `BOOTAA64.EFI`
Userland	release `2026.11.2`: 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 d2107de6, the close of N6.0):
kernel 0, abi 0, hal 205, bsd 8825.

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#1826 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

EmiBSD 2026.11 (pre-release) Pre-release

Pre-release

enavarre-cl released this 06 Nov 11:40

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

EmiBSD 2026.11.4 (pre-release, signed)

What changed since 2026.11.3

The media

What it assembles

Checked

Known gaps

Uh oh!

EmiBSD 2026.11.3 (pre-release, signed)

What changed since 2026.11.2

The media

What it assembles

Checked

Known gaps

Uh oh!

EmiBSD 2026.11.2 (pre-release, signed)

What changed since 2026.11.1

The media

What it assembles

Checked

Known gaps

Uh oh!

EmiBSD 2026.11.1 (pre-release)

What changed since 2026.11

The media

What it assembles

Checked

Known gaps

Uh oh!

EmiBSD 2026.11 (pre-release)

The media

What it assembles

Checked

Known gaps

Uh oh!