Remember I posted that LibreSSL is in base DragonFly, but not default? Well, it’s default now. You can have a system without OpenSSL at all, by rebuilding DragonFly-current and using up-to-date dports.
Update: see John’s comments for clarification: LibreSSL is default; the change is that OpenSSL isn’t even built any more. The result is still the same good news: you can have an OpenSSL-free DragonFly system now.
I’ve uploaded ISO and IMG files for DragonFly 4.6.1, so they should be available for download at your local mirror. Note that there’s an uncompressed 4.6.1 ISO for those installing to a virtual server.
I don’t have it uploaded yet, but DragonFly 4.6.1 is tagged. Anyone with an existing 4.6.0 or earlier system can upgrade now. Use the 4.6 release instructions if you are unsure on how to upgrade. The 4.6.1 tag commit message has all the changes.
OpenSSL in DragonFly 4.6 has been updated to 1.0.1u. It’s time for a DragonFly 4.6.1, to catch up on this and other updates since the 4.6.0 release. I plan to work on it this weekend.
It looks like I summarized iwm(4) updates too early, cause Imre Vadasz added an actual powersave option. I’d like to see someone with a power meter do some before-and-after testing.
It’s been a quiet week, but there’s some activity: Imre Vadasz has been committing many improvements to iwm(4). They haven’t been standalone enough for me to build a post around, but the most recent enables a low-power scan mode.
I’ll just say I did this:
cpdup -VV -v /var/hammer/usr/snap-20160928-0301/local/pgsql/data /usr/local/pgsql/
And managed to bring back my last year or so of RSS feeds and the like. Phew!
If you had trouble getting your laptop’s touchpad to work under DragonFly, try again. (If you are running DragonFly-current)
It’s now possible to build dports using LibreSSL instead of OpenSSL. Set SSL_DEFAULT in make.conf to the appropriate port name, and start building. Use synth for fastest results, of course.
LibreSSL will eventually become the default library. This is in addition to the previously-mentioned, already-completed in DragonFly 4.7, base system switch to LibreSSL.
For those running DragonFly 4.7, there’s new firmware for all iwm(4) devices. Also, you can get temperature readings off the iwm wireless device now, if I’m reading this correctly.
Tomohiro Kusumi is thinking about porting it. Follow the whole thread for details.
3D printing on DragonFly with a Fabrikator? Yep, it works. (from jh32 on EFNet #dragonflybsd)
I’ve never had as many hackathon links as I did for g2k16 over this week and last.
Matthew Dillon has added powerd, a utility that will automatically step down processor speed based on reported temperature. The range is configurable, and there’s some other nice-to-have features. This will save your CPU from melting, and probably also your thighs from being burned.
karu.pruun has been trying to get a Macbook’s hybrid graphics card to work in DragonFly. He’s been working on a gmux driver, but it needs a framework like Linux’s switcheroo. If this topic interests you, help him out.
I may have mentioned this in part before, but Matthew Dillon has a brief script to reload pf when an interface IP changes. I’m linking it here in case it’s useful in the future.
Recent changes for virtual machine support and the new powerd utility have been rolled into the release branch for DragonFly. They’ll probably be in the next point release, or you can rebuild a release machine now for immediate access.
Also mentioned in the update from Matthew Dillon, DragonFly-master users should upgrade carefully as DragonFly migrates to using LibreSSL in base, and dports-based LibreSSL in dports.
The’Errata 793‘ issue is apparently a bug where an AMD CPU can hang under very specific circumstances. Sepherosa Ziehau has a fix – please try it if you have the appropriate hardware.
How long does it take to build all 24,000 packages in the DragonFly ports collection? Apparently about 22 hours on a dual Xeon machine (with I think 36 cores) or 48-core Opteron. This is with synth. I used to measure pkgsrc builds in weeks.
DragonFly now has version 2.4.2 of LibreSSL and uses it in base. Ports may still link to OpenSSL, though – it’s still built by default, though make.conf can be configured to prevent that.