// OPENBSD · THE DARK SIDE OF UNIX

OpenBSD 7.9: from USB to first login

A friendly, careful install of OpenBSD 7.9, from official download to the first blinking cursor. Designed for a spare PC or virtual machine.

Before you install: keep your working disks safe

Welcome to the OpenBSD 7.9 side of the DarkPC universe. OpenBSD 7.9 was released on 19 May 2026. We'll install it with the standard text-mode installer on a conventional 64-bit Intel/AMD (amd64) computer. Commands and prompts may differ on other hardware or future releases.

DarkPC's safest route: use a virtual machine or a dedicated spare computer with an empty drive. If your existing computer already runs Windows and Slackware, do not select that drive for this tutorial. This guide does not cover a complex multi-boot arrangement or drive resizing.

// STOP · YOUR DATA MATTERS

The OpenBSD installer can permanently overwrite the selected disk. Back up important files to a separate physical device, verify the backup, and identify the installation target by model and size. If you cannot confidently distinguish the target disk from the USB installer or existing system drive, cancel the installation.

Bring along

  • A spare amd64 PC or VM with a dedicated empty virtual disk. For a comfortable learning machine, allow considerably more than the 8 GB minimum suggested by the OpenBSD FAQ.
  • A spare USB stick, or a VM that can mount the installer image.
  • A working keyboard and display; wired Ethernet is easiest while you learn.
  • A strong password and a plan for the normal (non-root) user account.

OpenBSD is its own complete operating system, not a Linux distribution. Part of the fun is discovering what is familiar and what is deliberately different.

1 · Get OpenBSD 7.9 from the source

Visit the official installation FAQ and the amd64 downloads page. From an official OpenBSD mirror, obtain the right image for your installation:

FileWhat it isGood for
install79.imgUSB disk image with installation file sets included.Recommended for a USB-based first install.
miniroot79.imgSmaller USB image; downloads installation sets separately.A connected machine with reliable networking.
install79.isoCD/DVD image with installation sets.Optical media, or a virtual machine if supported by its configuration.

For a USB stick, choose install79.img. For a VM, attaching an install79.iso as a virtual optical drive is often easiest. Use the amd64 downloads for a typical modern Intel or AMD PC; don't mix these up with arm64 images.

2 · Verify the download before writing it

Download the corresponding SHA256 checksum file from the same mirror directory and check the exact image you downloaded. On Slackware/Linux with GNU coreutils:

sha256sum install79.img
# Compare this digest with the install79.img entry in the official SHA256 file.

On an OpenBSD computer you can use:

sha256 -C SHA256 install79.img

For an authenticity check, use SHA256.sig plus OpenBSD's signify and the official openbsd-79-base.pub public key, using the key location appropriate for your system. The official FAQ documents the signature-verification process. A matching plain checksum detects corruption but is not equivalent to signature verification.

// A NOTE ABOUT INSTALL FILE SETS

An installer booted from a verified install79.img may report that its included sets have no separate SHA256.sig. This is documented in the official FAQ. Proceed only when you have verified the authenticity of the image beforehand; do not blindly dismiss verification warnings.

3 · Create your OpenBSD installation USB

On Windows, use a reputable utility that can write a raw disk image to USB. A normal file copy to a formatted USB drive will not make it bootable. Choose the USB stick by its displayed capacity, and remember that writing an image erases everything on it.

On Linux, a graphical disk-image writer is simpler for beginners. If you already understand dd, you can use the procedure below—but only after identifying the destination beyond doubt:

lsblk -o NAME,SIZE,MODEL,TRAN
# Identify your USB drive by model and capacity.
# STOP: replace /dev/sdX ONLY with your verified entire USB device.
sudo dd if=install79.img of=/dev/sdX bs=4M status=progress conv=fsync
sync

Never paste /dev/sdX literally. The output path must be the whole USB drive, not a partition and not your Windows/Slackware SSD. If unsure, use the graphical writer instead.

For a VM with install79.iso, attach the ISO to the virtual optical drive. There is no USB creation step in that case.

4 · Boot and meet the text-mode installer

  1. Boot the spare computer from your prepared USB, or boot your VM from the attached ISO. Your PC's firmware boot menu often uses F12, F11 or Esc.
  2. The OpenBSD boot sequence will print hardware-detection messages.
  3. At the installer prompt, choose I for Install rather than Upgrade, Autoinstall or Shell.
  4. Work through the prompts for keyboard layout, hostname (for example openbsd-lab) and network. Accepting a sane default is generally easiest for a beginner.
Welcome to the OpenBSD/amd64 7.9 installation program.
(I)nstall, (U)pgrade, (A)utoinstall or (S)hell? i

If an option looks unfamiliar, read its question before hitting Enter. You can consult the official simple installation walkthrough on your phone or another computer.

5 · Networking, passwords and normal user

When a wired interface is offered, DHCP is an easy first choice on a normal home network. Wireless hardware may need firmware: if Wi-Fi is your only connection, consult the OpenBSD FAQ section on bootstrapping firmware before proceeding.

Set a strong root password, and create a separate normal user for everyday computing. During installation, OpenBSD can ask about allowing root logins via SSH; leave remote root login disabled. Do not expose SSH to the internet simply to complete a tutorial.

Depending on the answers and version, the installer may ask about time zone, X Window System, whether to run the graphical display manager, and enabling sshd. You can choose to keep the computer console-first and enable a graphical desktop later. For a machine not intended for remote access, there is no need to enable sshd.

6 · Pick the correct disk and the automatic layout

This is the step where care matters most. The installer may list disks with names such as sd0, sd1 or wd0. Disk names are examples, not reliable IDs: the USB may also appear in that list. Check the available size and identity of the target device against the dedicated empty disk you prepared.

For an OpenBSD-only lab disk, choose the option that uses the whole selected target disk, then choose the automatic disk layout to start. OpenBSD commonly creates multiple FFS partitions for areas such as /, /home, /usr and /var. That is normal and intentional.

// DESTRUCTIVE STEP · RECHECK THE DISK

A whole-disk installation destroys the previous contents of the selected disk. Do not use it on the drive holding Slackware, Windows or any files you want to keep. An existing multi-boot setup requires its own separate plan.

On a UEFI PC, the installer can handle appropriate boot arrangements for a dedicated disk. Avoid manually changing partition tables or boot loaders on your working PC unless you know precisely what you are doing.

7 · Install the official file sets

OpenBSD installs its operating system from signed release file sets, not from pkg_add packages. The names in 7.9 include:

File setPurpose
bsd, bsd.mp, bsd.rdKernel files / installation ramdisk (where applicable).
base79.tgzBase operating system.
comp79.tgzCompilers, headers and libraries.
man79.tgzThe manual pages. Excellent reading material.
game79.tgzTraditional text-mode games.
xbase79.tgz, xfont79.tgz, xserv79.tgz, xshare79.tgzX11-related utilities, fonts, libraries and documentation.

Install all sets for your first machine, as OpenBSD recommends. Even a mainly text-mode user may need libraries from the X-related sets. Select the local installation source if your install79.img includes the sets, or choose a trustworthy official mirror when installing over the network.

Let the installer complete and reboot. Remove the USB stick (or detach the VM ISO) so the newly installed system boots from its own disk.

8 · Your first OpenBSD login

Log in as the normal user you created. Open a console or terminal and try these harmless checks:

uname -a
sysctl kern.version
id
pwd
ls -la
df -h
man hier

uname and sysctl identify the system; man hier teaches you the file hierarchy. OpenBSD's tmux is part of the base system, so you can launch it without installing a separate package:

tmux
# Press Ctrl-b, then d to detach; reattach with: 
tmux attach

For more, jump straight into our OpenBSD Terminal Survival Guide.

9 · Patch the base system, update firmware and packages

Maintenance is deliberately split into different tools. syspatch applies base-system fixes on supported official releases. fw_update finds firmware for supported hardware. pkg_add -u updates installed third-party packages. These are not synonyms.

Run administrative commands as root, or configure and use doas as described in the next section. Here is a safe, readable sequence for the root account:

# After logging in as root for system maintenance:
syspatch
fw_update
pkg_add -u

Follow prompts; reboot if base-system patch instructions require it. For a newer major OpenBSD release, sysupgrade is a separate process. Always read the official upgrade guidance and take a backup before moving to a new release. Never run a major upgrade merely because a command is mentioned in a guide.

10 · Make it your own: doas and console software

OpenBSD uses doas for controlled privilege escalation. It does not automatically grant every account permission to administer the system. Confirm your groups with id, and read man doas.conf before configuring /etc/doas.conf as root. Follow least-privilege principles; never use a blanket passwordless rule from a random forum.

Once you have a working network and appropriate administrative access, the following commands install some familiar console tools as root:

pkg_add irssi neomutt links
# Check installed packages:
pkg_info

Package names and availability may vary with mirror and architecture. Use pkg_info -Q searchterm to browse the available repository first. tmux is already in OpenBSD's base system. If your terminal is your happy place, you are right at home.

Troubleshooting and official documentation

ProblemWhat to investigate
USB not bootingCheck the image is appropriate for your architecture and was written as a raw image. Review your system firmware boot settings.
No networkCheck ifconfig, cabling and DHCP; Wi-Fi may require firmware support.
Wrong disk shownStop. Power off and identify the target device before touching disk layout.
Package install failsCheck connection, official package mirrors and your OpenBSD release.
Need graphical softwareThe standard install includes X-related sets; choose a desktop later rather than risking your first install.

OpenBSD's own documentation is exceptional. Go straight to the source:

DarkPC guide reviewed 16 October 2026 against OpenBSD's official 7.9 documentation. This is an instructional walkthrough, not a claim that a real installation was tested on your hardware.

Official references and further reading