red hat enterprise linux (rhel) 8.0

Here’s my personal review of Red Hat’s latest, RHEL 8. It’s not much, so if you’re looking for something far more in depth, then you won’t find it here. Instead I look at it from the perspective of an end user who’s used older versions, and try to determine if I should use this latest version.

RHEL 8 was formally released 7 May 2019, a little less than a month ago from the date of this post. It’d been out in beta form before that, as I noted by a number of comments in various fora around the end of 2018. But I stayed away from checking this latest RHEL release, due in no small part to my less than happy experiences using RHEL 7 and its unpaid version CentOS 7.

From what I’ve seen so far it appears that RHEL 8 may actually deserve its primary version increase. The upgrades across the board are substantial enough. If I wanted a RHEL-like distribution with up-to-date tools, why not use Fedora? Because I DO NOT want to deal with Fedora’s peculiarities and periodic ‘bleeding edge’ breaking changes within Fedora releases just to keep up with the latest packages. All I ask of my Linux distributions is that they are reasonably up to date in the core tools and will work without special handling in just about any environment. There are a lot of distros that can do this, but Fedora isn’t one of them. I haven’t used Fedora since its late teen releases, and I don’t expect I ever will again. But it would appear that RHEL 8 now falls within that categorization of easily up-to-date and easy-to-install. Thank you Red Hat.

It looks like there might be just a tinge of desperation at Red Hat Central. I say this in large part noting how RHEL 8 is being launched. In the past, when I went to download and install a developer version of RHEL 7, I jumped through a fair number of hoops to get an ISO. After installation I was reminded periodically that my ability to install updates was time limited. RHEL 8 on the other hand is noticeably different. Everywhere I look and read there are articles about RHEL 8 as a development platform. When I went and logged recently into Red Hat  Developer, I was immediately led to the download section where I easily found and downloaded my ISO copy. After installation as a VM in Oracle’s VirtualBox (6.0.8 as of this writing) on macOS 10.14.5, and after registering with my developer credentials to keep my installation up-to-date, I was not greeted with any kind of time limitation warning. It still annoys me I have to register to get the updates, which is one big reason I prefer CentOS; CentOS updates are just a simple yum away.

I think that desperation might be rooted in the observation that Red Hat might not be relevant to a lot of developers these days. Red Hat’s biggest competitor I believe to be Ubuntu. I’ve read a number of stories where developers, especially AI developers, are now buying machines with Ubuntu desktop pre-installed. And I’ve watched Ubuntu pushing out not just into the server side but into cloud containers as well IoT images. Yes, I know all about Red Hat’s push with Kubernetes. But that’s countered in part that Red Hat is now owned by IBM, and I can assure you that I at least am not happy about IBM in the mix. That’s another reason I’ll get my images from CentOS and go elsewhere for my cloud needs.

RHEL 8 is actually using a fairly recent Linux kernel, 4.18, as apposed to RHEL 7 and RHEL 6, which stuck with a version 3 kernel, heavily patched. And the tools supplied in RHEL 8 are also fairly up-to-date; gcc is at version 8.2.1, git is at 2.18.1, and Python (or python3) is at version 3.6.8 (python2 isn’t even installed). So the quality of the tools in RHEL 8 is, in my not-so-humble-opinion, a big step up over RHEL 7, and about time. All of this is out-of-the-box.

There were some additions and tweaks. For example I added gnome-tweaks to get the Tweak Tool and enable dark mode via Adwaita-dark. I also enabled all the control buttons on the right corner of each window and enabled having the application’s control menu on the application’s left side. That last “feature” really bothers me. This is yet another attempt to copy an Apple macOS feature. That feature looks great on macOS, but it’s always looked bad on the Linux desktop. Seriously, if you want that look and feel then buy a Mac. And finally, for running RHEL 8 as a VM in VirtualBox 6.0.8 on macOS Mojave 10.14.5, you need to select running the VM’s desktop as a standard Xorg X windows system, rather than using Wayland. Wayland does not play well with VirtualBox and it hasn’t since Wayland was first officially released with RHEL, going back to VirtualBox 5.x. You pick that at the login screen (see the little gear on the lower right beneath where you type in your password). If you don’t do that you’ll see nothing but constant tearing and flashing of the virtual display.

My installation was bare-bones, just enough for the tools (compiler tool chain primarily) without any games or social media or office software. As pure as possible to just a desktop and basic developer tools. To that I added htop, Amazon’s Corretto Linux release (Java 8 212), Microsoft’s Visual Studio Code editor and IDE, and Microsoft’s PowerShell Core 7 Preview 1. The following three show htop, Visual Studio Code, and PowerShell respectively.

There’s a reason for these specific applications. The same applications run on macOS and Windows 10. That means that given the same languages (Python and Java, for example) or advanced C++ compilers that support the latest C++ standards (gcc 8.2 and Microsoft’s Visual Studio, for example) as well as the same CM tool (Git), then there is no longer any reason to remain committed to a single platform. Commit all your work up on Github, and then move from platform to platform as the need may be to get your job done. And I very much like the idea of PowerShell being common across all the platforms.

I believe RHEL 8 is going to be a very solid release, the best in a few years. The only issue is with other distributions, the biggest competitor being Ubuntu. I run a mod of Ubuntu from System 76 called Pop!_OS. It too has Corretto Linux, Visual Studio Code and PowerShell. I like Pop!_OS primarily because of its very excellent looking desktop out-of-the-box. For all practical purposes RHEL 8 has achieved parity with the latest Ubuntu release and derivatives.

Update January 2020

I deleted the Pop!_OS VM some number of months back because it seemed to have corrupted itself. I’ve only had one other Linux distribution do that, and it was Arch Linux.

On RHEL 8 I’ve replaced Amazon’s Corretto Java with AdoptOpenJDK ( PowerShell 7 is now up to Release Candidate 1.

virtual box 5.1 report – it’s pretty good

Screen Shot 2016-07-16 at 11.59.36 AM

Oracle released VirtualBox 5.1 last week, and today I downloaded the latest bits and updated my VB installation on my MBP. Right now the MBP is running with OS X Version 10.11.5 (I’ve resisted the urge to install the Sierra beta). I also updated the extensions package as well as the guest additions ISO.

Once VB 5.1 installed, I updated all my existing VM’s guest additions without incident. So far I have Mint 18 (seen above), Fedora 24, CentOS 6, Ubuntu 16.04, and Kali. Kali doesn’t have the guest additions as I want as pristine an environment as possible with those tools.

But this version of VB isn’t without problems.

  1. I can’t seen to install the guest additions in CentOS 7 (based on RHEL 7). I don’t know why but the tools can’t find the kernel headers, even though I installed the full gcc and kernel-devel packages. I suppose I could have dug around and found out why it can’t find the kernel headers, but I have four other working Linux distributions with additions, and I just didn’t feel like putting in the effort. Lazy, I guess.
  2. I tried to install PC-BSD. Initial live media boot and installation went swimmingly. Trying to run after the install (with the MATE, the KDE, desktops) resulted in a panic. After two attempts I gave up. If I need a BSD-like OS I have Mac OS X. And if I want Unix-like, well, I have all these systems around the house, including Arch running on three Raspberry Pi 3s. I have no shortage of OS playgrounds.

Other Software

I decided to try out Microsoft’s Visual Studio Code editor in the Mint VM. I’ve played with it a bit on Windows 10, Ubuntu 16, and my MBP, all directly on hardware and all without incident. But trying to install and run it on my Mint 18 VM didn’t work out so well.

Screen Shot 2016-07-16 at 11.51.43 AM

Screen Shot 2016-07-16 at 11.52.06 AM

I would have loved to have worked with the editor in the Mint 18 VM, but it looks like it’s not to be. I don’t know why the editor has a corrupted interface, but it’s totally unusable in this particular setting. I still have vi and gedit as a consolation.


One of the big claims with VM 5.1 is performance improvements. I use it now on my Windows 10 notebook in place of VMware, and on my MBP, and I’ve never thought it was slow. VMs seem to boot rather quickly, and the VMs operate efficiently once up and running. I’m quite happy with the way everything works.

After what I wrote about abandoning Oracle’s Java, and why, you might think my use of VB is a bit hypocritical, and you’d be right; it is. Unfortunately, I’ve found nothing that works as well, especially VMware. And I need a virtualization tool that works on my multiple notebooks, with as many different Linux distributions, as possible. VMware keeps getting worse and worse in that regard. I certainly don’t mind paying for a good software package, and I almost broke down and bought a commercial copy of VMware, but the free player has been so plagued with issues that it’s turned me off buying a license (or licenses, one for Mac and one for Windows). I’ve better things to do with my time than trying to get everything initially working.

I would have liked for PC-BSD to have worked (finally). But it didn’t and I refuse to go forum diving for old and/or cryptic information. Considering the definition of insanity, some might consider my continued attempts at getting FreeBSD/PC-BSD up and running in a VM (which I will do before committing hardware). Fortunately, I wasted no more than about 15 minutes before calling off the latest PC-BSD installation experiment.