Red Hat Enterprise Linux (RHEL) Reviews

We use the solution majorly for JBoss, Apache, Java workload, and Comcast. We also use it for Apache Sattelite to do all the patching and database management. We use it for almost everything. We were a pure RHEL shop, up until recently. 

The most valuable feature is Satellite. Its consistency in patch upgradation is great. For the ten-year lifecycle, we have been able to rely on it and not worry if the patch will break. We do not need additional patching features since it covers everything.

The Modules feature is awesome but it could be even better.

We have been using the solution for 25 years.

The solution is stable. I have never remotely questioned its stability. The downtime is rare. It is usually a vendor's application issue unrelated to it. 

My company only has one complaint; we have been using it for more than seven years out of its ten-year lifespan and have yet to receive any version update. The drivers have become stale. We are trying to upgrade them manually. It would be nice if they had updated the drivers. If they do not update them, the solution will end soon. They should prevent it from crashing every time we try to update it. We are still rolling Ansible to automate some of the functions but, it is complicated to process with a vast sync of firmware and drivers.

The solution is scalable. I am a Satellite owner and we've had scaling issues with it. Those issues are mostly because my company didn't make it scalable in the right way.

They have their own expectations of how to make something highly available. And Satellite doesn't fit into that. 

I rate the solution's technical support as nine out of ten, as there is always room for improvement. I never had an issue with the support services. It is good and worth the value. 

I don't usually put up a ticket for every minor error. I am an expert and know the technicalities required to resolve the issues. So, whenever I contact them, I expect it to get somewhere. Because most of the time, the executives put more than one problem in the same ticket unrelated to another. It becomes more complex and confusing.

Positive

Red Hat Enterprise Linux generates a return on investment. We have everything on it. We have Windows servers for SharePoint and multiple cloud providers as well. In addition, we have OpenShift and Docker Enterprise, and some other open-source applications.

The solution is a good value for money. They keep adding up essential features to the specific subscription plan. I am also not a big proponent of top-level open-source applications as they do not provide support services. Whereas, with Red Hat, I can call them for queries and get answers immediately. In comparison, open source doesn't have that facility. Even if you hire a support vendor, they just give their opinions and try to help but they don't own the project.

At the end of the day, we have a 999.99% reliability of only 20 minutes a year of downtime with Red Hat. It is impossible to get that with open-source vendors as sometimes the applications might break if it doesn't notify about the changes on time. Conversely, Red Hat Enterprise Linux has a ten-year life cycle assurance, so we don't have to worry much. Also, we are in a TAM program. Thus, we can call the support team immediately for any issue.

Our organization constantly evaluates other options, as Red Hat Enterprise Linux's cloud version doesn't offer new features. Other than that, we go back and forth using Centralized and Rocky Linux. We prefer the ones we don't have to pay for the licenses.

It has a strong security posture. I did a SELinux contract for my current company. Compared with open-source alternatives, Red Hat Enterprise Linux provides better support services and reliability. Also, we are rolling out a new Ansible platform for insights. It gathers information about how many jobs we have, how long they take to complete, etc.

We need to manage vulnerabilities for a massive base of clients' systems. We don't use open-source apps for it like Red Hat. We have a third-party tool as we straddle different compliances. However, Red Hat is great about security announcements. I can call them anytime for an update as well. But it is challenging to work with the vendor for scanning machines. It does not know how to work with Red Hat packaging version numbers.

I rate the solution a nine out of ten.

Our company uses one of the solution's varieties, mostly CentOS. We are restructuring and moving to the licensed version of RHEL and its derivatives. 

We use both RHEL 7 and 8 mostly in the cloud but also have a small data center where the solution is used on bare metal. Our team does a lot of AIML work where we set up instances to run simulations. 

We are moving a bit into Redshift because we do not have many staff members with containerization or Kubernetes experience. 

We run most things on the solution and its impact has been huge. We do have a few items on Ubuntu but question its use. Conceptually, Ubuntu is for amateurs and RHEL and CentOS are for professional organizations with hardened security. 

The YUM repository is valuable. We are in an interesting situation because we cannot have access to direct YUM or browser repositories so we have to copy to a Nexus server and pull from there. From what we have seen, pretty much everything is available right there. 

The solution's use of Kubernetes as an internal or core process on the system is brilliant. You eventually get to Kubernetes whether via Redshift or other tools and do not have to worry about your hardware because you deploy and push to the infrastructure without worry. 

The Cockpit makes it very easy to maintain systems because you do not have the overhead of running gooey but still have the interface. I am a Linux person and had issues with Windows because they required gooey on servers when it was not necessarily needed. 

The solution is moving away from CentOS and there are growing pains from the customer's perspective. It was purchased by IBM and they are for profit which everyone understands. There is a huge shake up right now because customers who run CentOS do not know what to do with all their systems. One of the reasons CentOS is used for government offices is its security feature that does not change because it occurs after route. The solution placed CentOS in the middle so government customers do not trust it. The way the rollout occurred caused a lot of mistrust with Red Hat. 

The SELinux is great but the Amazon security features cause issues. For example, we run RHEL and CentOS on AWS but they control the cloud and do not give us access to security features. We have to go through multiple layers to deploy an instance. Something that could be controlled with a firewall or blocking ports is now controlled by security groups inside AWS that we cannot access. 

I am newer to the solution but our company has been using it for a long time. 

I previously worked with an Intel customer who used a lot of CentOS, so I am aware in that sense. I am very familiar with the YAM and DNF. I have even played a bit with Rocky which is not specific to the solution. 

My work in systems and software supports one of our teams. 

Technical support staff are personable and quick to get to problems. Support is better than other vendors and I rate it a ten out of ten. 

Positive

I used to work for a government organization that was heavily into AWS. One of the reasons they embraced open source was because Oracle was too expensive. They put everything into AWS rather than open source, so they will soon be in the exact same position where everything is proprietary. 

The solution is easy to set up but sometimes there are issues with custom software deployments. For example, we want to use Ansible in RHEL 8 but the software is only supported in RHEL 7. We question whether we should install an old version of Python to get things to run. 

The solution is pretty easy to troubleshoot. 

Our organization is huge but I handle the setup for instances in our small data center.

I do not deal with money, but I see an ROI in terms of the engineers' skills because they can reapply them to multiple RHELs and incidents. 

The solution is moving away from its open source roots and licensing is a little bit of an issue. 

We use Ubuntu, but not much. 

Primarily, we are dedicated to RHEL and CentOS to the point that we do not see Windows as a viable server option. Microsoft's cloud is getting traction but it only makes sense if you have a solution meant for Windows. 

We also use Redshift and Cockpit. There is consistency across products so they are backward compatible with familiar operations. For example, you could use RHEL 8, YUM, or DNF because the syntaxes are identical.  

The solution is very into Ansible and we are trying to drive everything to it.

Look at the security features of the solution and compare them with other options. Open source is great, but at the end of the day, you need someone supporting the product. Another option is to just listen to groups that write on the internet, but you have to decide if you trust that along with their adversaries. 

Government offices have to worry about adversaries from other countries because the code they use is unclear. The idea of open source is to be able to evaluate the code but it is not clear if anyone actually reviews it. 

I rate the solution a ten out of ten. 

I use Red Hat Enterprise Linux to create directories and files and configure security settings for the Red Hat Certified System Administrator exam.

The knowledge base offered by Red Hat Enterprise Linux comprehensively covers the fundamental knowledge required for the Red Hat Certified System Administrator and Red Hat Certified Engineer certifications. My experience taking the Red Hat examination was positive, and I am satisfied with their product.

I can easily work with Red Hat OS because it is user-friendly, even for manual tasks. While it may be as expensive as Windows, they offer a four-month trial and provide cloud access. This is valuable for understanding Linux concepts and working within the Linux environment. Overall, it's a great learning experience.

We prefer not to install the Linux OS manually, so we opt to work in the cloud instead. The cloud platform provides a real-time experience, enabling us to practice for exams easily and enhance our Linux knowledge. This proves highly beneficial for students pursuing Red Hat certification.

While preparing for the Red Hat administrator examination, I worked with the cloud platform, which was generally good but occasionally experienced some lag. Sometimes, the platform would be very slow, making it difficult to open labs. It could take around 30 minutes to start a lab, and there were limitations on data persistence. Any work or files created would only be available for one week before disappearing, requiring recreation. This lack of long-term storage is a disadvantage of the Red Hat Cloud platform.

I am currently using Red Hat Enterprise Linux.

I would rate the stability of Red Hat Enterprise Linux seven out of ten because of the lagging.

Red Hat Enterprise Linux is scalable.

The support team was helpful in addressing the lag in the cloud.

Neutral

I used UNIX before switching to Red Hat Enterprise Linux. UNIX did not provide adequate support for developers, making it challenging to work with. Though it's open source, UNIX lacked the features that we needed. So, I transitioned to Red Hat. Red Hat offers developers extensive support and access to technologies like OpenShift and Kubernetes. This makes it easier for developers and large companies to manage workloads and adopt new technologies.

I installed UNIX on my laptop and experienced no lag, unlike the lag I've encountered in the cloud with Red Hat Enterprise Linux.

Installing Red Hat is easy. We download the file and run it in our labs.

One Red Hat license costs USD 131, which I find reasonable.

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

We have 15 members in our group that use Red Hat Enterprise Linux.

I recommend Red Hat Enterprise Linux. It's much faster than UNIX and offers extensive management support, making it valuable for startups and engineering developers.

We use Red Hat for everything or we have a Red Hat derivative.

We use it on-prem and on the cloud. We use it in a hybrid cloud environment. We see it everywhere. We have a more consistent view. We do not have the same churn that we have with other operating systems. The longevity of Red Hat Enterprise Linux is pretty cool.

We see it being used a lot for containerization projects. A lot of the things that I am involved in involve Red Hat Enterprise Linux. It is a great experience. It is something that we know we can come into and have a good outcome. It is very reliable.

They are at the forefront in terms of built-in security features. I have seen a lot of things that they are doing. We would like to see more of that because security is something that is impacting everyone. 

The portability of applications and containers built on Red Hat Enterprise Linux is great for keeping our organization agile. It is consistent. When I build an image with Red Hat Enterprise Linux, I know what is in it. I know it is trusted. I do not have the same churn that I would have with others. The way they support it and the way they communicate are well-known.

It is the number one Linux operating system that we've run in to, and the way it does things is the way I prefer. I do not know if it is because they did it first, or they just read my mind.

The number one feature we like is that it is a very reliable platform. It is a very consistent platform. There is very little that we cannot do with Red Hat Enterprise Linux, and there is very little that we worry about when we are running a Red Hat distribution.

Red Hat started as a very open and outwardly focused release, but recently, some of the changes that were made have affected that reputation. From the standpoint of what they can add to the product, the product is pretty stable. 

They continue to push the ecosystem forward, but as a consumer, what was most important for me was the reputation of openness that Red Hat has fostered. I would like that back. I wish they did not care about CentOS and things like that. I have seen my customers push away from Red Hat as a result of that perception, which is weird because it does not change anything. I wish they would value that. Because of new owners too, the perception has changed suddenly.

I started with Red Hat before Enterprise Linux. I started in the nineties when Red Hat first went on floppy disks. They had a bunch of floppy disks. That was my first release, and then they started doing it via CD-ROMs. The first Red Hat Enterprise Linux release that I used was 2 or 2.1 in early 2000. I remember the Red Hat person coming to where I was working at the time and saying that they are going to start this enterprise distribution. We were really skeptical. We were like, "We have Red Hat. We love Red Hat. Why are you messing with a good thing?" It is kind of funny.

It is stable.

It is scalable.

It has always been solid. It is getting a little worse than it was before. When you get to the right people, you always get amazing support. It is just a bit harder to get to the right people. I would rate their support a ten out of ten. I love it when we get there.

Positive

It has been very long since I started working with these types of solutions. I have used them all.

We use it in the cloud. We use it on-prem. We use it in a hybrid situation. We use all cloud providers.

Its deployment has always been simple.

I am a consultant and integrator.

For us, our ROI is the predictability of Red Hat. We know what is coming. It is well-communicated. We could see the upstreams. We know how it is supported. We know how they communicate about CVEs and things like that. We know how to iterate the ecosystems. We know how to deal with RPMs. Very rarely, you are like, "This is brand new." It always usually works into a construct. There is always a utility that you can use to wrap complex things, such as SELinux or containers. There is always something.

We have done bake-offs before with the big three that everybody talks about. There is Red Hat. There is SUSE, and there is Ubuntu. Personally, I am not a fan of Ubuntu. I do not run a desktop, which is probably why. The ones that I run into all the time are SUSE or Red Hat Enterprise Linux.

If I were not going with Red Hat Enterprise Linux, I would go with a Red Hat Enterprise Linux clone. In business, I would always use Red Hat. Personally, I would use CentOS just because I prefer the way Red Hat organizes everything, so it has always been Red Hat or a Red Hat clone.

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

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.

We have an older environment with a lot of servers. They are development servers for a lot of in-house development. We have a lot of things. We have Ruby on Rails, Java, and a lot of Oracle applications

Red Hat Enterprise Linux is mostly on-prem in my current job. In my previous jobs, we have had it on AWS or Azure.

Red Hat Enterprise Linux's built-in security features are good when it comes to simplifying risk reduction and maintaining compliance. It is something that they do very well. It is one of the reasons why we like running it. It is rock solid in all areas. Red Hat does a really good job of keeping on top of vulnerabilities and making the patching process easy.

Red Hat Enterprise Linux has impacted our uptime and security. We have had no breaches, and our systems are usually up.

Red Hat Enterprise Linux has not yet enabled us to achieve security standards certification because that is not a requirement for where we are, but I am pretty confident that we would meet those standards. Our security teams are usually chasing problems on the other side of the house.

I like most of the features. I like its stability. I like its views. It provides a very stable environment. There is not a lot of downtime. There are not a lot of issues. Primarily, we are deploying things and configuring things, and occasionally, we add new things for developers as needed, but it does not require much troubleshooting or break fixing. That is rare.

The knowledge base offered by Red Hat Enterprise Linux is another thing I like about it. It is particularly easy to find an answer to your problem online. There is very good documentation, very good user communities, and good support when you need it.

The upgrade procedures are a little bit cumbersome. It would be nice if they are not because every three or four years we have to update, and I find that to be a bit on the cumbersome side. We have been able to automate most of it, but we still run into things where the job does not finish. There are things that require additional steps. There are things that need to be removed and that always require manual intervention. I do not know how they can get rid of that, but it is cumbersome in an environment where you have hundreds or thousands of servers.

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

I would rate their support a nine out of ten. I just do not give tens. I am sure there are some areas where they can improve, but they are good. They are responsive.

Positive

I have got experience with Windows and Solaris before that. Red Hat Enterprise Linux is my favorite. With Solaris, that stream stopped a long time ago, but Red Hat Enterprise Linux has all of the nice things about it, and they have continued to develop and build many new things. For instance, when you had to patch on a Solaris box, you had to take the server down into single-user mode and apply the patching. I like it better than Windows in every way. It is more intuitive to me. I like that I can do more things from the command line. It is easier to automate things.

I have been involved in the upgrades and some migrations for migrating things from Solaris. We also had CentOS, which was converted to DevStream, so we have had to change those to Red Hat. The upgrades and migrations were not terribly difficult. Usually, the tools were there. We called support when we ran into problems, but for the most part, it worked.

I have used Convert2RHEL. It was a bit helpful. It did the job.

We mostly use Ansible for deployment, patching, and managing the system in general. Our experience has been good. I am looking at some of the newer things they have at the conference that we have not had a chance to play with, but it meets our needs.

We have seen a return on our investment. We are able to do what we need to do without any problems or interruptions, and we are able to do it quickly.

For me, it is not too bad, but my company pays the bill, so I do not worry too much about it. 

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

We use the product to host operating systems, applications, or infrastructure for our customers. Our customers use the product as a long-term solution that they don't have to upgrade every other year. They can get people that know the solution from the get-go.

The biggest feature is the longevity of the distribution. Compared to any other product, Red Hat Enterprise Linux provides a stable backported solution for a long time. It is important because we have moved a lot of software containers. We want to update it but don't want to unless we have to. So it's great to have something stable for a long time.

The biggest thing that the solution could introduce is an even slimmer version of Red Hat Enterprise Linux. We are moving to containers, but we also have a lot of void loads that don't go into containers. It would be nice to have an even thinner operating system. Even if you choose minimally, you still get a lot of useless stuff you don't need.

I have been using the solution for 20 years.

I rate the product’s stability a nine out of ten.

I rate the solution’s scalability a seven out of ten.

It's really difficult to get to someone that knows something. When you get to the right people, support is really good. But there are a lot of people that can only answer first-level questions.

Neutral

We're using a lot of different OSs. We use Red Hat Enterprise Linux because we are a partner.

It's pretty simple to install the product. However, some tools required to install it are missing.

The pricing is great for virtual systems. The pricing for physical systems is way too high.

The overall costs depend on the project and the company.

We continuously evaluate other options. The main difference between Red Hat Enterprise Linux and other solutions is the complete ecosystem's longevity and possibility. Other products may present something similar, but they don't have the ecosystem around them.

We probably purchased the solution from a cloud provider. We are using versions 5 to 9 currently.

The solution’s built-in security features are pretty good, but it's not something that I would take as a major selling point. The portability is good because we have a stable baseline for applications and containers. Red Hat Enterprise Linux’s security posture is pretty good. I don’t know if it's the strongest selling point, but it's up there.

In some ways, Red Hat Enterprise Linux enables us to centralize development. However, that's not mostly what we focus on. The primary output from Red Hat Insights is targeted guidance. Targeted guidance has not affected our uptime much.

It makes sense to go with a stable distribution compared to others. Overall, I rate the product an eight out of ten.

As a whole, our organization is using it on Bare Metal on-prem and the private cloud, and then also in more than one public cloud environment. We probably have all three cloud providers. We definitely have Azure and Google Cloud. The environment that I support has about 40 apps in one cloud or another, but the organization as a whole definitely has hundreds of apps in Google Cloud or Azure. They're predominantly in Azure. The Google Cloud adoption is pretty recent compared to our Azure utilization.

I'm supporting a capital markets environment. A substantial portion of my environment is still Bare Metal at Colos. I'm sure on the application side, there's plenty of JBoss in our environment. There have been recent conversations around OpenShift on-prem that I'm working on, and our enterprise cloud teams are looking at or are using ARO in the cloud. In the next year, our use of the Ansible Platform will go from zero to full throttle as quickly as we can make that happen. We found the event-driven Ansible very interesting.

They've helped us work on employing technologies suitable to our various use cases. We're pretty slow adapters of containers, but that seems to be changing fairly quickly at the moment. That certainly gives us portability for workloads. They helped us with some aspects there, and they've helped us with a lot of automation conversation at the summit this week as well around Ansible.

When it comes to resilience in terms of disaster recovery, the operating system is robust. If it fails, it's probably an app issue. The majority of work in any of our DR scenarios is dependent on whether we have got cold standby or hot standby. If it's hot, the data replication is already there, and things are already spinning. Maybe it's on or you turn it on. Other times, you may have to start up something. Nearly all of those things are application architecture decisions as opposed to dependencies or things from an OS perspective, but in terms of the ecosystem for managing our Linux environment, using Satellite and so on has been very good.

I prefer it to Windows because of the level of configuration, level of control, and the ability to see the performance of processes on a given system. I prefer the control over logging and the ability that logging gives you to investigate a problem.

Its community is also valuable. It's open source, and Red Hat-supported streams are also valuable.

The level of communication we've got with them is fantastic. 

The integration with the apps and support could be better.

A colleague was talking about having some recommendations for the Ansible Cloud on the console and having some way of identifying your dev or prod path and whether you've got read or execute access to a playbook. There were different things like that, and they made a lot of sense, especially if you're in a dev or prod environment because mistakenly running something in prod would be a huge issue. There could be something that Red Hat configures, or there could be a text field where organizations can add labels to a part of the console to distinguish that for themselves. Those would be things that would be useful. I can't imagine it's hard to implement but being able to know which environment you're in matters a ton.

As a part of my professional career, I've been using it since 2004. I joined my current organization in 2018. It has been almost five years since I've been working with Red Hat Enterprise Linux in the security environment of our organization.

It's stable. We rarely have our systems crashing.

It's pretty easy and getting easier. It's not an OS issue. In terms of scalability, even while running our trading apps, we don't run into limitations related to the OS. Our limitations are more hardware-defined, and even then, we're running Red Hat Enterprise Linux on servers with eighty cores and almost a terabyte of RAM, and the OS doesn't have any issues.

Their knowledge base is great. There are lots of times when we don't even have to open a support case because we find what we're looking for.

I've spent a lot of time with the Red Hat account team over the past nine months. They've helped me understand products. They've helped develop the skills of my team. They've helped us with technology conversations with other parts of my organization. They've been hugely supportive of the technology conversation we're having with other parts of the bank.

They've been over and above the expectations in most cases. I'd rate them a ten out of ten. I don't know if it could be better. It has been extremely good. They've been extremely helpful in reaching out and figuring out what they can contribute. The account manager that they have working with us is a former colleague, so it's a really smart decision because we have a very good relationship with the guy. He knows our environment. It has been extremely positive.

It's a growing relationship with Red Hat. We have been using Red Hat Enterprise Linux for a very long time, and I don't know if we can even compare it to the other OS vendors, but having the account team working with us with that level of experience with our environment helps them work with us. It helps us accomplish what we're trying to do. It has been a very good partnership.

Positive

We get our licenses directly through Red Hat.

We haven't used the image builder tool or insights, but it's something that we might explore in the coming months. 

I'd rate it a ten out of ten. It's very customizable and very supportive. It never seems to crash. There could be better integration with apps, but from an OS perspective, it's excellent.