I recently migrated my Unifi controller from a bhyve instance in Triton to an LXC container in a Raspberry Pi. I won’t go into all the reasons why here, but suffice it to say that I had made some choices about my existing network that, while they made sense at the time, didn’t really jell with the way Unifi is intended to operate. I’ve been running a controller myself for over a year, and I already have a router and several spare Raspberry Pis laying around, so getting a Cloud Key or Dream Machine wasn’t something I was willing to pay for just yet.
The CDDL is not incompatible with the GPL. Anybody who says otherwise has an agenda. I’ve heard all the arguments. They’re all bullshit and FUD. I, of course, am not a lawyer. But I can read. This is written primarily to discuss the situation with the Linux kernel and ZFS. First, let’s review. The Linux kernel is licensed under the GNU General Public License version 2 (GPL). The effective clause of the GPL is in section 2, as follows (emphasis added).
Last week I presented on Triton at LOPSA LA and UUASC. I’ve got video this time! And slides, though most of the talk was live demos, so the slides leave a bit to be desired.
I’ve previously written about creating SSL certificates. Times have changed, and ECC is the way of the future. Today I’m going to revisit that post with creating ECDSA SSL certificates as well as how to get your certificate signed by Let’s Encrypt. Generating an ECDSA Key Since this information doesn’t seem to be readily available many places, I’m putting it here. This is the fast track to getting an ECDSA SSL certificate.
I have a different relationship with Star Wars than most people. Star Wars was origionally released in theaters fourty-seven days after I was born. The Empire Strikes Back was the first movie I saw in a cinema. I stood on the seat, transfixed on the screen from the crawl to the credits. Return of the Jedi was the first movie I remember seeing in theaters. I’ve seen A New Hope something on the order of two thousand times.