In this commit, Paul Irofti (
pirofti@) added support for reading timecounters in userland without making a syscall.
In this commit, Paul Irofti (
Since we reported the first bits of powerpc64 support going into the tree on 16 May, work has progressed at a steady pace, resulting in snapshots now being available for this platform.
So, if you have a POWER9 system idling around, go to your nearest mirror and fetch this snapshot. Keep in mind that as this is still very early days, very little handholding is available - you are basically on your own.
In the following
(and a bunch of others), David Gwynne (
dlg@) imported most of the code submitted recently by Jason A. Donenfeld and Matt Dunwoodie to allow you to use WireGuard natively on OpenBSD:
Wesley Mouedine Assaby who runs the OpenBSD Jumpstart webpage with hints and tips for beginners about OpenBSD in general has produced a visualization of how PCs boot into OpenBSD.
I presented a talk on how I used OpenBGPd as a control plane for my ISP. I cover areas such as Routing fundamentals, a lightning introduction to BGP. An interesting aspect of the design is how the OpenBSD / OpenBGPd is used to control the routing information in my ISP yet the forwarding of packets is offloaded to hardware Layer 3 switches. I also outline my favourite new feature of OpenBGPd max prefix out which I'm sure will save my blushes if/when I fat finger my Prefix filters (although if my hair cut is anything to go by it is clear I have no shame anyway!). You can check out the talk here! Tom would welcome comments and feedback on the talk. I hope the talk will help others in deploying OpenBGPd and OpenBSD in their networks.
I would also suggest that those interested in learning more about OpenBGPd check out Peter Hessler's Tutorial on OpenBGPd which served as an essential aid in getting comfortable in configuring BGP on OpenBSD / OpenBGPd. Peter usually runs the Tutorial in advance of BSD Conferences.
I would like to give a big shout out to the people who write the code in OpenBSD and OpenBGPd, and that your effort makes my life running my network and ISP easier.
A huge word of thanks is due to Dan Langielle and the BSDCAN2020 Volunteers who organised the virtual BSDCAN 2020 conference this year in quite difficult circumstances.
Jonathan Gray (
jsg@) has just committed an update to the
DRM code to the tree.
This update brings support for newer AMD and Intel graphics parts.
Date: Sun, 7 Jun 2020 22:48:16 -0600 (MDT) From: Jonathan Gray <firstname.lastname@example.org> To: email@example.com Subject: CVS: cvs.openbsd.org: src CVSROOT: /cvs Module name: src Changes by: firstname.lastname@example.org 2020/06/07 22:48:16 Modified files: sys/arch/amd64/conf: Makefile.amd64 sys/arch/arm64/conf: Makefile.arm64 sys/arch/i386/conf: Makefile.i386 ... Log message: update drm to linux 5.7 adds kernel support for amdgpu: vega20, raven2, renoir, navi10, navi14 inteldrm: icelake, tigerlake Thanks to the OpenBSD Foundation for sponsoring this work, kettenis@ for helping, patrick@ for helping adapt rockchip drm and many developers for testing.
As is clear from Jonathan's commit message, this work was sponsored by the OpenBSD Foundation - it shows how your financial support of the foundation can directly improve (in this case) hardware support. Many thanks to Jonathan for working on this.
Otto Moerbeek (
posted to misc@
a useful summary of the state of play of FFS2
in the 6.7 release (and, to some extent, -current).
In his mail, Otto clarifies some things about the latest release:
In a commit touching quite a few files, Theo recently renamed the installation images from
Date: Sun, 17 May 2020 11:04:29 -0600 (MDT) From: Theo de Raadt <email@example.com> To: firstname.lastname@example.org Subject: CVS: cvs.openbsd.org: src CVSROOT: /cvs Module name: src Changes by: email@example.com 2020/05/17 11:04:29 Modified files: distrib/alpha/miniroot: Makefile distrib/amd64/iso: Makefile ... bin/dd : dd.1 usr.sbin/ldomctl: ldomctl.8 Log message: Change install images called *.fs to *.img. These are UFS filesystem images, but additionally have a bootblock in the first 8K (since UFS does not use that space). There are some UEFI direct-from-internet bootloaders that require the name *.img. So this makes things more convenient for those, while keeping it consistant in all architectures. ok kettenis beck kn
This means that with recent snapshots, you should use the .img file to prepare your installation medium, where you were previously using the .fs file. It also means that you can install 'direct-from-internet' on these fancy UEFI machines! Note that if you want to install the OpenBSD 6.7 release, you still need to use install67.fs.
These are some highlights of the improvements in the present release:
- For new installs on nearly all architectures the default file system is now FFS2, sporting 64-bit timestamps and block counters
- There are numerous SMP improvements, including unlocking of several system calls
- Hardware support in all architectures is much improved and expanded, with a number of new drivers including the iwx(4) driver for new Intel WiFi devices as well as significant expansion of arm64 and armv7 hardware support.
- Enabled rpki-client(8), to support Origin Validation in BGP-speaking routers in the base install.
- New versions of programs and subsystems maintained as part of OpenBSD but widely reused elsewhere:
Thanks to the developers for all the good work that goes into each release! To support further work on OpenBSD, please see the donations page for ways to contribute even if you can not offer up code yourself.