A running description of activity related to DragonFly BSD.
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.
Today is the day that FreeBSD moves to using clang by default. This is not necessarily a surprise, but I like the finality of calling it “Clang-Day”. I think Clang will probably be the next compiler brought into DragonFly’s base system, instead of the next release of gcc. Don’t make any bets on my statement, though, cause I certainly won’t be the one doing it. (It’s hard.)
I’m glad 3.2 is out the door. I think I spent more time on release notes and watching package builds than any other release.
Your unrelated link of the day: Sir, You Are Being Hunted. I link to the Kickstarter for this game for no other reason than I think it would be fun to play.
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.
I mentioned this before in the Lazy Reading from last Sunday, but it’s worth a second look: Apple’s new Fusion Drive product appears to be very much like DragonFly’s swapcache. DragonFly doesn’t have exclusive right to the idea of caching on a faster disk, clearly, so I’m not complaining that it’s “ours”. It’s frustrating to see product announcement/press releases stumbling all over this like it’s a new thing.
Then again, having new ideas about technology ideas and making sure they spread is one of the points of the BSD license, so perhaps there’s no good reason to complain at all.
(Before anyone reads too much into this: No, I don’t know of any direct relationship between swapcache and Fusion Drive; they may have no common background other than structure.)
I lost Internet access because of Hurricane Sandy, and couldn’t get my machine to recover until I power cycled. I think it’s because my external IP changed, and pf doesn’t seem to handle that well for NAT or just in general. The recommended fix, putting the interface name in parentheses, doesn’t seem to work. Anyone have advice?
John Marino’s committed bmake as the replacement to make, as mentioned previously. You should probably do a full buildworld/kernel sequence. This of course only affects you if you are on DragonFly 3.3.
Life is busy, busy, busy. But there’s always time for Lazy Reading!
Your unrelated link of the week: Delilah Dirk. It’s a comic, and the story available to read online is about a tea merchant, which makes it exactly right.
Matthew Dillon’s put more of his Hammer work into DragonFly, with notable parts being the creation of a ‘dmsg’ setup for advertising available block devices to share between machines using Hammer. To anticipate your next question: No, it’s not something you can run right now as a test; this is the underlying framework.
The kernel in DragonFly is now SMP by default. The “SMP” option in the kernel config is no longer needed, so it’s been turned into a no-op. You don’t have to update your custom kernel config… yet.
A thread on pkgsrc-users@ reminds me: adding a specific line for bin-install will save time when rebuilding packages; pkgsrc will use existing binary packages instead of rebuilding from source when possible, when this is set. At least, I’m pretty sure that’s what it does.
The pkgsrc packages for DragonFly 3.2 are still building… I’ve tagged the release, so it will be ready as soon as the packages are ready.
Sandip Jadhav asked if anyone was working on an I/O scheduler. Chris Turner replied with a “no”, but also with a list of places to look for details on writing one, which I’m linking here for posterity.
John Marino is working on a very good idea: bringing bmake into DragonFly as a replacement for the current ‘make’. bmake is going through more active development and apparently also in use/will be used? on FreeBSD, so syncing up with the same make flavor as FreeBSD and NetBSD will help everyone. It’ll also remove the problem where you ‘make’ everything in DragonFly, except pkgsrc packages which you ‘bmake’. It’s not changed over yet.
(What does OpenBSD use for make?)
I had some interesting home network troubleshooting over the past week…
Your unrelated link of the week: Terrorism as Art. An extended profile of Survival Research Laboratories at The Verge. Even if you don’t like the content, the focus of the artist is remarkable.
A conversation about compilers in the DragonFly base system led peeter (must) to describe his group’s use of OpenMPI on DragonFly for physics calculations. Apparently he’s had a significant performance improvement on DragonFly.
Along similar lines, John Marino helped out by bringing in libssp and libgomp for gcc 4.7 for use with OpenMP. (This is in DragonFly 3.3, not 3.2).