leaf.dragonflybsd.org, where the DragonFly website is hosted, is temporarily down while a disk is replaced. Images and binary packages are still available.
This may not be a huge surprise, but the Minnowboard MAX can run DragonFly just fine, modulo some dmesg complaints.
Sepherosa Ziehau has introduced a new sysctl:
net.link.ether.inet.log_arp_creation_failure
Set this to zero and you won’t get endless ARP events from networks you aren’t on. For example, I’m hooked up to a cable modem. I only get a public routable IP address, but the network used for the cable modem network itself bleeds ARP packets out where my DragonFly machine can see it. Since it’s on a different network segment than the address I receive through DHCP, it always fails and the system logs it. For example:
May 11 05:20:52 www kernel: arplookup 100.68.112.145 failed: host is not on local network
I can’t do much about it since that layer 2 leakiness is going to happen, but I can shut it up with this sysctl – and thank goodness, cause I’ve been seeing these messages since first using a DOCSIS modem in… 2001 or so?
Francois Tigeot has committed his Broadwell work, which has a longer-than-I-realized list of benefits. Does anyone have a 4k screen to try?
Jesse Wattenbarger wrote in with his success story of switching to DragonFly, both for server and desktop. Of note is his noticeable speedup with swapcache.
If you’re running DragonFly-master and you have an Intel video chipset, Francois Tigeot has an update for you. It brings accelerated Intel video up to match the Linux 3.14 version, adds Broadwell chipset support, and should generally improve performance. He lists how to test right in the message.
DragonFly committer Joris Giovannangeli has a Google Summer of Code project. He’s bringing Hammer2 to OpenBSD, in single-node form. It’s a very difficult project, but Joris is a very talented worker.
Tomohiro Kusumi has been quietly making a lot of commits to Hammer. I haven’t been linking them because they don’t necessarily equate to new features, but here’s an recent exception: the -A argument will make your Hammer command run on every PFS. It only affects reblocking/rebalancing – for now.
It’s been a relatively calm week, for once.
- New Delhi has a BSD user group. (via)
- PC-BSD and 4K — Oh my!
- Is nvidia the best option for gaming on FreeBSD?
- EuroBSDCon 2015 has extended the time for paper submission, cause they have so much to work through.
- Hipster keyboard layout on NetBSD
- The pkgsrc-security GPG key has changed.
- Binary packages of pkgsrc-2015Q1 for illumos and OS X are available.
- I like cross–pollination.
- PC-BSD can now restore encrypted volumes over iSCSI.
- Two more mentions of OpenBSD (though any should work) on Vultr.
- Better OpenBSD performance on KVM via x2apic mode.
- OpenBSD rolls their own file(1).
- OpenBSD has W^X support for i386 userland now.
- 2-factor authorization on FreeBSD. (via)
- My switch to OpenBSD, first impressions (via)
- Microsoft .NET Running on FreeBSD 10.1/amd64 (via)
You can now export Hammer slave volumes as NFS mounts – but since slave volumes are updated from master, you’re mounting a snapshot of that point in time. That may actually be an advantage.
DragonFly builds two compilers by default. If you weren’t interesting in building both, there were switches to build only the default, like NO_GCC47. This changed with every compiler update.
With the switch to GCC 5, the new switch is “NO_ALTCOMPILER”. That will last through compiler changes. I’m mentioning this now because sooner or later, you’ll want to gain back some time on a buildworld.
DragonFly now has GCC 5.1 release. If you are running DragonFly master (i.e. 4.1), you’ll probably want to both rebuild world and kernel, and update your packages so they all match. There’s already packages built with GCC 5.1, so binary package upgrades can happen quickly. There’s GCC 4.7 packages still available if you aren’t making the jump yet.
If you’re on DragonFly 4.0.x – nothing’s changed.
I’m late posting about these, but they go together: Sepherosa Ziehau has added the ability to read CPU temperature through various sysctls, and the same for DIMM temperature readings.
Matthew Dillon bought a system with a Broadwell series CPU, installed DragonFly, and wrote up his experience. Read it if you plan on purchasing this hardware any time soon.
Here’s some comments from Matthew Dillon on page coloring in DragonFly; a topic that comes up every year for some reason.
The release candidate for GCC5 (5.1.0) is out, and it’s in DragonFly too. It’s not yet switched over to run as the default – that’ll require the release.
The default compiler in DragonFly is going to change over from GCC 4.7 to GCC 5.x very soon, to match the GCC 5.1 release. This means that packages built for DragonFly-master won’t be compatible with the old ones. You will need to reinstall packages when you next ‘pkg install’. John Marino has an extensive writeup detailing what’s needed, and the actual change is some days off.
If you are using DragonFly 4.0.x (the release), this doesn’t affect you at all.
Francois Tigeot has a new update to the drm/i915 driver for testing. It matches, feature-wise, what’s in Linux 3.12. Try it if you’ve got the hardware. (and dragonfly-master)
I have had trouble with my daily/weekly periodic reports never making it to my GMail account. Sascha Wildner pointed out to me that periodic.conf has its own answer already:
daily_output=”/var/log/daily.log”
daily_status_security_output=”/var/log/security.log”
weekly_output=”/var/log/weekly.log”
monthly_output=”/var/log/monthly.log”
… and newsyslog is already set to take care of them. There’s more in the periodic.conf man page.
There’s been some linking to the updated HAMMER2 design document. The Reddit link doesn’t have anything specific, but the Hacker News one has some details (including a credit code!) for installing DragonFly on a Vultr VPS.