OK, so who broke #syspatch in #OpenBSD 7.8?

```
# syspatch
syspatch: Unsupported release: 7.8-current
```

Start your syspatch engines!

006: RELIABILITY FIX: January 10, 2025 All architectures

Traffic sent over wg(4) could result in kernel crash.

https://www.openbsd.org/errata76.html

#RUNBSD #OpenBSD #syspatch #upgrade

OpenBSD 7.6 Errata

the OpenBSD errata page

When the question comes up, "Why OpenBSD?" one answer is ease of maintenance.

Patches are announced on the OpenBSD.org website at https://www.openbsd.org/errata76.html and on the openbsd.announce mailing list https://marc.info/?l=openbsd-announce&r=1&w=2

All you do to update is:

$ doas syspatch

It's very quick.

And for packages, it's:

$ doas pkg_add -u

And for a new release, which happens twice a year:

$ doas sysupgrade

(followed by doas pkg_add -u)

So easy!

#openbsd #syspatch

OpenBSD 7.6 Errata

the OpenBSD errata page

I just applied the latest OpenBSD 7.6 patch. Also had (yet another) Intel firmware update.

https://marc.info/?l=openbsd-announce&m=173160609919262&w=2

#OpenBSD #syspatch

'OpenBSD Errata: November 15, 2024 (expat)' - MARC

Valuable News โ€“ 2024/09/09

The Valuable News weekly series is dedicated to provide summary about news, articles and other interesting stuff mostly but not always related to the UNIX/BSD/Linux systems. Whenever I stumble uponโ€ฆ

๐šŸ๐šŽ๐š›๐š–๐šŠ๐š๐šŽ๐š—
You Have Installed OpenBSD. Now For The Daily Tasks.

You Have Installed OpenBSD. Now For The Daily Tasks.

You Have Installed OpenBSD. Now For The Daily Tasks.

Aaand patched #openbsd. #syspatch time!