After spending the majority of my personal computing adventures on my MacBook Pro last year, I received my final deprogramming session with the latest batch of macOS updates. Surveillance tech has now festered deep inside macOS Sequoia itself with the rollout of Apple Intelligence. Apple’s promises of groundbreaking privacy protections aside, I employ a strict zero-trust policy when it comes to accessing my personal data.
After my recent rant about Enterprise Linux, the company where I work became a SUSE Linux partner. Therefore, I’m giving Enterprise Linux another go. After initially looking at SUSE Linux Enterprise Desktop (SLED), I decided to go with SUSE’s rolling offering, Tumbleweed.
The Nginx mainline branch (currently version 1.25.3) has implemented support for HTTP/3 and I want it on my server. The first order of business will be to switch from the nginx stable branch (currently version 1.24.0) to the mainline branch. As Arch Linux provides both Nginx branches in their repository, it’s just a matter of performing a quick drop-in replacement.
I temporarily return to Fedora and am welcomed back by more breakage. The first thing I did after updating and restarting my Fedora laptop was to fire up the Cider app to connect to Apple Music. It immediately croaked with its dying words being Skia shader compilation error. That felt eerily familiar, as I remember facing the same problem on Fedora a few months back.
Earlier this year, Canonical decided to advertise the arrival of Ubuntu Pro by hooking up the following message in the terminal as users were issuing apt update: “The following security updates require Ubuntu Pro with ‘esm-apps’ enabled: (list of vulnerable installed packages)”. Predictable for anyone but Canonical, confusion ensued.
During an issue with a defective storage solution, I had temporarily (as in not added to fstab) mounted an external USB disk under /mnt/usb-disk on a Proxmox server to keep the backups flowing. A day and a reboot later, those backups started to fill up the local storage instead with unfortunate consequences. As they say, you really can’t fix stupid.
A few years ago I speculated in the article “Slackware Linux trivia, history, and things you didn’t know” that slackware.com was being hosted on Slackware Linux 12.0. My assumption was based on the host headers returned from the server. Those headers reveal that the webserver is Apache/2.2.22, coincidentally the last Apache patch ever released for Slackware 12.0. However, it turns out that I was very wrong.
After a few years with the Finnish cloud platform provider UpCloud, I decided to move my services to Germany and try out Hetzner Online. UpCloud has been excellent, but I felt like it was time for a change, and Hetzner Online offers a lot of bang for your bucks.
I wanted to enjoy a lazy Saturday morning by listening to some black metal on my Slackware 15 installation. However, before I could get to that, I had to connect my Samsung soundbar to my Slackware machine over Bluetooth. Unexpectedly, after establishing a connection, the devices immediately disconnected.
For the second time this year, our old FreeNAS storage platform went offline and left our Proxmox VE 6.4 servers in a continuous state of distress. This issue renders the Proxmox VE GUI unresponsive and thus unable to display information about the virtual servers it’s running.