A running description of activity related to DragonFly BSD.
The two things that make my day! The work on DragonFly-current has led to some significant speed improvements. So good, that Samuel Greear’s post on OSNews.org links to graphed results from him and from Francois Tigeot (multi-page PDF) showing the results from pgbench.
The results show a jump in multi-core/processor numbers that vastly exceeds DragonFly 2.10’s performance, and is comparable to FreeBSD 9/10. Here’s some of what did it.
Alex Hornung has created ‘dfregress’, a test framework designed to be as simple as possible for adding tests to DragonFly. This would make it easier to verify an upcoming release is correct, for instance. See his commit note for extensive details, and add a trivial test for anything you value.
This is another one of those features that I bet goes away, and nobody would notice because nobody uses it any more. Sascha Wildner has removed AppleTalk from DragonFly.
The host leaf.dragonflybsd.org has been upgraded to new hardware. This is the machine used for anyone who wants to develop on DragonFly, so there’s a good performance boost there for developers. It also hosts bugs.dragonflybsd.org, which should be working again soon.
DragonFly has a new memory allocator, called (not surprisingly) “dmalloc“. It’s only present on x86_64, not i386, because it could eat up more VSZ (virtual memory) than an i386 kernel may have available.
I’m going for more verbose linking. Because my opinion layered over a bunch of linkblogging is just what you wanted on a weekend, isn’t it? If not – too late!
Your unrelated link of the week: The New Shelton Wet/Dry. Titles, content, and images are all picked from unrelated sources, but it forms an oddly compelling digest of multiple topics. Slightly NSFW, sometimes.
The presence of /usr/include/crypt.h in DragonFly (starting in December 2010) meant that some programs compiled during that time will expect that file to always be there. It was recently removed, so any programs compiled in that timeframe will also need to be recompiled. Right now, this affects you only if you are running DragonFly 2.13 , since that’s the only place crypt.h was removed. This may be an issue for the release, but we’ll worry about that when we get there… I’m kicking off new 2.13 bulk builds now.
There’s a new page up on the DragonFly website, about using rpkgmanager to manage your pkgsrc-installed packages.
In DragonFly, there’s only a few places C++ is used. If you wanted to make sure DragonFly was pure C, Samuel Greear lists those remaining nooks and crannies.
Almost all the packages in pkgsrc support non-root installation now… except these last 31. I recall something about their removal by the next quarterly release if they still don’t work, or maybe just after. Jump in if one of these packages is useful to you.
You can now have, in theory, up to 32 terabytes of RAM on your 64-bit DragonFly system, from a change made by Matthew Dillon. I’m curious to see if anyone has even 1 terabyte, as that’s at least feasible.
John Marino added tuning support within GCC 4.4 for the Geode CPU. Waaaay back when, these were x86 -compatible Cyrix chips. Nowadays I think they are most common in single–board computers.
The November issue of BSD Magazine is out. No DragonFly content again, in part because I wasn’t even sure when the deadline was. (The editor changed.)
Some cleanup in the CVS -> git process wasn’t happening, so if you have been using pkgsrc 2011Q3 from git (i.e. via make in /usr), re-pull to make sure you have everything.
(The post noting this seems to have been eaten by the mailarchive… that’ll be replaced.)
There’ll be some brief outages this week as a few of the dragonflybsd.org machines are upgraded. The new machines will be 64-bit DragonFly, and have 16G of RAM. RAM is crazy cheap these days. I’m continually dumbfounded by it.
The Technology Innovation Management Review (used to be the Open Source Business Resource) has its second issue out since the rename. There’s still plenty of open-source focus in there.
Have you noticed how what was nerd culture 20 years ago has become mainstream? In the same way, open source is becoming a given assumption, rather than a niche to follow on its own.
A bumper crop of articles to read this week.
Random unrelated link for the week: “War Photographer“. This animation makes me so happy.
This recent structure change (are there others like this? Maybe?) means that existing binaries may need to be recompiled for anyone tracking DragonFly master. This probably means that an upgrade from 2.10 to 2.12 will require rebuilds of all binary pkgsrc packages.
Well, they’re still available, but you don’t want them in your config any more because they can slow you down. This will only affect you if you are running binary files from DragonFly 1.2 or earlier, or… I guess a 4.3 BSD binary? From 1986? I’m sure there’s some other reason for it to be there.