OpenBSD 8.0

Original Article ↗ Hacker News Discussion ↗

OpenBSD 8.0’s release prompts both enthusiasm for the operating system’s steady evolution and debate over its AI‑satire themed artwork, which parodies machine‑generated “slop” and nods to The Simpsons. Commenters highlight OpenBSD’s strengths—predictable upgrades via `sysupgrade`, strong security features like `pf`, `pledge`, and `unveil`, excellent manuals, and reliable support on older Lenovo hardware—while comparing it favorably to increasingly complex Linux distributions. Technical notes touch on SMP networking improvements, multiprocessor support in the hypervisor, toolchain choices like Clang/LLVM, filesystem limitations, and growing (though hardware‑dependent) support for Intel and Apple Silicon Macs.

Release artwork and AI satire

  • Many dislike the 8.0 “blowfish on bike” graphic, calling it ugly or “slop-like.”
  • Others see it as deliberate satire of AI‑generated images and tech culture, including references to pelican benchmark memes and self‑sabotage bicycle memes.
  • Some appreciate the irreverent, anti‑polished aesthetic, arguing OpenBSD has long embraced deliberately offbeat visuals.

Release song and Simpsons theme

  • The release song “The Simps on AI” is widely praised as funny and on‑theme.
  • Numerous Simpsons references are noted (three‑eyed fish “Blinky,” reversed-name gag), reinforcing that the artwork and song form a cohesive parody of AI and pop culture.

Upgrade process vs. Linux

  • The doas sysupgrade → reboot → sysmerge → pkg_add -u workflow is lauded as simple and consistent across releases; some mention also running syspatch.
  • Comparisons with Debian/Ubuntu/Fedora/Arch upgrades spark debate:
    • Some claim Linux upgrades are as simple or simpler.
    • Others note that full distro upgrades (e.g., Debian release jumps) are more involved, whereas OpenBSD’s guided release upgrades feel quicker and less fragile.

Performance and SMP / VMM

  • Interest in benchmarks for SMP networking and overall performance improvements in 8.0.
  • Some links to community benchmarks are shared; anecdotal reports mention smoother audio and system load on older hardware.
  • Multi‑processor support for the hypervisor (VMM/VMD) is highlighted as a major feature.

Hardware support and laptops/Macs

  • Multiple users report smooth multi‑release upgrades on older Lenovo laptops and praise suspend, radios, and general reliability.
  • Discussion of running OpenBSD on Intel Macs points to rEFInd and T2‑chip hurdles; experiences are mixed/unclear.
  • OpenBSD reportedly supports M1/M2, though details in the thread are sparse.

Filesystems, browsers, and toolchain

  • OpenBSD uses FFS/FFS2; more advanced filesystems like ZFS/btrfs are seen as unlikely due to licensing.
  • A porting effort for GeFS is mentioned; seen as promising but not yet mainstream.
  • Firefox ESR is favored due to better -stable backporting; Chromium variants may lag in security updates.
  • Ancient GCC/binutils in base are noted; others respond this is outdated since Clang/LLVM is now standard.

Stability, Unix “feel,” and usability

  • Long‑term users emphasize that OpenBSD feels like “classic Unix”: small, coherent base system, minimal background daemons, predictable releases (roughly every six months).
  • pf, consistent high‑quality man pages, pledge/unveil, and straightforward service management are frequently praised.
  • Some say it’s ideal for bastion hosts, routers, and “set‑and‑forget” systems, though not everyone uses it as a daily desktop.

Security and cryptography

  • The changelog note about switching ssh’s fallback ed25519 implementation from SUPERCOP to libsodium is highlighted as a subtle but meaningful crypto change, with better strictness checks and API ergonomics.

AI “slop” and cultural commentary

  • Thread contains broader anxiety about AI‑generated “slop” diluting software and art.
  • Some argue human work is more interpretable and reliable; others counter that “reliable human-made stuff” is romanticized.
  • OpenBSD’s theme this release is widely interpreted as commentary on outsourcing thinking to machines and tech self‑destruction, though exact intent remains somewhat ambiguous.