Red Hat Enterprise Linux (RHEL) Reviews

We are using the full setup in Linux and use the enterprise edition. We're migrating a lot of things over. 

We like that it's open-source and fully secure. We've fully migrated to Linux, and we were able to move everything over from the Red Hat database.

Compared to earlier tools, we get more options, and it's very user-friendly. The patching, for example, is easier. It can also support many things. It took us about six months to realize the solution's full benefits.  

The solution is very user-friendly. 

The Red Hat Enterprise Linux scripting is very good. It is easy for us to access those parts in the Linux portion. 

The security is very good. It helps us to maintain overall security.

I have a Linux certification, however, they do have good documentation in order for users to get information about the product.

The management experience for patching is very good. We can do the patching through the portal. We can use it based on our own timing. If there isn't something in production, we can do the patching. The patching experience is very nice compared to what we had to deal with previously. For example, with Windows, the patching would happen whenever. We can control it via the portal, and it is very user-friendly now.

We only use the command line. We do not use the GUI. The graphical user interface is useful. However, we prefer to use the command line as we can do many more things. 

Red Hat Enterprise Linux has positively affected our uptime. It's very fast. If you have to do patching, and need to reboot, it doesn't take too much time to do that. It might only take one to two minutes. 

For the most part, everything looks fine. Everything is going smoothly. 

Right now, we need to get memory and CPU via the console. If it was available in the console so that we could adjust these two things, that would be ideal. 

I've used the solution for the last four years. 

The stability of the solution is fine. I'd rate it nine out of ten for stability. It's user-friendly and the downtime is low. It won't impact business.

The solution is not deployed across multiple locations. We have around 300 end users.

It is scalable. We can immigrate to servers and it won't impact the business. 

We know there are some issues, and if we come across some vulnerabilities, we'll work with support. If we get an error, we'll go to them and discuss the issues. We take advice from them on how to work through problems. 

Sometimes, we'll get some errors and we'll send them an email. Sometimes it takes too much time for them to respond. The support time could be better.

Neutral

We did previously use a different solution. 

I was not involved in the installation. I have not worked on the OS level and I'm not involved in the migration to the cloud.

We have eight to nine people on our team that may handle some maintenance tasks. If there are any issues, we can patch and fix them. We go through the portal to handle patching and maintenance. We'll check the system pre and post patching.

I'm not aware of the exact pricing of the solution. 

We did not evaluate other options. We've fully moved to Linux and used Red Hat Enterprise Linux to do this. 

I'm an end-user. 

We will be moving to the cloud only. I'm not directly involved in that. The main thing will be that soon everything will be in the cloud only. Currently, I work with the on-premises version only. It's on a VM right now. 

This is a good solution if you are handling migrations or your internal environment. It's user-friendly and you can connect with technical support easily. It's also very secure. 

I'd rate the solution nine out of ten. 

Red Hat Enterprise Linux serves as the foundation for our cluster infrastructure, allowing us to deploy applications and connect servers. We further enhance operational efficiency by deploying Kubernetes on top.

We chose Red Hat Enterprise Linux for its stability and well-rounded features and its proven track record of decades of reliable operation.

Red Hat Enterprise Linux's built-in security features and mandatory access control help to mitigate and secure the OS from threats.

Red Hat Enterprise Linux is well documented and anyone with a technical background can easily understand and use the OS.

Red Hat's image builder is helpful.

Building upon the industry's 95 percent adoption of Linux OS, our Red Hat Enterprise Linux with Kubernetes setup has helped our operations.

We have not encountered any downtime while using Red Hat Enterprise Linux.

Red Hat Enterprise Linux enables us to achieve security standards certification.

The performance of Red Hat Enterprise Linux is consistent between on-premises and cloud deployments. The key difference is simply a shift from owning hardware to renting cloud space for the operating system.

Red Hat is open source, so what we get with Red Hat Enterprise Linux is valuable support that is not included in the free version.

Recently, whenever we have applied a Red Hat patch, we have encountered errors requiring additional work. Unfortunately, the release notes for these patches are not always updated accurately, creating further challenges during troubleshooting. Specifically, the notes often fail to mention dependent packages that are also updated alongside the main package.

While the OS hardening feature is helpful, it could benefit from additional automation. A one-click package for hardening all files would significantly improve efficiency compared to the current manual process, especially considering the hundreds of files we've processed over the years.

The support has room for improvement.

I have been using Red Hat Enterprise Linux for eight years.

I would rate Red Hat Enterprise Linux a six out of ten.

Red Hat Enterprise Linux is deployed across multiple locations in our organization with 95 percent of our employees that use it.

To ensure optimal performance and security, we must prioritize installing operating system updates as they become available.

Taking the Red Hat administration course beforehand will significantly ease the user experience when using Red Hat Enterprise Linux.

I provide consultation to clients for their mission-critical applications. Its primary use case is running containers and microservices on Springboard.

My customers use versions 7.2 or 7.3. I have used versions 8.2 and 8.4. I have tried version 9, but I use version 8.4 specifically because it supports HighPoint RAID for storing the data, whereas the client applications run on the much lower version.

There are benefits in terms of price, security, and stability to reduce the risk of applications going down or something like that. A vast majority of systems are on Red Hat Enterprise Linux than on other distributions, which is another benefit.

Red Hat Enterprise Linux helps to achieve security standards certification. They use it in the PCI DSS segment, so it enables the applications to be compliant with all these security aspects.

Red Hat Enterprise Linux is very stable. It has been in the market for many years, and it is used by large organizations.

Their documentation and knowledge base are valuable. As an individual developer, whenever I have problems, it is easy to find the information. Their knowledge base is seamlessly integrated with the software. Whenever I have a question, it directly takes me to the knowledge base. It is well documented.

It supports scripting very well. Everything is scripted. A snapshot is taken in the VM, and the script is applied. It lends itself to better security and governance processes.

Its installation on a RAID or cluster system is something difficult. There are specific teams working on that. The GRUB configuration is also a little different from the other Linux distributions. 

In terms of additional features, as technology keeps evolving, the product will also have to evolve. For example, Microsoft Windows has come a long way. In Windows 11, there are so many features that are fundamentally the same as the oldest version, but there are other aspects or processes that have improved. macOS has also evolved over time. Similarly, in the Red Hat Enterprise Linux that I used in 2003 and the one that I am using now, some things are the same and some things have changed. Red Hat can continue to engage clients, understand the use cases, and update them.

I have been using Red Hat Enterprise Linux since 2002 or 2003. Red Hat has a vast variety of products. I have only been using Red Hat's operating system. I have not used Red Hat's other products.

It is very stable.

It is scalable, but I do not have experience in building hundreds of systems on a VM.

I have not used their technical support at all. I only use their documentation portal for self-support. Our production support team interacts with Red Hat's support team.

As a developer, I use both SUSE as well as Red Hat Enterprise Linux. My personal preference is Gentoo, but no one runs Gentoo on a production system. Gentoo is better in terms of customization. You can choose what you want.

I am not directly involved in its deployment, but I am planning to build an application. At that time, I will be deploying it myself. In the organization where I work as a consultant, there is a segregation of roles. There is a production support team, there is a development team, and there is a DevOps team. I am a part of the development team.

Its initial setup is straightforward. It is not complex. It also depends on the architecture, high availability, etc.

In terms of deployment, earlier, it was on-prem, but now, it is on the cloud. My client runs about 150 VMs on the cloud in the production, staging, and QA environments. Most of the things have been consolidated into VMs. The migration is complete. It was not that complex.

I have not measured that, but it should pay back for itself easily. The ROI should be reasonable. The cost over a period of time should be minuscule. As compared to other OSs, it is better to go with a big, known, and trusted vendor.

As a developer, I pay around 10,000 Yen, which is around $100 per annum for support. SUSE and Red Hat are typically the same without standard support. The pricing is not a big deal. Enterprise customers will pay for the support. Enterprises have the money for one or two products like this that are reliable and supported.

As a consultant, I advise customers to go for support. You mitigate risks by having support. For your personal usage, you can manage without support, but when it comes to the enterprise level, you need to delegate things to people, and it should be through the proper channel. You need a proper point of contact.

I would advise following the best practices recommended by Red Hat. It will minimize the downtime of the application or system. Partner with the vendor and get that support. Know the business case and build a strong relationship with the vendor. Trust them and tell them your use case, and they will come up with the best solution possible.

I am not a big authority on Red Hat or other Linux or Unix products. Only recently, I have been exposed to the concept called hardening and penetration testing. I do not know whether Red Hat provides a hardened version of the OS. My basic distribution is Gentoo which provides a hardened version of Linux. On the client side, the organizations we work with have different departments, such as the security department and the compliance department. For security, they work with various options that are available. For penetration testing, we engage a penetration testing consultancy company once a year.

Overall, I would rate Red Hat Enterprise Linux a nine out of ten. 

We use Red Hat Enterprise Linux as an infrastructure support operating system across both x86 and s390 platforms. Specifically, we are running it on x86 Intel and Linux s390 mainframe on Zynq.

Red Hat Enterprise Linux is a stable operating system. We recently upgraded the majority of our systems from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8. We were able to automate most of the upgrade process and did not encounter any major issues. As a result, we were able to bring our systems up to date quickly and easily. This is a major advantage of using Red Hat Enterprise Linux.

From an automation standpoint, we have been able to automate some of our patching workflows. This has definitely saved us time and money.

From a security and compliance standpoint, it is easy to maintain compliance. This is mostly accomplished by patching Red Hat Enterprise Linux on a frequent basis. The availability of security patches is also quick, which allows us to keep up with our client requirements quickly. Red Hat usually does a good job of making fixes available in a timely fashion, so we can remediate high-priority issues when they arise.

From a containerization standpoint, Docker and Podman now give us the ability to move workloads and structures around with little effort. It is very flexible and consistent, and the results also provide us with a stepping stone as we move towards an orchestration platform like OpenShift. Our ability to run Podman on servers and then migrate those Podman deployments to OpenShift is very beneficial.

The most valuable features are ease of support and the ability to run a read-only course on the operating system.

Red Hat Enterprise Linux is easy to maintain. We currently use Red Hat Enterprise Linux 7 with Docker for containerization. With Red Hat Enterprise Linux 8, we are moving to Podman, which is a native container runtime that is part of the operating system. 

I suggest that Red Hat move to a continuous delivery model instead of major releases. I know that this is a trend for many middleware products. We do not have a major release network. We only have monthly or quarterly roll-on releases on our continuous delivery model, which reduces the impact of a major version. This would probably be the easiest change to make.

The technical support has room for improvement.

I have been using Red Hat Enterprise Linux for two years.

Red Hat Enterprise Linux is stable.

Since we run a number of hypervisors for all of our real systems, I believe that a lot of the scalability comes from a level higher than the operating system. However, Red Hat Enterprise Linux can accommodate these tools.

Red Hat support could be improved, and they should have a better relationship with IBM and VMware. This is because a lot of what we do involves working with IBM, both from a hardware standpoint and from a hypervisor standpoint. We have a long history with IBM, and we are now starting to work more with Red Hat on OpenShift private cloud solutions and other tooling. However, Red Hat and IBM are not on the same page. They are still very different companies, and they don't always know what the other one is doing. This can lead to contradictory information, inaccurate information, and frustration for customers. I think there is a relationship between Red Hat and IBM that could be improved. If Red Hat and IBM could work together more effectively, it would put customers at ease and make them more confident that they could get the work done. It would also help IBM and Red Hat to better understand each other's products and services, which would lead to better customer support.

For example, we recently had an incident that started as a severity two on the scaling. A number of our account representatives called and emailed us, saying, "Hey, we wanted to let you know that you have an open case. We need some help with this." The incident was not a production outage, but it was preventing us from doing something, so there was an indirect production impact. After about ninety minutes of back-and-forth communication, we were told, "Okay, go ahead and bump it up to severity one. That should get traction." We did not hear from anyone for four hours. This does not happen every time, but in this case, it needed to be dealt with well before four hours. It made things more difficult than they needed to be. Sometimes the support is an eight out of ten, and sometimes it is a four.

The end result was still good because they acknowledged what happened and got everyone together to resolve it but it was not done in an efficient way.

Neutral

The initial setup of Red Hat Enterprise Linux is very straightforward. It is not much different from any other Linux operating system. Most of the things we need to consider when deploying Linux are relatively standard. Therefore, Red Hat Enterprise Linux is easy to deploy and maintain. If we know how to administer Linux operationally, then Red Hat Enterprise Linux should be easy to deploy.

I do not know enough to give a comprehensive answer, but other operating systems are in use at my company because they have more favorable licensing terms. This is a major factor in why we do not use Red Hat Enterprise Linux everywhere.

We evaluated SUSE Linux Enterprise and a few others. Depending on the computing platform, it is sometimes better and sometimes not. For some of our environments that are running on s390, SUSE Linux Enterprise gives us a better price point. However, for some of our other environments, such as x86 on VMware, it is more valuable. It is a better financial move for us in those cases. Therefore, the value of SUSE Linux Enterprise changes depending on the computing architecture.

I give Red Hat Enterprise Linux a ten out of ten.

We have a requirement to have a Linux operating system.

I'm not sure how our developers are building their images. I believe they use some desk start products.

We use SUSE Linux Enterprise for Linux on the mainframe. In a particular enclave, we have some government contracts where we use Red Hat Enterprise Linux for a number of reasons, including licensing for hosts. These hosts are hosted with OpenShift. We use Red Hat Enterprise Linux for all our Bastion hosts and OLS for our other hosts.

The Red Hat knowledge base is generally an eight or nine out of ten, but it can be difficult to get the information we need. The initial level of support is a six or seven, but it improves as we escalate the issue.

I am a Federal Contractor. Red Hat Enterprise Linux is one of the FedRAMP-approved operating systems, so the government is comfortable with using it. That is why we use it, even though it is a bit outdated. Most of our software runs on Red Hat Enterprise Linux because we work in Identity Access Management. For example, Oracle Identity Stack runs on Linux, so we have to use Red Hat Enterprise Linux. We follow very strict security protocols, and we use Ansible to enforce them. Red Hat Enterprise Linux is the easiest way for us to do this.

Red Hat Enterprise Linux is a trustworthy and highly scalable operating system. The federal government needs an operating system that they can rely on, with enterprise support and long-term service. As well as being stable and well-known within the community.

I have not yet experienced a disaster recovery scenario, but resiliency is important, and risk is very reliable. The auto logs are very clear. Additionally, with those support communities, it is straightforward enough to understand what we are looking for and to eventually resolve the issue.

I actually like the in-place upgrade that Red Hat Enterprise Linux offers. It has made our upgrade process from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8 much easier than we originally thought. 

I know that many people prefer in-house support, but I personally prefer Red Hat's support. It is easy to get in contact with their support team.

Even though it is not directly related, the fact that Red Hat Enterprise Linux and Ansible are closely related makes it easier for us to move forward.

The package management, repository, and satellite repository are easy to use.

I am a bit biased because my client is air-gapped. This means that we cannot connect to the internet, so all of our operations are disconnected. I would like to see better support for disconnected operations. For example, the in-place upgrade from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8 initially relies on a lot of online resources. This makes sense, but it would be nice for a consumer or integrator like me to be able to say, "Hey, we need an offline solution so we can upgrade our government clients on-premises." Red Hat does provide instructions on how to create a repository, but the instructions are not very clear. This leaves us scrambling to figure out why we are missing a repository in our satellite image. Red Hat should provide a way to mirror repositories or at least provide a solution for us to bubble up packages throughout the entire process.

I have been using Red Hat Enterprise Linux for four years. We started with Red Hat Enterprise Linux 6, and we upgraded to Red Hat Enterprise Linux 7 in an airgap environment. We are currently in the process of upgrading to Red Hat Enterprise Linux 8.

Red Hat Enterprise Linux is stable.

Red Hat Enterprise Linux is scalable. It is deployed in a 10,000-plus enterprise company.

The support team is always direct and easy to find. Their answers are so helpful that I have not yet had to call them. I also appreciate how they approach troubleshooting. They don't assume that you're doing anything wrong. Instead, they try to educate you on how to fix the problem. In my experience, the support team has always been very positive.

Positive

I have experience with most Linux operating systems, including distributions like Apache, Debian, CentOS, Fedora, and others. From my perspective, Red Hat Enterprise Linux is not necessarily the top standout product, but I know that it is a product that I can rely on. It is the standard image that enterprise users in the community will use. We can rely to a degree on the standardization of how packets are used to support it. However, it does not stand out to us as much as the other products. Nevertheless, I know that it will have a positive partnership with us. Red Hat Enterprise Linux is a more suitable operating system for enterprise environments in terms of stability and reliability.

We are currently in the process of reviewing our initial solution for upgrading from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8. The in-place upgrade for the airgap environment is an area where we are still struggling to understand the documentation. However, Red Hat has been very supportive and has offered us pathways to move forward. We do not have much to say at this time, as we are still in the middle of the process.

When we upgraded Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7, it took us around six months due to external factors not related to Red Hat Enterprise Linux.

Our client has a direct subscription to Red Hat.

I give Red Hat Enterprise Linux an eight out of ten. I am not a firm believer that everything is perfect right out of the gate. Everything can be improved. I am a little biased. I wish there was better support for offline environments. I understand that I am in the minority in this case, as everyone is connected to the internet now. However, as a federal contractor and integrator, we have requirements that we must meet. It is not fun having to download binaries offline and then figure out how to set up our own repository. These are not straightforward tasks like Red Hat telling me what to do. We just wish it was easier to do things like patch management. Perhaps there could be more support for air gap environments. These are not environments where we can temporarily connect to the internet. They have never seen the internet.

Depending on our customer's environment, sometimes they have GovCloud, but we still use Red Hat Enterprise Linux images there. Sometimes the customer can't use that so we use the offering from CentOS. But we still try to match it with CentOS.

The reason why some clients don't use Red Hat Enterprise Linux on the cloud is not because of security concerns. I think it's more about cost and their current contract situation. They need a low-cost, open source alternative, and our recommendation would be CentOS. However, many clients are not ready to pay for the enterprise edition of Red Hat Enterprise Linux, so they may choose to scale back their plans.

I have not used the Red Hat Enterprise Linux knowledge base strictly. I have only used the Red Hat Enterprise Linux support.

Clients who use Red Hat Enterprise Linux on the cloud, typically use AWS GovCloud. As a government integrator, we strive to design our solutions in a way that does not lock our clients into any specific cloud provider. This is why we chose Linux, as it can be run on any cloud platform. This flexibility is important to our clients from a price contract perspective. For example, Amazon provides Kubernetes services, among other things. We try to figure out open source solutions or at least architecturally determine them and provide them to our clients. For example, we can tell them that they can move all of their GovCloud data to Azure or Google Cloud. Government agencies really like Amazon right now because it is FedRAMP. However, for other classes that are not government or commercial, we try to introduce them to the CentOS perspective so that they can get a taste of the upstream.

We do not use the image builder tool provided by Red Hat. Instead, we use the one provided by Amazon. We take a base image, coordinate it with Ansible, and provide it to any environments that have used the cloud. For on-premises solutions, we strictly use manual processes.

I don't have a perspective on the golden image, which is at least with our client. The parts that we use are always evolving, so we don't really maintain the golden image. We do have a relative backup of what we deployed to, but we don't necessarily have a strict golden image.

Migrating workloads between the cloud and the data center using Red Hat Enterprise Linux is not entirely applicable to us. We did migrate from on-premises to the cloud at one point, but migrating from Red Hat Enterprise Linux on-premises to Red Hat Enterprise Linux in the cloud was not a concern for us. We knew it would be stable and fine. The main concern was migrating our customer data from our enterprise to the cloud.

If someone is looking for an open source cloud-based operating system for Linux instead of Red Hat Enterprise Linux, I would like to eventually drive them over to Red Hat Enterprise Linux, but I would recommend starting with CentOS. CentOS is a good gateway OS because it is very similar to Red Hat Enterprise Linux, and the knowledge transfer between the two is very straightforward. This makes it a good choice for users who are new to Linux, or who are looking for an OS that is compatible with Red Hat Enterprise Linux.

I use it as an EC2 Web Server.

It was needed for FedRAMP Moderate compliance.

The ready-to-go AMI is a valuable feature.

It does not pass the RHEL8 STIG standards without a lot of extra work.

I have used the solution for one year.

I previously used CIS RHEL 8 Level 2.

Check it to verify costs.

I did not consider any alternate solutions.

It does not pass the RHEL8 STIG standards without a lot of extra work.

We are using Red Hat Enterprise Linux (RHEL) primarily in the health care industry for AI modeling and edge computing. One use case involves specific monitoring in a room with equipment and hardware.

I'm keen on this product because everything works as expected. It has embedded compliance features. We expect more in version 10. The keynote mentioned embedded OpenSCAP reporting, which is something everyone wants.

Red Hat Enterprise Linux has a lot of specialized documentation. Typically, people search on the Internet and find solutions by trial and error. However, everything about Red Hat Enterprise Linux is there in the documentation. You only need to follow it correctly. 

The security features have room for improvement, especially for highly regulated industries like health care. That's why it isn't the primary OS in health care. It would be great if they added some features to address the specific challenges health care providers face. 

It isn't hard to patch, but migrating between versions is difficult. We have the the latest version, but the previous version is still working very well. It's hard to leave a working version to upgrade. I would like more AI features, but those will be added to the next version. We are in an AI age, and it's an area where we need to keep pace. 

I have been using Red Hat Enterprise Linux since version 3, starting around 2000. Currently, we use version 9.4.

The stability of Red Hat Enterprise Linux is excellent. I have nothing negative to report in this area.

Scaling Red Hat Enterprise Linux as our needs change has been good. The older versions continue to work well even as we introduce newer solutions.

I rate Red Hat support nine out of 10. They provide competent support and help resolve issues quickly. You don't need to spend a long time searching for a solution. I don't rely on them much, but it has been a big help for my colleagues.

Positive

I have been using Red Hat Enterprise Linux for many years, so it is my default choice when selecting an operating system.

I'm a technical guy, so I'm not dealing with the money side of things, but we've seen a return on investment in terms of time saved due to the good documentation and support. 

Red Hat Enterprise Linux is expensive, but I'm not paying anything because it's the company's money. However, it's priced comparably to other enterprise Linux solutions. It costs a lot because you have a large staff working on the concept and improving everything. There is an open-source developer part that is free, so you can test everything before buying it. 

I rate Red Hat Enterprise Linux eight out of 10.  I know this is a good product because I've used it for many years, and it continues to improve. The OS is great, so I continue to use it. If I'm working on a new project and given a choice between another solution and Red Hat Enterprise Linux, I would always choose Red Hat for the community, support, and documentation. 

There's a free developer version. If you are thinking about purchasing Red Hat Enterprise Linux, you can try the developer version for free. Practice using Red Hat Enterprise Linux, and you will see the difference between the other distributions and Linux. If you want the product to perform at an enterprise level, you need to learn the product. There a plenty of tools and also the Red Hat Academy.

Our primary use case for Red Hat Enterprise Linux is to deploy OpenShift solutions on the cloud.

We use Red Hat Enterprise Linux with AWS, GCP, Azure, and Oracle Cloud.

Red Hat Enterprise Linux offers easy migration between cloud platforms, a crucial advantage for businesses. For example, we recently helped one client move from AWS to Azure and another implement a VPN solution using both Oracle and Azure to leverage the strengths of each platform.

It offers a comprehensive knowledge base that can be accessed through the Red Hat portal.

Red Hat Enterprise Linux helps support our hybrid cloud strategy.

The upgrades and migrations are straightforward and typically performed when introducing new hardware.

Red Hat Enterprise Linux's most valuable feature is its seamless integration with Kubernetes, a powerful platform for automating the deployment, scaling, and management of containerized applications.

Red Hat Enterprise Linux should enhance its support for commonly used application servers such as JBoss, Tomcat, and Apache.

I have used Red Hat Enterprise Linux on the cloud for five years.

I have a Red Hat account for client support, and their technical support is excellent.

Positive

We have used other Linux solutions, such as Ubuntu, SUSE, and Debian, but the primary difference lies in the level of knowledge and support provided. Red Hat excels with a comprehensive support portal, while SUSE offers less extensive support, and Ubuntu provides no official support options.

The initial setup is complex. I rate the complexity as two out of ten, with one being the most complicated.

Our clients see a return on investment within the first year.

The licensing for Red Hat Enterprise Linux in Peru is very expensive. On a scale of one to ten, with ten being the most expensive, I would rate the cost an eight.

We leverage Red Hat's Hybrid Committed Spend program to procure and implement Red Hat Enterprise Linux.

I would rate Red Hat Enterprise Linux eight out of ten.