One of our use cases is for our in-house applications that the development team builds. We also use it for typical tasks like running Jenkins, GitLab, and other development tools to make them accessible for the developers who write code and do software development.

One of Red Hat Enterprise Linux’s valuable features is its enterprise-level security. We are guaranteed that it's secure, and that's important for us because we need to comply with security regulations. Security always remains a top priority.

We just run Red Hat Enterprise Linux’s built-in security features day in and day out. We know it's secure, and then we just move on to other tasks. It's like a routine where we don't have to think too much because we know it's already integrated into the whole enterprise. It's the next step, and it gives us more time to focus on other tasks.

We are trying to figure out how to enable encryption or just encryption. The last thing we want is to use locks, which are a hassle for encryption. We don't have the personnel to unlock the system every time it gets rebooted. I know there's a way, like on Windows, where they have TPM. I'm not sure how Red Hat Enterprise Linux’s TPM works. That's one of the issues we face—how to utilize TPM effectively.

I think in the future, if the company requires us to encrypt everything, it would be a time-consuming process. I'm not sure how long that would take or if it will happen. I just want to understand how Red Hat Enterprise Linux and TPM work or if there's an existing solution that works similarly where I don't necessarily have to be present every time my system reboots and enter a password. At least for Windows, we know that it works, but I'm not familiar with the equivalent functionality in Red Hat Enterprise Linux.

In future releases, I would prefer a Red Hat Enterprise Linux image that fits on a DVD. The Red Hat Enterprise Linux image keeps getting larger and larger. One of the biggest requirements for my company is that it has to fit on a DVD. Now, with Red Hat Enterprise Linux 9 approaching close to ten gigabytes, it won't fit on a DVD anymore. The last thing we want to resort to is using Blu-ray. I prefer not to use Blu-ray. So we need to keep the image size on a DVD smaller. That's one of the main issues. And we can't use USB sticks either, even though they're a new option. Everything needs to be burned on a DVD. So having a Red Hat Enterprise Linux image that fits on a DVD would be beneficial for any future versions or releases.

I have been using this solution for eight years now. Right now, we're migrating. I'm trying to upgrade from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7. And that process is painstaking. It's taking a lot of time. I know we want to get that done before October because I think that's when the security support for Red Hat Enterprise Linux 6 expires. We need to move everything to Red Hat Enterprise Linux 7.

We have a lot of legacy systems, and it's very time-consuming trying to figure out what will work and which version of Red Hat Enterprise Linux will support all our applications. So it's just a lengthy process to go through.

In terms of stability, there have been some issues, particularly on the workstation side. The workstation tends to freeze up occasionally, requiring a system restart. The server side, on the other hand, works well as intended. Although Red Hat Enterprise Linux is primarily designed for servers, our developers use it as a workstation, and that can sometimes cause issues after a couple of days of continuous use.

They may need to restart their systems when something freezes or stops working. So it's one of those things we encounter.

I don't really use it extensively. I have some knowledge and experience with it, but I don't heavily rely on Red Hat support. Whenever I encounter a problem, I usually turn to Google for solutions.

The knowledge base provided by Red Hat exists, but I find it difficult to navigate. The information seems scattered and hard to find. I tend to prefer searching on Google since I can get immediate answers there compared to the knowledge base, which can be challenging to navigate. It seems like the knowledge base could use some improvement.

One of the main advantages is the level of support. Red Hat Enterprise Linux provides nearly ten years of support, including two years of extended support, whereas other operating systems typically have one or two major versions released within five years. It can be challenging to allocate the budget for frequent updates over such a short period. So I think that's the main appeal of Red Hat Enterprise Linux—its ten-year support with an additional two years.

Since I've been working with Red Hat Enterprise Linux for a long time, it feels easy for me. However, for someone completely new to it, especially coming from a Windows background, it might seem more complicated. But for me, it's second nature and not that difficult. So the initial setup depends on the level of familiarity with the system.

For a brand-new system, it might take around ten minutes.

I have worked with CentOS, Fedora, and Ubuntu. So I have experience with different flavors of Linux, from the Ubuntu side to Fedora. From a developer's point of view, the main difference, if I compare it to Ubuntu, is that they always get the latest packages, which helps them a lot. 

On the other hand, with Red Hat Enterprise Linux, I understand that it's set up to prioritize security. But sometimes, from a development perspective, it's challenging for them to obtain the latest packages. As an assessment, I have to go out there, fetch the package or compile the new package for the new version, and then bring it into Red Hat Enterprise Linux so that developers can use it. I think that's the issue. It's a balancing act between trying to get the latest package versions and ensuring stability and security. It's a problem that I think everyone struggles with.

Overall, I would rate the solution an eight out of ten because there is always room for improvement when it comes to technology.

I use the solution to develop OS for our internal use. I deliver it to our internal clients, so they can use it for whatever applications they may need to use it for.

The product is very stable. The knowledge base is excellent.

The solution should improve its documentation.

I have been using the solution for 16 years.

The solution scales well.

The support is good. I would rate support an eight or nine out of ten. The documentation should be improved to make it a ten.

Positive

The deployment is very easy for me because my organization has been doing it for a long time.

The product’s resiliency is pretty good. It responds fast to security updates compared to some other closed-source vendors. 

We moved from other priority operating systems to Red Hat Enterprise Linux because it saves us costs on the commodity hardware. Overall, I rate the solution an eight or nine out of ten.

We use Red Hat Ansible Automation Platform. We are using version 8.4, but we started with 8.3.

The solution’s stability is its most valuable feature. It has only been two years since I first started using the product. So far, I have seen a subtle comparison of the solution’s stability to other operating systems.

It is challenging to use the knowledge base and the deployment documentation. Some of it is all over the place, and it's challenging to piece them together.

It has been two years since we put in the first footprint of Red Hat Enterprise Linux in our organization.

We have about 30 to 40 servers.

The support team is pretty good. Whenever I send support requests and ask questions, the team is knowledgeable enough to get me the necessary answers. Sometimes there are delays in the response. However, it has been a positive experience for me.

Positive

I was the main engineer during the initial deployment of the product. The initial setup was straightforward. Whatever was in the documentation was exactly what was meant to be done.

We did not struggle with the documentation because I have been an engineer for years. Someone who is just getting started might have a different perspective on the ease of setup.

We purchased the solution from a third-party vendor.

I use Ansible Builder to build my containers. However, I do not use Red Hat Enterprise Linux’s image builder tool.

We do not use Red Hat Insights yet, but we're planning to use it in the near future. As soon as we get more servers in our environment, our firm’s directors might decide to start using Red Hat Insights. Right now, we are just using Automation Analytics. The solution’s resiliency is pretty solid.

We implemented the solution because we wanted automation. We cannot install Ansible Automation Platform in operating systems other than Red Hat Enterprise Linux.

Overall, I rate the product an eight out of ten.

Primarily, we use it for a couple of different servers. Some are doing data hosting, and some are doing network management-type functions.

We use it on-premises. We do not use it on the cloud. Because of government work, we're not cloud-based.

By implementing Red Hat Enterprise Linux, we were mainly looking for stability. By having a lot of open source solutions, we ran into problems where there were too many flavors and too many variables. We ran into issues with ISO and other things where this particular site was a one-off from this site, which was a one-off from this site, which was one-off from this site. That became a problem for making sure that we stick to a consistent level and patch to a consistent level across the board.

The portability of applications and containers built on Red Hat Enterprise Linux has been good. We do a lot of containerization and a lot of microservices. It has worked really well. It helped in keeping our organization agile. Our partners provided us with a lot of quick utilities and reuse of things. We can shut down a container and spin up a new container to introduce new capability quicker. 

The biggest feature that I have found valuable is stability. 

The way it lent itself to automation has been very invaluable for us. It makes the setups a lot more consistent and repeatable across the board. We're able to deploy the product quickly in a very consistent manner, which meets our timelines. A lot of what we do has very short spending dates, and they need a lot of product work.

It has been pretty good for us. I have no complaints as such. We just learned that we can get access to more support documents by going through the portal. I didn't know that. If it was something that was more known or advertised, that would have helped us to find out some of the information a little better.

I have been using Red Hat Enterprise Linux for about a couple of years.

It's a 10 out of 10 in terms of stability.

It's a 10 out of 10 in terms of scalability.

The customer service is good. There is a lot of support documentation out there for anything you're looking for.

Positive

We tried quite a few flavors of different things, but nothing provided the consistency that we are getting with Red Hat Enterprise Linux. We tried everything such as Ubuntu, Mint, etc.

Red Hat Enterprise Linux stood out for its consistency and stability. We had several different problems with drivers on Mint. There were so many different flavors. We had one developer who built everything on one, and then another developer built on another, and none of that was coming together. It was not meshing, so we finally went to a common platform with stability and supportability. It was a lot better. It has allowed the developers to focus more on their code rather than having to worry about fighting the underlying things, such as drivers aren't on this one, and that one is not working.

It was very straightforward. We've pushed in further to make our own ISOs, so we're making sure that everything is getting the same applications and everything is deployed across the board, and we are able to virtualize in some cases. It has been good.

You definitely get what you're paying for. From what we've seen, it has been great. It has also allowed virtualization and making their own ISOs. We're able to package all that up, and it has worked consistently and repeatability. We've written our own Bash scripts so that we can automatically deploy that and stick it as part of the build. We're saving a lot of time and getting to a common platform repeatedly.

Overall, I'd rate it a nine out of 10. There's always room for a little bit of improvement.

I am an administrator for Red Hat Enterprise Linux. We use Red Hat Enterprise Linux in a hybrid environment running off of on-prem servers and also AWS. 

I use Red Hat Enterprise Linux for a variety of purposes. For example, we use it in cloud control systems at our factories. We also use it for test systems, data acquisition, databases, and web services.

The biggest problem we were trying to solve by implementing Red Hat Enterprise Linux was scalability. I have found that since implementing Red Hat Enterprise Linux, we get a lot more value for our money from our hardware. Red Hat Enterprise Linux has also increased our utilization of Windows as a solution.

I am not the one who moves workflows between the cloud and our data center using Red Hat Enterprise Linux. However, we have tested it and I believe it is seamless. It just works. This is one of our disaster recovery methods. We will have images, and we use Veeam for this. Veeam actually takes the image we have and moves it to the cloud. We then fired it up and did not have any problems.

The most valuable feature is the reliability of Red Hat's support.

Red Hat Enterprise Linux analytics are cryptic. While it is user-friendly, it is also very picky about who it takes for a user. It is rock solid, but it can be difficult to find things in there. Google is probably the best way to find information, but solving a problem can be difficult if we don't know what flags or permissions we need. We need more transparency or ease of use.

I have been using Red Hat Enterprise Linux for almost twelve years. 

Red Hat Enterprise Linux is scalable.

I can always get a hold of someone when I call, and they always resolve my issue. I only have to call them once or twice a year, because things just work.

Positive

I have used Fedora and Oracle Linux. I have some systems that run CentOS. 

Our organization requires us to use different solutions. We have had instances where products were developed on Oracle Linux. These products are medical, and switching to a different platform is not a simple task. I am encouraging the organization to switch everything to Red Hat Enterprise Linux because, although Oracle Linux is a fine platform, it is eight months behind Red Hat Enterprise Linux.

The main benefit of CentOS is its cost. Both systems are reliable, but Red Hat Enterprise Linux has a major advantage: Red Hat support. With Red Hat support, we have access to top-level Linux experts. If we need help with anything related to Linux, we can call Red Hat and they will connect us with an expert who can help us.

The first time I deployed Red Hat Enterprise Linux, I was swapping floppies. It has gotten a lot easier since then. The deployment process is straightforward. I usually map an ISO, and then check a bunch of boxes and let it run. I can have a server up and running in about fifteen minutes. After validating the system and installing the necessary software, I can deliver it to the end user in an hour. I know that if I automate the process, I could probably reduce the time to six minutes.

I give Red Hat Enterprise Linux a nine out of ten because there is always room to grow.

Someone looking at an open source, cloud-based Linux OS instead of Red Hat Enterprise Linux should consider what is being used in their customer base. If they are putting something up there as a proof of concept, then dabbling in open source is fine. However, if they have customers relying on them and they want minimal downtime, then they need Red Hat Enterprise Linux.

The knowledge base can be a bit cryptic at times. We can go in there and read the same information that's in the documentation, but sometimes it's not clear enough. So I'll often go to a half dozen other websites that tend to give us examples and other helpful information. The knowledge base is a good place to start, but it's not the end-all-be-all.

I use Red Hat Enterprise Linux for web application support, mainly OpenShift.

Azure is the cloud provider.

Red Hat Enterprise Linux is easier to manage because it can scale to a large amount and be managed across many platforms. This can lead to cost savings for our organization.

Red Hat Enterprise Linux has reduced the amount of management required on the Windows side.

Red Hat Enterprise Linux is extremely resilient because it is much more secure.

Red Hat Enterprise Linux's day-to-day functionality is very easy.

Red Hat Enterprise Linux has helped our organization save money by not requiring large-scale virtual machines, resources, or images.

OpenShift is the most valuable feature because it can be used to create applications on the fly.

The UI is not user-friendly and has room for improvement.

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

I am impressed with how extremely stable Red Hat Enterprise Linux is.

Red Hat Enterprise Linux's scalability is excellent.

Technical support is quick to respond, but sometimes tickets can get stuck in tier one for a while before they are escalated.

Positive

We previously used Windows but switched to Red Hat Enterprise Linux for cost savings.

The initial setup is straightforward. We can copy and paste any templates we need into the environment.

We have seen a return on our investment simply from receiving timely support when needed.

We purchased the Red Hat Enterprise Linux license via Azure and the vendor.

We evaluated CentOS but ultimately chose Red Hat Enterprise Linux because of the support.

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

When evaluating operating system options, keep in mind that Red Hat offers the best support.

We run various application servers. We have application servers for Java and Python. We also run Postgres and different applications. We have Kubernetes, Docker, Docker Swarm, etc. We have a wide variety. 

We weren't trying to solve a particular problem by implementing Red Hat Enterprise Linux. We've used Red Hat Enterprise Linux for so long. We used to modify the Kernel in the early versions of Red Hat, but that's not needed anymore. We are currently using versions 7, 8, and 9. 

Red Hat Enterprise Linux has enabled us to centralize development in our hybrid cloud environment because the containers can be migrated from Red Hat Enterprise Linux to AWS. It's not an issue. There is also a Red Hat-supported programming tool called Skupper, which is a layer seven service. It's an open source product. It's supported by Red Hat, so we could use that to migrate our containers back and forth on the cloud and on-prem, which is very much needed.

Red Hat is pretty good at containing risks. We have a firewall, but we also use iptables and SELinux. SELinux has proved to be very valuable. We have certain tools where when somebody tries to break SELinux, we immediately get alerts.

We don't have a problem with compliance. We also use Red Hat Satellite. Our Red Hat Satellite server is helpful in terms of meeting compliance requirements.

We're able to modify and migrate containers and redeploy containers very easily. We do that on the Red Hat platform. We do it with other tools such as VMware. Red Hat API works very well with other vendors, so that's definitely a plus. In terms of changes, for instance, if we want to connect to ServiceNow to create a ticket in Ansible, we're able to do that without any problems whatsoever. We can create a ticket in ServiceNow. We can remediate it, and we can close the ticket on ServiceNow from Ansible. Ansible is a big part of Red Hat.

It's a rock-solid operating system. We don't need anything fancy from the operating system itself. What we need is something that doesn't crash, stays up to date, and provides the security features that we need to keep external players out.

The CVEs that come out for the vulnerabilities are very fast. We try to do patching in different tiers. Our regular patching happens once every ninety days, and then we have special iterations that need to be done, and those are on demand, or if there's a high-security risk and it's absolutely immediate.

The other thing that we like about Red Hat is the support for open source. That for us is a slam dunk.

They should work more on container documentation. The only issue that we have is that Red Hat specifically promotes OpenStack, and we don't use OpenStack. It's good if you're using OpenStack, but if you're not using OpenStack, and you're using Docker or something else, it isn't that good. Having more support for non-OpenStack would be very helpful, but, of course, as part of their business, we don't expect it.

I've been working with Red Hat Enterprise Linux for many years.

It's very stable.

It scales very well. We have about a thousand servers, but we could scale to five thousand servers without a problem.

Their support is good overall. It's better than some of the other vendors. The staff is very friendly. The people I've met hear and discuss issues. We're very much interested in open source, so we use a lot of open source. The engineers have been extremely helpful. 

I'd rate them an eight out of ten. I'm not giving them a ten. Some of it has to do with the time cycle, and some of it has to do with different levels of quality with the support. You could get a junior support person, and obviously, that's going to be a very different experience.

The knowledge base offered by Red Hat is very good.

Positive

Our environment is hybrid. Most of our Red Hat Enterprise Linux is on-prem. For the cloud, AWS is the cloud provider, but we are using a different distro for AWS. We use AWS Linux for that. For on-prem servers, we're strictly using Red Hat Enterprise Linux. For desktops, we use Fedora.

The reason for using AWS Linux is that we only have AWS. If we use multi-cloud, for instance, if we use Azure and AWS clouds together, we would definitely need something other than AWS Linux. AWS Linux is very solid too, and our team likes it. We can download the AWS Linux version for on-premises too. I've done that. I tested it, but we're sticking with Red Hat Enterprise Linux.

In the server space, nothing comes close to Red Hat Enterprise Linux. I know that Ubuntu is making a big push, and some people have gone ahead and migrated to Ubuntu, but I think those are going to migrate back. There's just no comparability. They're different. They're like cousins. They're very similar in some ways, but they're very different things. You can install SELinux on Ubuntu, but why bother and why go through the whole configuration? Red Hat Enterprise Linux is more suitable for servers.

We use certain tools from HashiCorp, such as Packer, so deploying it is very simple. We have a script that runs every night, and it creates via the CI, goes up to GitLab, gets whatever it needs, such as parameters, and sends it to Packer. Packer grabs the ISO, and it creates a very specific, customized deployment. It's done with a couple of right clicks. That's it.

We've absolutely seen an ROI. It's in terms of reliability, stability, security, and usability. You name it. The use cases are out there.

The licensing structure is very convoluted. It's very confusing. We have a Satellite server, and we license it through the Satellite server, but if we didn't, we'd have to buy individual Red Hat licenses. That would be a nightmare to maintain in terms of renewing it every year and things like that. 

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

We use the product for application hosting, availability, and CI/CD pipelines.

The solution has good availability and is easy to use. It saves money and resources like support staff.

The product should provide a portal to manage licenses.

I have been using the solution for more than five years.

The solution’s stability is fine.

The product’s scalability is fine.

The support is good.

Neutral

We have seen an ROI on maintenance. As long as our servers run, our company makes money.

We evaluated SLES and Windows.

We purchased the solution via a cloud provider. We use AWS, Google, and Azure. The resiliency of the product is the same as other products. 

The solution helped us reduce costs. We use SLES and Windows alongside Red Hat Enterprise Linux. Application support and vendor support for Red Hat Enterprise Linux are better than other products. 

Overall, I rate the product an eight out of ten.

I use the solution to build web applications.

The tool provides more support, resources, and documentation than other products.

The product is super easy to use.

The default settings are confusing. I often change these settings to avoid problems.

I have been using the solution for a couple of years.

The stability of the product is very good.

I did not have issues finding configurations and changing settings as needed. I haven't had any issues like bugs or downtime while using Red Hat Enterprise Linux. Overall, it was a good experience. Overall, I rate the solution an eight out of ten.

I work in the financial industry in Brazil and my first job was to use Linux.

We deploy Red Hat Enterprise Linux on-prem and in the cloud. Our cloud provider is AWS. 

We use Red Hat Enterprise Linux for web applications, including the JBoss data bridge. We also have some applications for prevention and risk. Red Hat Enterprise Linux is used for most of our applications in Brazil, so it is used for almost everything.

We run our workloads and applications on AWS.

There are many Linux-based operating systems. We wanted an operating system that was mature and reliable, and Red Hat Enterprise Linux was the best choice for us.

Red Hat Enterprise Linux is a highly resilient operating system. It has a strong XFS file system, kernel, and package build.

Migrating workloads between the cloud and our data center is easy. There are no problems.

The knowledge base offered by Red Hat Enterprise Linux helps a lot. It is very useful and has helped me to resolve the issue by looking at the documentation.

The integrity of our operational systems is very stable. Red Hat Enterprise Linux has a good file system type and good kernels. It does not crash for any reason. This makes it a very stable platform for me. It is the best solution for our needs.

There was a reduction in the amount of detail provided in backlog messages between Red Hat Enterprise Linux versions six and seven, compared to versions eight and nine. This makes it more difficult to troubleshoot errors in versions eight and nine, as users must dig deeper into the operating system to find the source of the problem. Versions six and seven provided more detailed error messages, which made it easier to identify and fix problems. Deploying applications using Red Hat Enterprise Linux versions six and seven was seamless. However, there is a chance that something could be broken when deploying with versions eight and nine, and we may not know it.

I have been using Red Hat Enterprise Linux since versions four and five.

Red Hat Enterprise Linux is extremely stable.

One of the reasons we adopted the Red Hat Enterprise Linux ecosystem is because of its ability to scale.

I have not had a good experience with Red Hat engineers. When we have an issue, it is very difficult to have it resolved in the first call. They always have to escalate the issue and involve multiple people. At a minimum, we have to escalate an issue three or four times before it is resolved. The support team in Brazil has helped me a lot because they work with me to resolve the problem, but if I have to open a ticket and follow the steps I never get proper service.

I give the technical support of Red Hat a zero out of ten.

Negative

The initial deployment is easy. I can deploy Red Hat Enterprise Linux myself using a base image within a few minutes both on-prem and in the cloud.

The implementation is completed in-house.

We purchased our license from Red Hat.

I give Red Hat Enterprise Linux an eight out of ten.

Cloud vendor lock-in is inevitable when we adopt the cloud. This is because once we adopt a cloud service, such as DynamoDB or AWS, we become dependent on that provider for support and maintenance. It is very difficult to work with multiple clouds 100 percent of the time, as this can lead to problems with failover and other issues in multiple cloud environments because the risk is high.

The Red Hat Enterprise Linux ecosystem is more attractive because we are not just buying an operating system. We are buying an ecosystem that helps, supports, and secures our platform. I believe this is the better option.

Applying patches in the new versions of Red Hat Enterprise Linux is more time-consuming than in Oracle Linux because Oracle Linux does not require legacy environments to be patched or changed through applications.

For someone looking for an open source cloud-based Linux OS instead of Red Hat Enterprise Linux, I recommend AWS Linux. It is a very stable version of Linux and does not require a subscription.