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.
I can’t remember ever having an issue with updating the firmware of my XPS 13 7390 on Ubuntu. Today, however, Ubuntu 21.10 (Impish Indri) decided to throw an ugly-looking warning in my face after proudly proclaiming that it had a new device firmware update ready to be installed. To add insult to injury, Ubuntu told me to reboot the system to install the new firmware, after GNOME Software correctly informed me that it had failed.
With the release of Tor Browser 11.0, I remembered that I have an onion site so I figured it was a good time to see how it was doing. However, I must have been sleeping in class because the Tor Browser informed me that the site was most likely offline.
Understandably, I was burning with a desire to upgrade the Windows 10 virtual machines in my Testlab to the latest and greatest from Microsoft. To my dismay, my old Asus G771JM Arch Linux-powered host did not meet (by a long shot) the highly artificial requirements to run Windows 11.
If your Fedora Linux installation had only one hour left to live, where would you go and what would you do? Welcome to another brand new installment of my adventures in enterprise Linux’ing.