DragonFly 4.0 users should upgrade

If you happen to still be running DragonFly 4.0 – that’s two releases ago and not supported – you may be noticing less ports are building.  There’s been enough significant changes in DragonFly since that release that it’s reducing the number of buildable ports.

DragonFly 4.0 to 4.2 is not a difficult jump, so jump when you can.  The converse of this, of course, is that there’s even more building on 4.2 and DragonFly-current.

libc no longer in executable memory

John Marino is working on versioning libc, and as part of that process, libc is no longer loaded into executable memory.  Here is I think an explanation of lib versioning that may apply, and of course moving things that aren’t supposed to execute, out of executable memory areas, is good for security.  There’s more on that topic, too – W^X may be a similar example.

This is a complicated topic that I’m not part of, so suggest better descriptions in the comments, please.

HAMMER2 root mounts and live dedup too

HAMMER2 recently gained the ability to be used as the root mount for your DragonFly system.  Live deduplication of data is also now possible, which means fast copy operations, less space used, and no need to wait for an overnight batch process to do it.  If you want to try it, you need a bleeding edge DragonFly system and the WANT_HAMMER2 option.  It’s still not ready for production use, so don’t try it with any data you want to keep.

Many Hammer 1 updates, and credit

I don’t note it enough, but Tomohiro Kusumi has been making constant updates to HAMMER, the version we have now.  Often they are the sort of update that makes the code more readable, or fixes possible problems, and so on.  Very essential, but hard to post about it.  In any case, I’m using his recent improvements to hammer volume-del to note his contributions, of which there are much more than the day’s worth I link here.