OpenBSD Journal

Errata and (First) Binary Patches Announced

Contributed by rueda on from the patch me cos you can dept.

Errata for OpenBSD 6.1 and 6.0 have been announced. The message to announce@openbsd.org [from T.J. Townsend (tj@)] reads:

Errata patches for dhcpd, vmm, LibreSSL and softraid have been released
for OpenBSD 6.1 today.

Details can be found on this page: https://www.openbsd.org/errata61.html

Binary updates for the amd64 and i386 platforms are also available via
the syspatch utility. Note that syspatch uses the mirror configured in
/etc/installurl, so all mirrors may not have the files yet.

OpenBSD 6.0 is only affected by the softraid issue.

A patch for it can be found here: https://www.openbsd.org/errata60.html

It's time to get (sys)patching!

Update

In a follow-up email, Antoine Jacoutot (ajacoutot@) wrote:

Due to a mistake in creating the syspatch archives, a multi-processor machine
would not default to the MP kernel. New syspatches have been re-rolled and
you're advised to revert and re-apply them (even on non-MP machines). Make sure
your mirror (/etc/installurl) has the new syspatches first (dated May 3rd).

As root:
   while true; do syspatch -r || break; done
   syspatch

If you're running on a multi-processor machine, you may also remove the extra
/bsd.mp kernel. Sorry about that and thank you all for your report and feedback.

(Comments are closed)


  1. By Renaud Allard (renaud) renaud@allard.it on

    syspatch works quite fine, but, beware, after a kernel upgrade, if you renamed bsd.mp to bsd because you have a multiprocessor machine and the installer did it, your "new" bsd will be the bsd.sp, so you will reboot in single processor mode.

    1. By Matt M. (165.234.0.138) on

      > syspatch works quite fine, but, beware, after a kernel upgrade, if you renamed bsd.mp to bsd because you have a multiprocessor machine and the installer did it, your "new" bsd will be the bsd.sp, so you will reboot in single processor mode.

      a mail thread on the subject https://www.mail-archive.com/misc@openbsd.org/msg153424.html

    2. By Renaud Allard (renaud) on

      > syspatch works quite fine, but, beware, after a kernel upgrade, if you renamed bsd.mp to bsd because you have a multiprocessor machine and the installer did it, your "new" bsd will be the bsd.sp, so you will reboot in single processor mode.

      New syspatches have been re-rolled and you're advised to revert and re-apply them (even on non-MP machines). Make sure your mirror (/etc/installurl) has the new syspatches first (dated May 3rd).

      As root:
      while true; do syspatch -r || break; done
      syspatch

  2. By Noryungi (noryungi) noryungi@yahoo.com on

    I was actually expecting this!

    Running syspatch took less than one minute, and installed everything quickly and neatly.

    An especially nice touch is the ''rollback'' file, ready to be used, just in case!

    Kudos to Antoine Jacoutot for a great utility!

  3. By Anonymous Coward (68.100.56.160) on

    The issue still exists for me. The patch files have both bsd and bsd.mp. I'm not sure what's supposed to mv /bsd.mp /bsd on MP machines.

    1. By s (82.68.199.130) on

      > The issue still exists for me. The patch files have both bsd and bsd.mp. I'm not sure what's supposed to mv /bsd.mp /bsd on MP machines.

      You aren't expected to install the syspatch files manually. The install_kernel() function in /usr/sbin/syspatch does that.

      1. By Anonymous Coward (68.100.56.160) on

        > > The issue still exists for me. The patch files have both bsd and bsd.mp. I'm not sure what's supposed to mv /bsd.mp /bsd on MP machines.
        >
        > You aren't expected to install the syspatch files manually. The install_kernel() function in /usr/sbin/syspatch does that.

        Yeah, I was just using syspatch. It was user error. One machine would install the SP kernel even after reverting all the patches and reapplying. My other MP machines would syspatch with the MP kernel just fine. It turns out that on the first machine, I had built and installed the stable MP kernel by mistake before syspatching so I had it in my head that it was an MP machine. It isn't. syspatch just uses `sysctl -n hw.ncpufound` to determine whether to install SP or MP, not which kernel was installed before patching which seems reasonable.

Credits

Copyright © - Daniel Hartmeier. All rights reserved. Articles and comments are copyright their respective authors, submission implies license to publish on this web site. Contents of the archive prior to as well as images and HTML templates were copied from the fabulous original deadly.org with Jose's and Jim's kind permission. This journal runs as CGI with httpd(8) on OpenBSD, the source code is BSD licensed. undeadly \Un*dead"ly\, a. Not subject to death; immortal. [Obs.]