Cobbled together early cause I have an unexpectedly busy weekend, so you are getting a straight dump of everything pending I had in RSS, Thursday night.
I have more links than I expected.
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.)
I am confused because it seems like we had two BSD Now episodes in a week, but I am not complaining. Episode 298 is up (show notes) and has a goat.
The callout_* API in DragonFly has been rewritten. This will only affect you if you are doing some very specific programming – but it will be intensely interesting if so. I mentioned it before, but don’t forget debugging.
If you didn’t see the email: here’s details on how BSDCan 2019 is starting up, this weekend. Go, even if you aren’t near.
Update: corrected registration details.
It’s on the RSS feed but not in the normal place, and it’s early, so I bet this week’s BSD Now is put together early because of travel. I’m linking to it early for similar reasons.
ChiBUG is meeting tomorrow, Tuesday, at Giordano’s at 6. Go, if you are near, and ask joshua stein about his astonishing hardware hacks.
I am opinionated this week!
I’m still playing catchup so it’s as of a few weeks ago, but the version 8 branch of gcc in DragonFly has been updated from 8.1 to 8.3, with backported fixes.
Related: gcc 5 is out.
This week’s BSD Now covers (ecumenically) OpenBSD’s release, NetBSD 9, the FreeBSD jails book, and so on. Check the show notes for details.
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.
This timer fix enables booting DragonFly on AWS. Well, that and the ena(4) driver. I haven’t tried it yet.
If, like me, you’ve been running DragonFly for a long time, and you haven’t switched away from tcsh for your account or for root, you may not have ‘set autorehash’ in your .cshrc. Newer installs have it.
Put that into .cshrc if you don’t have it, and it’ll save 15 seconds of the rest of your life not typing ‘rehash’… assuming you can overcome the muscle reflex.
I’m really loading up with links this weekend; make some time to read today.
I’m still not making through all the stuff I need to link to, but this is enough to keep you busy for today.
Matthew Dillon has committed two changes, both to DragonFly 5.4 and to DragonFly-current. His note to users@ explains the details. I don’t have a date for 5.4.2 being rolled out, but I expect soon.
This is the commit I should have linked to yesterday, and was reminded by an anonymous commenter: git: sys/vfs/fuse: Add initial FUSE support. It’s not complete, and so isn’t built by default; check the commit for details.
Remember my Wyse terminal experiment with a DragonFly VM? I mentioned an odd output pause where the screen would stop updating until there was keyboard activity – or occasionally just die. That was an artifact of Virtualbox; running this now in Qemu has no such problem.
I now have a very overcomplicated clock! I’m running GRDC on this Wyse-185 connected as a vt100 to the virtual machine running DragonFly 5.4 in Qemu on my Windows 10 work laptop. It’s at 9600 baud so I can see the numbers morph. I find this aesthetically satisfying.