There’s some code changes for callout, where the actual lines of code that trigger it are stored in the callout structure. It’s a little thing, but it’s a big thing if you need it.
Lots of BUG news this week; thank you all for the leads on groups to watch.
- Talking Jails at Semibug, 9 April 2019. Note the meeting has been moved up a week.
- “FreeBSD Mastery: Jails” and a new novella.
- April 9th Meetup. ChiBUG.
- Rusted ravens: Ravenports march 2019 status update. There’s some DragonFly stuff in there I haven’t had a chance to link to.
- How to use NetBSD on a Raspberry Pi. (via)
- Serenity: x86 Unix-like operating system for IBM PC-compatibles. Almost UNIX, almost BSD. (via)
- Before Unix: An Early History of Timesharing Systems. Influences on BSD.(via)
- OpenRA imported – game engine recreation for RTS games of the Command & Conquer family. (via)
- Project Trident 18.12-U8 Available. (via)
- Removing PF. (via)
- Silent Fanless FreeBSD Server – Redundant Backup. (via)
- LLDB/LLVM report for March 2019. NetBSD.
- Continuation of signal semantics improvements. NetBSD.
- iked curve25519 group number change. OpenBSD.
- Valuable News – 2019/04/01.
- Sega Dreamcast Running NetBSD. (via)
- UNIX and BSD Discord/Matrix Servers.
- BSD Router Project 1.92 is now available. (via)
On DragonFly, booting from a USB stick means your boot volume is usually /dev/da8. That’s a rather arbitrary distinction. As a bonus from the recent part-by-label device change, you can now find the boot disk in /dev/part-by-label/, named by the booted kernel rather than a device number. The commit message has a slightly better explanation.
There’s a bounty entry for Aarch64 support for DragonFly, on the bounties page. This is a difficult goal, but I think worth it. Add to it if you agree.
That somewhat symmetric title is to note a new device feature on DragonFly: if you use disklabel to label a disk, its parts will automatically appear under /dev. So, if you label a disk MYVOLUME, and it has 3 parts, a, b, and d, you will automatically gain a /dev/part-by-label/MYVOLUME.a, /dev/part-by-label/MYVOLUME.b, and a /dev/part-by-label/MYVOLUME.d.
Thanks to Aaron LI, you can now (actually, since December) run ifconfig without involuntarily loading associated kernel modules, with the -n option. See his commit message for an example.
I’m finally cleaning out some things I never got to post when new: last October, the DragonFly installer gained the ability to ask for terminal type, when used over a serial cable. Thanks to Diederik de Groot for that one.
(A rare combination… but when you need it, you won’t have an alternative.)
The binary package repository for DragonFly-current has been updated with the latest build of all packages, thanks to tuxillo and others on EFNet #dragonflybsd doing a lot of work.
Tuxillo noted: there’s new rust, thunderbird, firefox, nginx, several llvm versions, and a new chrome (version 72). freerdp is temporarily broken; use remmina with the rdp plugin instead. openvpn isn’t upgraded yet cause the build was with libressl, which is a broken combination – it’ll all be built with openssl in a future run.
A little thing: Matthew Dillon has made changes to vm_page_list_find2() which should improve performance in low-memory situations, though how much I don’t know. Mentioning it, cause every little bit helps – for knowledge and speed.
Because someone decided years and years ago that the CAM structures should be passed through to userland, smartctl, camcontrol, cdrecord, and some other tools will be broken in DragonFly-master for a few days. If you are on -stable (5.4) this won’t affect you.
Thanks to tuxillo and others, there’s a new build of dports on the way for DragonFly 5.4 that includes packages that weren’t building before – mongodb, kodi, mysql80, and I imagine more that I don’t know about. If the synth build is still running when you read this, you can look at its status page. If it isn’t running, the packages are of course in the normal place and you can use ‘pkg upgrade’ to get them.
Two minor things that were keeping me from mounting Windows shares on boot of my DragonFly system: the right location for nsmb.conf and using proper capitalization. I’m writing it here to save someone else 10 minutes of search.