Every flavor now boots with something. Both the GUI and the headless assets ship a working default hopos.cfg — one edit required (hopos.apikey), then boot:
- GUI: a ready-made desktop — display, launcher and the app catalog straight from the hop-os-surf rolling release, no addresses to fill in.
- Headless: a bare node waiting for work over the HOP API, with commented
hopos.init[]lines in the template to seed your own baseline.
Editing that file on the FAT partition is node management: no shell, no rebuild. The Pi 4 gains the same initramfs hopos.cfg boot recipe as the Pi 5 (full JSON job specs, no bootargs size limit).
Prebuilt, signed boot images — https://gethop.org/hopos/ for the 5-minute quickstart.
- BOOTAA64.EFI + hopos.cfg — any UEFI arm64 box: EFI to
EFI/BOOT/, config in the stick root - hopos-rpi5.zip / hopos-rpi4.zip — unzip onto the SD bootfs (config included)
*-headless— the same images with zero GUI code linked;hopos-headless.cfgis their config template. For UEFI, renameBOOTAA64-headless.EFItoBOOTAA64.EFIon the stick.
Verify: ssh-keygen -Y verify -f allowed_signers -I hello@gethop.org -n gethop-release -s SHA256SUMS.sig < SHA256SUMS && shasum -a 256 -c SHA256SUMS