This week's BSD Now includes a link to, a way to install BSD using a rescue boot environment, which is going to come in handy for someone reading this.  I know I've linked to it before.
Predrag Punosevac has some notes on how he cleaned up some HAMMER drives and freed up half his disk space.
I know I'll need this again, so I am making a post out of it.  If you are running a DragonFly system through NVMM using the excellent site instructions, and you want X apps to display on a local Windows workstation, you need to:
  1. Install VcXsrv (or your X server of choice) on Windows and start it up.
  2. Install xauth and xterm on the DragonFly host.
  3. On the DragonFly host, set these three options in /etc/ssh/sshd_config.  They are already there but commented out with different arguments.
    X11Forwarding yes
    X11DisplayOffset 0
    X11UseLocalhost yes
  4. Reload sshd: 'service sshd reload'.
  5. 'Enable X11 Forwarding' under Connection -> SSH -> X11 in the puTTY setup dialog.
Connect to the DragonFly host with puTTY, type 'xterm', and a terminal window should appear on your Windows desktop within a few seconds.  This could be turned into a shortcut with puTTY to avoid having redundant terminals, but I'm not writing that out yet.  
I use date(1) just rarely enough that I can never remember the right arguments to create a human-readable result.  Now, there's an -I arg to date(1) that uses a word instead of a format string to get ISO8601 output.
Here's something I just learned: If you are running dma(8), /etc/dma.conf will contain MAILNAME.   If your email server is somewhere else, but you set MAILNAME as your domain - dma will deliver locally. I had /etc/dma.conf set with MAILNAME - so dma kept delivering overnight periodic results to root, which was aliased to in /etc/mail/aliases and so it was delivered to 'justin' locally on the machine. Changing MAILNAME to - the host you are reading right now - fixed the problem.  Now, whether this was an automatically set config or something I misconfigured some years ago... I can't tell.
I didn't know about this, but there's a daily/weekly/monthly/security_show_badconfig option in periodic.conf that is now defaulting to "yes" in DragonFly.  This I assume means you'll get the output of erroring periodic scripts sent to you.  Useful, especially if you find out about an error you hadn't seen before.
If you edit /etc/fstab, and then later change something like the proc filesystem from OpenJDK, you might not boot normally.  Antonio Olivares has a solution for you.
If you upgrade pkg on your system, it may start erroring out.  This is because the default config will confuse the newer version.  To fix this, you can copy over a working config and the problem will go away.  I expect this may only be a problem until the next release.
Working on less traditional BSD links here.
Well, it doesn't fix anything, but it seems like an answer that almost always helps: running sysmouse usually fixes most X11 mouse problems.
The ChiBUG monthly meeting has gone virtual, so go now if you are interested.  The thread about it also includes some notes on how to connect under BSD that may be useful beyond this immediate event.
If you delete all your installed packages, you will also lose the certificate used by pkg to verify the connection to download new ones.  There's several workarounds for this problem.