There’s been a few changes to reduce memory usage; this may not affect you unless you have an extremely busy machine, but it won’t hurt.
I knew about files like /etc/services, for common IP port usages, and /usr/share/zoneinfo, for time zones, but I didn’t know that DragonFly (along with other systems) keeps a list of agreed names for various human languages defined by ISO639 in /share/misc/iso639, and it’s maintained at least in part by the Library of Congress. At least I didn’t know until Sascha Wildner updated it.
Updated: Birthstones and flowers. Don’t know why.
If you’ve ever wondered how building all of pkgsrc would go with GCC 4.7.2, which is in DragonFly but not the default compiler, John Marino can show you just that. He has a list of the results from a bulk build of all packages on DragonFly with GCC 4.7.2.
This discussion of cryptographic hardware for FreeBSD may include hardware that would work for DragonFly too. Can someone verify?
Do you use ndis(4) for a network card that would otherwise not work? Are you running DragonFly 3.3? Are you willing to run USB4BSD and see if it works? If you do, tell Sascha Wildner if his changes worked.
If you are one of the few people still wanting to read an OS/2 HPFS drive, support for it in DragonFly has been updated by Antonio Huete Jimenez. It’s read-only, but writing didn’t work well, and I’d be surprised if there’s any hpfs disks that aren’t archival, out there.
Also, Sepherosa Ziehau has updated the pktgen program to generate even more packets, even at relatively low CPU clock speeds.
Sascha Wildner recently brought in support from FreeBSD for HighPoint’s RocketRAID 4520 and 4522 SAS/SATA RAID cards. It’s in the hptiop(4) driver.
The initial download of pkgsrc via Git on DragonFly is a little bit faster now, with the ‘make pkgsrc-create-shallow’ option recently added by John Marino. Note that there’s a similar option for src. It skips downloading file history.
Sascha Wildner has added system management BIOS (SMBIOS) support, visible with kenv, from FreeBSD. Use it for getting things like the BIOS revision, system manufacturer, and so on. For example:
smbios.bios.reldate="12/04/2006" smbios.bios.vendor="Dell Inc. " smbios.bios.version="2.1.0 "
This may seem minor, but this can be very helpful when dealing with hardware you aren’t physically able to access.
Because of the recent good results for pgbench on DragonFly 3.2, Phoronix has a new benchmark of DragonFly using other (possibly unrelated) tests. There’s not a lot of information to glean from them; they are testing operations different than what was optimized for pgbench in 3.2. I’d like to see DragonFly 3.0 tested the same way to see how much improvement there was between versions.
While we’re talking about cross-pollination of BSDs: going by licenses, there’s some DragonFly code in the iPhone – at least the fairq scheduler. (Noted by several people on EFNet #dragonflybsd)
MaheshaDragonFlyBSD, a ‘liveUSB’ distribution of DragonFly with software preinstalled, has been updated to run using DragonFly 3.2.1 as a base. The linked page contains screenshots and a description of what comes out-of-the-box. (mentioned previously here.)
Sepherosa Ziehau is switching a number of network cards over to use ifpoll, which means they will have capabilities similar to MSI-X, even if the network card doesn’t support it. My suspicion is that it will make these cards perform better in busy situation where they would otherwise get bogged down… but that’s based on hunch rather than empirical testing. As Sepherosa Ziehau pointed out, it certainly can’t hurt.
On the 10th of November, I’m going to remove the binary pkgsrc packages from mirror-master.dragonflybsd.org for DragonFly 2.8 through 2.11. They are closing in on 2 years old at this point, and are from a pkgsrc branch that hasn’t been updated for that long.
If you are actually using version of DragonFly that old, you can continue building from pkgsrc normally; these are just prebuilt packages.
Every year, the Chaos Communication Congress tends to gather at least a few DragonFly-using people, and this year is no different. The event is being held in a much larger arena this year, in Hamburg, Germany, so there’s a good chance a DragonFly ‘assembly‘ could be held. Speak up on the users@ mailing list, or EFNet #dragonflybsd, if you’re going too. It’s happening on the last few days of this year, December 27th through 31st.
I’ve written a release email that includes the steps for updating from source and updating pkgsrc for existing installs. This release enjoys better performance and new packages, so go, enjoy.
There was one more file to change for the bmake import, so if you are running DragonFly 3.3 and updated between the 28th and 30th of October, do a full rebuild.
Peter Avalos has updated OpenSSH in DragonFly to 6.1p1. This looks to be a bugfix release, but check the changelog for details.