DragonFly 4.0.3 has been tagged; you can look at the tagging message for details, but the major reason for doing so is to include OpenSSL-1.0.1l. I will have images up soon.
John Marino has written up an extensive how-to for slider, the history tool for Hammer filesystems, including screenshots.
Thanks to Sascha Wildner porting from FreeBSD, mixer(8) now remembers state. This is something I’ve wanted for a long time.
For whatever reason, I’ve seen several people in the last week or so have mouse problems on install, and they were often solved by running moused. So, there’s your little reminder.
Can someone with experience on Google Compute Engine try out running DragonFly on it? There’s FreeBSD instructions, so it might work.
DragonFly no longer has SCTP. Nobody minds, I think – I had to look up what it is.
The short answer is ath(4) and iwn(4), via this post. There’s an update coming for the wireless infrastructure in DragonFly; Matthew Dillon and Adrian Chadd (on the FreeBSD side) are working together for improvements.
While I’m mentioning recommendations, the Silicon Image 3132 chipset is apparently excellent for eSATA drives on DragonFly.
Matthew Dillon’s added a sshlockout utility, to temporarily block SSH traffic from repeated brute force SSH login attempts. It’s been mentioned before, but it’s in the system now. It’s been refashioned to work with pf.
Francois Tigeot has performed a major upgrade of DragonFly’s sound system. If you had sound problems or unsupported hardware before, this may fix them. It will require a full buildworld+buildkernel.
Romick posted some more tips on setting up various special keys on an Acer c720 Chromebook, running DragonFly of course, and Matthew Dillon also has backlight key configuration. I wish I had a spare $200 right now for one of these.
I managed to miss this last week because of issues with my RSS feeds, but the 71st episode of BSDNow is/has been up. It’s “systemd isaster”, cause the interview is with Ian Sutton talking about BSD replacements for systemd dependencies. There’s a number of at-least-slightly DragonFly-related things in there, including OPNSense, pkgng, and Hammer mentions.
I’m breaking my normal weekend posting schedule to note that DragonFly 4.0.2 images are now linked on the main site and on mirrors now/soon.
DragonFly 4.0.2 has been tagged. I’m building the release images now. If you’re already running 4.0.1 it’ll be easy enough to upgrade to; you will want to catch up to this commit fixing a quiet memory issue.
The CAM layer in DragonFly has had its big lock removed/been marked MPSAFE, so you will notice a performance increase when using multiple disks. (assuming you aren’t throughput-limited, of course.)
That’s Virtual Private Server, if you don’t know the term. I mentioned VPSs and BSD before in a In Other BSDs article, but “Ed” found an article specifically about installing DragonFly on Vultr.
There’s a FreeBSD Forums thread about ZFS and Hammer, as several people have pointed out to me. It’s interesting to see, but there isn’t a lot of quantitative discussion. (It’s a forum post, not a white paper, though.)
Do you remember the BSDNow story a while ago about a Tanzanian community effort using FreeBSD to build a library? They’re looking at DragonFly, too, because of the low resource requirements. From that discussion: a hardware reason for an ‘indefinite wait buffer’ error, and a note on how to most efficiently download packages for multiple machines.
Sepherosa Ziehau has posted a note that V4-mapped addressing is no longer supported in DragonFly. You will need to do a full buildworld/buildkernel if you are running master. Also, TCP MTU path discovery is on by default. Also also, he’s added a SOL_SOCKET/SO_CPUINT socket option for use to reduce load in heavy network activity. As usual, I don’t quite comprehend.
You can now control your backlight settings through sysctl and enjoy greater video support/stability – as long as you are using a i915 video chipset on DragonFly.
John Marino has created something very useful: a graphical tool for Hammer file history. It’s called ‘Slider’, and it uses curses to work in a terminal. It shows historic versions of files and can restore those old versions as needed. This was already possible in Hammer, of course, but it required a sequence of commands that were not straight-forward. I’ve been slow enough posting it that version 2.0 is already out, offering a way to see files that no longer exist, but are still in history. (i.e. deleted some time ago) ‘Time Machine’ sounds like the best name, but that seems to be taken.