Because my memory is poor and my documentation skills are marginal.

Everything here should be taken as-is. Don’t expect too much in the way of accuracy. Sometimes, I document things thoroughly. More often, I do the markdown equivalent of a scribble on a post-it note. These a mix of those things and I can’t promise what’s written here was correct when it was written, let alone now. Is that enough of a disclaimer? Just to be completely clear. This is probably all wrong.

KVM on ancient tin

Getting KVM up and running on a decade old AMD CPU to serve ad-hoc VMs at home. Background on basic use of KVM as well as odds and ends of lessons learned about making OpenBSD run under KVM.

OpenBSD on the RockPro64

There are good guides out there to getting OpenBSD onto the RockPro64. I manaed to make a hash of it though so I recorded the resources I used to debork the thing.

Over-engineered home DNS

This is described properly on the home page. Suffice to say I like making my life more difficult than it needs to be.

Self-signed tls certificates for Unifi devices

I run Unifi kit at home for wifi and other things and so have various pieces of their software running on VMs and SBCs around the house. In the spirit of home-network over-engineering which motivates much of what I do, I decided that tls warnings were unacceptable leading to many a painful hour spent dealing with the different ways that each piece of Unifi software deals with certs. Currently this note only covers the EdgeRouter and Cloudkey devices.

ftdi serial devices on Mojave

I had a Dreamplug ARM7 device that I used for a long time as a Debian based, iptables firewall. I retired it when I switched back to OpenBSD and pf but kept it around. I recently decided to rebuild it and needed to get the ftdi based USB -> serial / UART device up and running on Mojave. This turned into a minor palava so I wrote it up.