The headline is a little misleading; umtpx has been in DragonFly forever, but now utmp is really retired and programs adjusted to match. The change is not that user-affecting and utmp data is still accessible; this is part of the ABI change alluded to over the past week.
If you are on DragonFly-current, the ABI changes of the past few days are complete and new dports packages are built, so now is a good time to do a complete build and install of world and kernel, and then a pkg update.
5.6 users can keep on keeping on; no breakage there.
There’s commits being made in DragonFly that will break binary compatibility. If you are running DragonFly-master, that means you will need to do a full buildworld/buildkernel when updating, and you will either have to rebuild packages or wait some days until a new set are built.
If you are running the 5.6 release, you are unaffected.
I’ve seen a similar config other places, but it never hurts to note: scrolling in X requires just a few xorg config lines.
The radeon driver support on DragonFly now matches Linux 4.7.10. Update and test, especially if you have one of the chipsets mentioned.
First, history: DragonFly has had binaries of dports available for download for quite some time. These were originally built using poudriere, and then using the synth tool put together by John Marino. Synth worked both to build all software in dports, and as a way to test DragonFly’s SMP capability under extreme load.
Matthew Dillon is working on a new version, called dsynth. It is available now but not yet part of the build. He’s been working quickly on it and there’s plenty more commits than what I have linked here. It’s already led to finding more high-load fixes.
Incidentally, my employer, REDCOM, uses FreeBSD as a base for its main product, is deployed in rough areas and in high-security government locations, and is one of the few electronics manufacturers still working entirely in the U.S.. REDCOM also has jobs to fill in New York, where I work. Please, apply if you see a job that interests you – and tell me.
- DistroTest.net, which happens to have runnable online versions of GhostBSD, FreeBSD, HardenedBSD, MidnightBSD, NetBSD, OpenBSD, OPNSense, and DragonFly. (via)
- The VBSDCon schedule (Sept 5-7, very soon!) is up.
- Update webmin/usermin if you have them installed.
- Impact of Tariff Increases. Eventually relevant even if you aren’t a U.S. reader.
- Project Trident 12-U3 and 19.08 now available.
- Valuable News for 2019/08/14 and 2019/08/19.
- Porting wine to amd64 on NetBSD, third evaluation report.
- USBNET: A story of networking and threads that won’t stop pulling.
- Getting the GNU gdbserver to work.
- Fuzzing NetBSD Filesystems via AFL. [Part 2].
- GSoC 2019 Report: Adding NetBSD KNF to clang-format, Part 2.
- Brutal Doom 64 on OpenBSD.
- OpenBSD -stable gets package updates! Release OpenBSD doesn’t normally get packages?
- Blueprint and progress status for mixed environment multilevel backup. Really, the thing to see is a spreadsheet.
- When a hacker tries to infiltrate an OpenBSD machine. Pufferfish reference.
- CFT: CBSD project switched to its own cloud images.
- Instant Workstation.
Here’s something I haven’t see before: at the time of me typing this, there are commits in DragonFly, FreeBSD, and I assume NetBSD (haven’t found the commit), but the 2019-5612 CVE entry is still shown as reserved and not public. This may change by the time you read this article, of course.
Update: the original source, found by an intrepid reader.
Matthew Dillon posted an extensive writeup about the hardware changes for dragonflybsd.org; price to performance ratio has been improving so much for multiprocessor machines that we can jump forward both for hosting hardware and for a testbed.
He also mentions his immediate thoughts on what to tackle next, since SMP has been so relentless improved in DragonFly. It resulted in a very long conversational chain as people weighed in with opinions, so I’ve held off posting it until the conversation finished. (I chimed in too.)