If you are running DragonFly-current, you can get your floppy drive running again. This is actually hard to test; floppy drives are becoming an endangered species.
Last minute, as always!
- The anatomy of tee program on OpenBSD. (via)
- Leaving Amazon AWS. (via, I think)
- FreeBSD Port-Knocking.
- s2k17 Hackathon Report: Stefan Sperling (stsp@) on wireless (iwm(4), athn(4) and more) progress.
- DiscoverBSD for 2017/12/03.
- Cross-BSD pollination. (DragonFly->OpenBSD, via)
- FreeBSD 11.0 is end-of-lifed.
- OPNsense 17.7.9 released.
- BSDCan 2018 Call for Papers is out. (via)
- DTrace & ZFS Being Updated On NetBSD. (via)
- NetBSD desktop for newbies. (via)
- What sort of fun projects are you guys working on using Dragonfly?
- pledge() work in progress.
- arm64 platform now officially supported [and has syspatch(8)].
- “SSH Mastery” 2nd ed tech reviewers wanted.
DragonFly 5.0.2 is released. As you may guess from the version number, this is a bugfix release. The release tag has the full details. Update through the normal process of a buildworld/buildkernel, at your leisure.
Thanks to Rimvydas Jasinskas, it’s possible to ‘make NOSHARED=yes buildworld‘ and build a complete DragonFly world without shared libraries.
If you are like me and have a long weekend, dig into /usr/share/examples. Not all of it is necessarily up to date, but there’s examples there on running rconfig, diskless, different pf and ipfw examples, and so on. Actual documentation is in corresponding man pages – and there’s examples on how to write them, too.
I just wasted an hour trying to figure out why xorg had strange output but no errors on this laptop, and it’s because I had i915_load=”YES” in /boot/loader.conf instead of i915_load=”YES” in /etc/rc.conf. I’m almost nearly sure I’ve mentioned that before, but if not: here you go.
(though if you never plan to run X, you can put it in loader.conf and everything will just work.)
(Title updated for a more correct sentence)
Welcome new DragonFly committer, Peeter Must!
Do you have a terabyte or more of RAM? You can boot DragonFly. In theory over 32 terabytes will require changes – but oh, to have such problems…
Noted from this commit: if you are routing over IPv6 directly to another address, the sysctl net.inet6.icmp6.nd6_onlink_ns_rfc4861 must be set to 1.
rdist has been removed. Does anyone mind? I don’t think so.
sys_pipe has been modified to avoid contention on DragonFly, which means better performance as tasks get handed between processors. See the commit message for details.
Matthew Dillon has added KVABIO, an API for avoiding the need to sync the TLB across all CPUs before continuing. What’s this mean? The more CPUs you are dealing with, the longer it takes to make sure all of them have the same cached view of the virtual memory. There’s a tradeoff – caching that view speeds up memory access, but the time cost of the synchronization can erase those benefits.
This API is now supported for NVMe and swap, HAMMER2, and tmpfs. Note that those last two links show a huge drop in IPI messaging. In the real world, this showed about a 5% improvement in performance for CPU-intensive work like complete synth builds. (Based on IRC conversations.)