If you are using urtwn(4) for your USB network connection, it now supports the Edimax EW-7811Un chipset? model?.
Yay, another week that overflowed with links!
- Creating a wireguard connection between my home and colo.
- How I configure dma for mail delivery in jails on my internet hosts.
- “OpenBSD Mastery: Filesystems” Status Report.
- New FreeBSD Quick Guide: Video Playback on FreeBSD.
- Support for ‘kill -SIGNAME …’ was added in 4BSD.
- 3D printed FreeBSD desk toys.
- Deploying FreeBSD on Oracle Cloud.
- “Return of the Emperor” – text-based game.
- Best laptop for OpenBSD? From the comments: jcs.org’s list.
- Valuable News – 2022/09/05.
- g2k22 Hackathon Report: Martijn van Duren on
snmpd(8)improvements. - OpenBSD may soon gain further memory protections: immutable userland mappings.
If you’re moving your dsynth build to a different machine, there’s now a ‘list-system’ directive that lets you recreate the same setup in a new place.
It’s not possible right now, but there’s people looking to implement it.
Predrag Punosevac has some notes on how he cleaned up some HAMMER drives and freed up half his disk space.
This will matter most to you if your connection to the Internet is poor: fetch(1) now will time out on data transfers too.
I mentioned a new committer for DragonFly, Sergey Zigachev, recently. He hasn’t shown in the commit logs for DragonFly directly – cause he’s fixing up dports. I’m mentioning that because the amount of work that goes into dports to keep all those ports working on DragonFly is separate and unseen – but necessary.
Welcome Sergey Zigachev, new DragonFly committer who has already committed an amdgpu fix.
If you pay attention to your daily security run emails on your DragonFly system, you may see entries like this:
+nlookup() at nlookup+0x623 0xffffffff806eff13 +kern_rmdir() at kern_rmdir+0x25 0xffffffff80706db5 +sys_rmdir() at sys_rmdir+0x4c 0xffffffff80706f0c +syscall2() at syscall2+0x11e 0xffffffff80bd9f9e
I see it on the machine where I run this Digest, as the caching mechanism adds and deletes files rapidly. Matthew Dillon has placed it behind a sysctl, so your messages log will be a little less noisy by default.
makefs(8) now supports HAMMER2 on DragonFly, so you can create HAMMER2 file system images, same as a CD image or a DOS disk.
When you are setting up a DragonFly machine on Hetzner, pay attention to this bug report for dhcp setup. The short answer is “use dhcpcd”.
Ian Grindley has created a BSD theme for rEFInd that covers all the BSDs – including DragonFly.
An interesting thought: since HAMMER2 is intended to be a multi-master file system, it has to figure out – and quickly – which is the most up to date versions of any given file. That means you could have multiple versions of a file existing at the same time until that decision is made. That wouldn’t be visible from a user perspective.
Hopefully there’s a new ISO/img on the mirrors for DragonFly 6.2.2 by the time you read this – or you can just update your installation. The changelog is short, because this is a bugfix-level release. Also, don’t forget there’s a new set of binary packages out; update that too if you haven’t.
If you’re interested in having virtio_console on DragonFly, keep an eye on this bug report.
There’s a new dports build, and there’s been some updates so a new point release to 6.2.2 for DragonFly is a good idea. The new binary packages are available now with ‘pkg upgrade’, and I’ll work on 6.2.2 over the next few days.
mlockall(2) in DragonFly has been revamped for compatibility with other implementations. This should have no obvious end user impact, other than a bit easier to port stuff. I want to mention it to note the work done.
You can now set a description for a network interface on DragonFly. Don’t use ETH0, please.
If you are trying to use both NAT and IPv6 with pf on DragonFly, there was a bug (seen here with FreeBSD) with :0 where it would use link-local addresses. It’s now fixed.