Rocky Linux Reviews

We work with a diverse set of tools and systems. We often need to experiment with various products and utilize standard development tools like compilers and debuggers to streamline our workflow.

We make extensive use of Rocky Linux for system configuration. It helps us keep our workstations in sync and ensures consistent settings across most of our machines.

We have a lot of PostgreSQL databases in our development work within our organization. Many of the tools and packages we need for this are readily available and easy to install and configure. The flexibility and availability of software packages make our workflow faster and more adaptable. It provides extensive community support and makes seeking recommendations, assistance, and access to software and settings easy. This supportive community aspect significantly simplifies our work in various environments, and it's something we greatly appreciate as developers.

Rocky Linux, being relatively new, initially lacked some of the software we were accustomed to from CentOS 7. There were some missing components and changes that required adjustment which is typical when transitioning between major releases in any distribution. Since it offers open-source documentation, there may be minor challenges in finding information. One of the potential issues is that if you don't pay for support, you may need to manage certain aspects on your own and rely on the community for assistance.

The operating system has proven to be stable and reliable in our experience.

We haven't encountered any major problems with the operating system itself. Our primary challenges typically revolve around software-related issues, especially when it comes to third-party software or our in-house applications.

Our decision to use CentOS, and now its successor, Rocky Linux, was rooted in the desire to stay close to the Red Hat ecosystem. We have continued this approach by selecting distributions that are as similar as possible to RHEL. The aim is to ensure that our development and testing process aligns with the standards of the industry and our customer base. We want to maintain a consistent and reliable development environment, which is why we choose distributions like Rocky Linux or AlmaLinux.

The implementation process is relatively straightforward. We typically start by cloning the repository, which contains various configurations and packages. Since we have a considerable number of workstations, specifically around eighty, we find this cloning approach to be efficient. Once the repository is cloned, the system can be set up to automatically perform updates and package installations.

When we need to set up a new workstation, we utilize a kickstart configuration which contains essential information about the workstation, such as its IP address and other specifications. After a new workstation is added, the kickstart process efficiently sets up the machine according to the specified parameters. The key is having a well-organized system for repository access and automation, which ensures a smooth and efficient workflow when working with Rocky Linux.

When evaluating a replacement for CentOS 7, we initially had to consider certain specialized requirements before making a decision. Regarding the choice between AlmaLinux and Rocky Linux, both options were strong contenders due to their close alignment with the CentOS path, which we were transitioning from. We conducted testing and analysis on both AlmaLinux and Rocky Linux. Initially, it was challenging to determine which one to choose, but we opted for the distribution that appeared to have a more significant user base and community support. This decision is often crucial, especially in open-source environments, as a larger user community can provide valuable assistance with development, information sharing, and problem-solving.

There is a wealth of valuable information available online when it comes to using Rocky Linux. It provides clear guidance on the initial setup steps to get your system up and running for experimentation. Once the system is up and running, you'll notice that, as a user, the experience is quite similar to using other Linux distributions like CentOS or RHEL. The primary differences tend to surface when it comes to system management and administration, where you may notice distinctions between Rocky Linux and other distributions. However, with the available resources and documentation, navigating these differences becomes manageable. I would rate it eight out of ten.

We tested Rocky Linux as a replacement for CentOS. It was a drop-in replacement that worked as advertised out of the box. However, we decided to go with another solution. We felt Alma Linux was a better fit for us than Rocky Linux. 

We decided not to use Rocky Linux, and therefore, it has had no impact on our organization. 

Rocky Linux does function as a drop-in replacement for CentOS, which is a valuable feature, but we felt there were better options out there. 

In terms of improvement, Rocky Linux needs to clarify its identity and target audience. While it is technically sound as a CentOS replacement, there is a disconnect in its marketing messaging, which initially positioned it as an HPC platform. It should define its core identity and audience more clearly.

We tested Rocky Linux for a window of about three months. 

I haven't needed to use customer service or support, which speaks volumes about their product's reliability and ease of use.

It is a straightforward setup, serving as a direct replacement for Red Hat Enterprise Linux or CentOS. Rocky Linux requires standard maintenance similar to any other Linux distribution, without any unusually heavy demands.

Overall, I would rate Rocky Linux as a seven out of ten.