The next release of DragonFly will be 6.0, mostly because 5.10 is an annoying version number rather than any significant version changes. We’re due to release by the biannual calendar schedule – but there’s a DRI bug that needs to be fixed; I plan to tag as soon as that’s done.
Because of this commit that makes some changes to lib/stdio, you might get more reinstalls than you expect on your next pkg upgrade because of the __DragonFly_version change. This only applies to -current (5.9) users.
(I might be wrong)
If you want to build a kernel with no options, stripped down, here you go. I don’t know how useful it would be…
Well, it doesn’t fix anything, but it seems like an answer that almost always helps: running sysmouse usually fixes most X11 mouse problems.
This seems so minor, but such a good idea: a regular check to make sure kernel and userland are in sync.
Daniel Fojt’s updated libedit in DragonFly; not huge, but I mention it cause I’ve seen the very first bug fixed in the commit listing; garbled history.
Matthew Dillon added “existence locks” to DragonFly, which as usual he committed with a long, descriptive message.
There’s now -K (kernel) and -U (user env) options to uname. Minor, but good to know the change.
I always thought of cross-pollination – sharing of code between BSDs – as a good thing. This seems like the most basic way to do that: same base sh.
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.
A complete set of new dports binaries have been built, for 5.8 and for -current, so now is a good time to upgrade. Update to 5.8.3 if you haven’t yet, while you are at it.