In Other BSDs for 2015/12/26

There’s some DragonFly links I snuck in here because why not?

Qemu fixes, and a bonus

A number of people have reported problems with qemu and DragonFly, both running locally and on a host.  It turns out to be a problem with the getcontext(), setcontext(), and swapcontext() functions, but Matthew Dillon fixed it in a way that doesn’t affect performance very much.

That apparently wasn’t good enough, so he added _quick versions of those same functions, so it became not just a fix, but an improvement.

In related qemu news: qemu-devel can use vknetd similar to a vkernel, now.

New DragonFly installer disk arrangement

The DragonFly installer has been modified to produce disk arrangements that will generally match between UFS and Hammer installs, plus directories where you usually don’t want Hammer history or backups (like /tmp or /usr/obj) are now under /build and null-mounted to where you’d expect, since null-mounting works transparently well on DragonFly.  Matthew Dillon has a note explaining the whole thing.

Who wants a DragonFly shirt?

As mentioned previously, Sepherosa Ziehau is printing up some DragonFly T-shirts for WeChat users.  He’s going to have a few left over, so he is sending them to me to hand to non-China people.  If you want one, leave a note saying so in the comments.  Here’s the front and back.

You need to provide some way for me to contact you – preferably email, and the size you’d want.  (Use the Land’s End Men’s Shirts chart for sizing, because why not.)  I’ll only have a few, so no guarantees.

Update: I have more responses than probable shirts at this point – sorry!  I’ll get in contact with each of you once the shirts come in and arrange delivery.

No atime in Hammer

Hammer now defaults to ‘noatime’, meaning the date and time of last access are not updated on every file action.  Note that creation and modification date and time are still recorded.  This will help with speed and disk activity.

This may cause a problem with any software expecting this to change – mutt, possibly?  We will find out.  This change was done after the 4.4 branch, so it’s not in the current release of DragonFly.

DragonFly 4.4 released

DragonFly 4.4 is released!  The release page has the information, and your nearest mirror should have the images by now.   To update an existing 4.2 system, see my users@ post.

Sharp-eyed users will note that release is happening with version 4.4.1, rather than the 4.4.0 you’d expect.  That’s because I tagged 4.4.0, built the images, and then OpenSSL 1.0.1q was released.  Rather than make everyone who installs DragonFly need to immediately update, Sascha Wildner brought in the OpenSSL update to the 4.4 branch, and I built 4.4.1 instead.