Fedora

After Saturday’s post I wanted to take a step back and talk about some history that many have either forgotten or weren’t familiar with in the first place. Some may remember it quite well, but haven’t quite gotten the lessons right the first time around. Let’s talk about Red Hat Linux and the early days of Red Hat Enterprise Linux before it was even called that. Red Hat sets the standard My Linux journey started with Slackware Linux in 1996, completely by accident. By that I mean that I had never heard of Linux or sought it out, until I stumbled on a 4-CD set and decided I wanted to learn more. I was studying English lit and Communications/Journalism at a state school in the northeast corner of Missouri. Nobody I knew cared much about computers beyond games or running Word to write their papers. It was literally years before I met someone else who was an avid Linux user. It was a surprise to learn, a bit later, that Slackware was a Linux and that many distributions existed. As I learned more and more about Linux, though, something became clear: Red Hat was the popular choice. Red Hat was the Coca-Cola of Linux, even before its IPO in mid-1999.

I’m probably late to the party, but Distrobox has to be one of the best open source projects to drop in the past few years.

After a few tries to put Fedora on the MacBook Pro 2015, I auditioned a number of other Linux distros and wound up going with Pop!_OS. I gave Chrome OS Flex a brief spin, but it wasn’t quite my jam. If you like Chrome OS and have an old PC or Mac you’d like to give a little more life to, I give it a thumbs up. I was able to install some regular Linux apps on it as well as the standard Chrome apps, but found Firefox to be sluggish and generally just didn’t click with Chrome OS.

Apple has decided that my 2015 MacBook Pro isn’t deserving of the latest macOS, so I’m looking to run Linux on it to get a few more years out of it. My first plan was to put Fedora on it, but Fedora 36 and 37 have failed to " set a new efi boot target." Chrome OS Flex installed just fine, but I don’t know if I want to stick with Chrome OS long-term....

Today I was setting up some VMs on Fedora in Cockpit and decided to clone an Ubuntu 20.04 LTS image, which immediately pulled the same IP as the original. I hadn’t had that issue with CentOS or Debian, not quite sure why, but the culprit is a duplicate machine ID. Here’s how to fix that.

I’ve been doing a lot of “set things up and tear them down again” lately, and the combination of Fedora 37, Cockpit and the Cockpit Machines application, plus an old Core i7 machine with 64GB of RAM is making that a piece of cake. The Cockpit Project is a fantastic project that doesn’t get nearly enough attention. It’s a web-based graphical interface for Linux systems, and it can shave a lot of time (and reading man pages…) off basic system administration tasks....

Installed Fedora 37 today and it was a pretty smooth experience. No surprises there. One of the recommended applications (Apostrophe) looked interesting so I installed that and found it wouldn’t start. Poking a bit at the terminal I got a Python error that I chased down on google and tracked back to a missing package (webkit2gtk4.0). Once I installed that it ran just fine. Went to file a bug and found that I can’t log in with my Fedora Account Services (FAS) account because it had been associated with my Red Hat email....

A few days ago, Microsoft announced that it has released PowerShell under the MIT license for Linux (and Mac OS X). Perhaps surprisingly, this has brought a number of folks out of the woodwork to gripe about Microsoft… releasing something as open source. Microsoft isn’t perfect, not by a long shot, but this is not Steve Ballmer’s Microsoft. This isn’t Bill Gates’ Microsoft. The days when Microsoft and the open source community are mortal enemies are behind us....

Here’s a pet peeve of mine, because I see it time and time again: Folks work on software or projects, put in a ton of effort, and then do nothing to promote the project or release. (And, for bonus points, complain that they don’t understand why the project isn’t getting more attention!) This doesn’t mean developers have to do double-duty as marketeers and public relations folks. Well, not if they can pass the torch onto interested contributors who are happy to do it for them, anyway....