This will turn into a real 5.6 release probably by weekend if no problems are found. See the tag commit message for a list of the commits since 5.4.
A question on starting up a virtual kernel on DragonFly and sticking it in the background led to some suggestions – follow the thread.
The next release of DragonFly should be smaller; Sascha Wildner and Rimvydas Jasinskas have removed or substituted enough packages on the installer image to drop the package disk usage 50%.
I am posting this so it can help someone else, someday.
I have a DragonFly-5.4 system. I installed mysql56-server, and started it up. By default, it listens on “*”, which meant it listens on a local socket and IPv6 ::1 – not 127.0.0.1.
2019-06-04 13:35:03 15833 [Note] IPv6 is available.
2019-06-04 13:35:03 15833 [Warning] Failed to reset IPV6_V6ONLY flag (error: 45). The server will listen to IPv6 addresses only.
I put bind_address=127.0.0.1 into my.cnf to get IPv4 loopback to work. Local socket connections still worked either way. I’m not using IPv6 on this machine, so this solution works in this situation. I’m not sure my mysql decides to go only IPv6 based on a strange flag, but mysql is reliably unreliable.
Remember the commit that autocreates human-readable disk device names under /dev? (Here’s a reminder.) It’s now in 5.4 – technically, since 5.4.2. Anyway, it will automatically identify the root USB disk when you boot from a USB .img file, so you no longer have to guess which /dev/daX file it was – usually da8 but sometimes you got a surprise instead.
I’m jumping ahead in my very full queue of DragonFly items to post to something new: Matthew Dillon has committed extensive work to the virtual memory system in DragonFly. He has a message to users@ that sums it up.
Images are available for download at various mirrors, too. If you’ve recently upgraded to 5.4, it’s the normal build process. There’s a brand new complete build of all packages uploaded, too, so plan on a ‘pkg update’.
This may never ever matter if you manage to avoid fdisk your whole life. But if you don’t pull that off, here’s the reminder: label your DragonFly slices with 108.
(Yes, I do in fact have a backlog of two months with DragonFly material. It’s been that constant.)
Matthew Dillon’s committed some performance work for HAMMER2, dealing with write-clustering. I don’t have statistics to note, so here’s the commit message.