Things that are done

There’s a number of things that all came together in the last 24 hours or so, which means: bullet points!

  • Jen Lentfer took my suggestion and ran with it.  He’s got an update to Sendmail 8.14.4 on the way too.
  • Binary pkgsrc-2009Q4 packages for DragonFly 2.4.x/i386 are all uploaded.
  • I finished a build of pkgsrc-2009Q4 for DragonFly 2.5.x/x86_64 – take a look and fix some of the broken items, if that interests you.
  • Weekend reading: check out this Trivium post as there’s some interesting historical items.  I may try that LackRack idea in a environment that doesn’t fit a normal rack well…
pkgsrc-2009Q4 binaries almost ready

A build of pkgsrc-2009Q4 for DragonFly 2.4/i386 is complete, and uploading now to avalon.dragonflybsd.org.  When the upload’s done, I’ll change the symlink so that pkg_radd downloads from the new collection.  Builds for x86_64 and 2.5 will be done soon.

There’s a couple packages – lang/mono, devel/boost-libs – that can be fixed with some updates; I’ll do so next chance I get.

Huge cleanup for games

Recently, Sascha Wildner committed a huge number of changes to the various games, bringing them in line with what’s on NetBSD and style(9).  This was all put together by Ulrich Spoerlein.

I draw attention to this not because it changed anything with the games in a functional sense, but because it’s huge (450 files changed, 31450 insertions(+), 29998 deletions(-)) and because it came out of nowhere.  It’s always nice to have new surprise contributions arrive.

Hammer REDO and other storage notes

Matthew Dillon declared his intention to have REDO working for Hammer very soon.  This will improve speed by lowering the number of fsync()s needed in a given period of time to flush data to disk.

He continues in a separate message talking at length about data flushing and how to implement it efficiently, with some comparisons to work in FreeBSD.  The followups are worth reading, too.

Too much ram: it’s possible

I’ve always said you can’t be too rich, too thin, or have too much RAM.  (I’m paraphrasing a quote from the Dutchess of Windsor.)  However, maybe you can have too much RAM.  Recent changes by Matthew Dillon have made it possible to run the kernel_map out of RAM depending on the quantity of video RAM and system RAM in use.

This isn’t a significant danger; I’m highlighting it because it’s an odd problem.  It’s easy to work around for now.  There’s a new utility, kmapinfo, to show mow much kernel memory is being used.