OpenBSD 7.9 ships as the project's 60th release; guide details the 7.8 upgrade path

OpenBSD 7.9 arrives as the project's 60th release

The OpenBSD project shipped version 7.9 of its operating system on 19 May 2026, according to upgrade walkthroughs published on dev.to in both English and Japanese. The release is the project's 60th, and the guides — which follow OpenBSD's official upgrade documentation — describe moving a 7.8 machine to 7.9 with a single command plus a short list of pre-flight checks and follow-up tasks.

Pre-upgrade checks

The guides open with the points the official tutorial groups under its pre-upgrade section:

• Disk space: the /usr partition needs at least 1.1 GB free, checked with df -h.
• Compatibility: read the release's configuration and syntax changes and its list of special packages. This cycle includes a major PostgreSQL update to 18.1, and the special-packages list also names aide, caddy, exim, icinga, lldpd and puppet.
• Backups: optional, but worth taking where the machine holds data you cannot lose.

Customisation is possible but skippable. As the autoinstall manual page quoted in the guides explains, an /auto_upgrade.conf response file on the installer's built-in RAM disk makes autoinstall behave as if the machine were netbooted while using local answers. The author's example deselects the X sets except xbase and drops the games set; an /upgrade.site script offers another hook.

One command, two reboots

The upgrade itself is doas sysupgrade, with one warning attached: once started, it cannot be interrupted. It fetches the signed 7.9 sets from the project CDN, verifies them, pulls updated firmware — an update for Intel's vmm firmware in the author's log — and reboots to install. A second reboot follows, sysmerge runs automatically, daemons such as sshd come up as usual, and the boot process checks for pending binary patches. A successful login lands on a banner reading "OpenBSD 7.9 (GENERIC.MP)".

Post-upgrade: sysmerge, syspatch, packages

Some configuration files cannot be modified automatically, so the guides recommend running doas sysmerge afterwards; /etc/login.conf is the file flagged this time. The walkthrough covers the interactive prompts: delete the temporary file and keep the current one, install the new file over it, or merge the two interactively — choosing the left or right side at each difference, then editing, installing or reviewing the merged result.

Two routine maintenance commands follow. doas syspatch installs the binary patches OpenBSD issues as needs are identified, and doas pkg_add -u updates every installed package. On the latter, the author's advice is to read the output carefully, especially the tail, where notes about important changes or required actions can appear; they also verify their default shell still starts, having once seen it break after a Python update. The release's ports highlights reportedly include further work on VMM/VMD.

The closing steps are short: apply any configuration and syntax changes, remove files the official tutorial lists as obsolete (there are none this cycle), check whether any installed package is on the special-packages list and follow its instructions — PostgreSQL's major version jump being the most likely to bite — and optionally reboot.

Why it matters

OpenBSD's regular releases and compact upgrade tooling are central to its reputation for dependability: the sets are signed and verified, and the whole release jump is reachable through one command. The 60th release milestone underlines how long that process has kept running. For administrators, the practical takeaways from the walkthrough are modest but real — check /usr space first, read the special-packages list before upgrading if PostgreSQL is in play, and do not start sysupgrade unless the machine can be taken through its reboots. Guides like these add value because the official documentation, while thorough, leaves the sequencing to the reader; a tested end-to-end path with real command output shortens the jump for everyone else.