I think/hope I cleared my backlog of BSD links.
- FreeBSD Graphics Blog – Getting Started With drm-kmod. (via)
- Berkeley smorgasbord. (via)
- Amazon Web Service EC2?a1???????NetBSD/aarch64???????. Probably need to be able to render/read Japanese for that link to work out. (via)
- Today I (re-)learned that
top‘s output can be quietly system dependent. - pfSense 2.4.4-RELEASE-p1 now available.
- unbound(8): DNSSEC validation enabled in default configuration.
- NetHack, OpenBSD, curses, tty. Curses as in the terminal interface, not as in Sword of Monster Calling -1.
- Configuration deployment made easy with drist.
- SoloBSD 11.2-STABLE-1206 is out.
- mports updates, mport package manager configuration feature added, and MidnightBSD security advisory site.
- Valuable News – 2018/11/24, Valuable News – 2018/12/01, and Valuable News – 2018/12/08.
- FreeBSD 12.0-RC3 Available. No, wait, FreeBSD 12.0-RELEASE out.
- pkgs.org – packages for as many systems as possible, including FreeBSD and NetBSD. (via)
- GOG Winter Sale – OpenBSD Highlights. (via)
- Cirrus CI support and FreeBSD.
- OPNsense 18.7.9 released.
- OpenSMTPD proc filters & fc-rDNS. (via)
- Otto Moerbeek on the Virtues of OpenBSD malloc(3). I need to keep a better eye on bsd.network; I can’t collate it like RSS. Or can I?
- A proposal for a new RPKI validator: OpenBSD rpki-client(1). (via)
- OpenBGPD – Adding Diversity to the Route Server Landscape. (via)
- FreeNAS 11.2 new features.
- NetBSD desktop pt.4: The X Display Manager (XDM). (via)
- PINEBOOK on FreeBSD soon. Joining OpenBSD and NetBSD. (via)
With the release of FreeBSD 12, I’ve love to read (and would even pay to read) someone write an in-depth review of how FreeBSD compares to dragonfly as in its current form today. But comparing the two given their shares roots.
Talk about the architecture choices (differences) over the years. Etc.
The link for the OpenBSD unbound item about enabling DNSSEC validation doesn’t say anything about that that I can see. I poked through the changes on the openbsd.org site and didn’t see it, either. (I’m interested because the last time I tried enabling DNSSEC on my own it caused much hard-to-debug breakage.)
I’ll go check openbsd-cvs on MARC next.
It got pulled out:
https://undeadly.org/cgi?action=article;sid=20181207141635
Ah, OK. Sounds like from the link they had problems, too, though not the same kind I had. Theirs was more of what could arguably be a(nother) DNSSEC design flaw: DNSSEC needs an accurate clock, but setting the clock (via NTP) requires a DNS query.