Linux Notes: Enterprise Linux (EL)
- The information presented here is intended for educational use by qualified computer technologists.
- The information presented here is provided free of charge, as-is, with no warranty of any kind.
Edit: 2024-10-19
What is Enterprise Linux? (EL)
Let's ask Microsoft Copilot
Question: What is the difference between Enterprise Linux and so-called traditional Linux?
Answer:
Certainly! Let’s explore the differences between Enterprise
Linux and traditional
Linux distributions:
-
Enterprise
Linux:
- Developed by open-source companies such as Red Hat and SUSE.
- Targeted for commercial markets, including businesses and academia.
- Often available through subscription plans, although some distributions (like CentOS)
are free.
- Offers various editions for server, desktop, workstation, and management platforms.
- Has a slower release cycle (typically 24-36 months) to maintain stable releases.
- Provides technical support.
- Notable enterprise Linux distributions include Red Hat Enterprise Linux, SUSE
Linux Enterprise, Oracle Linux, and CentOS.
-
Traditional
(Home/Personal) Linux:
In
summary, Enterprise Linux focuses on stability, support, and commercial use, while traditional Linux distributions cater to
individual users and offer more frequent updates. 😊🐧
Let's ask ChatGPT
Question: Explain how Enterprise Linux is different from so-called common Linux
Answer:
Enterprise Linux and common Linux distributions differ primarily in their target audience, support models, release cycles, and package management systems.
Target Audience:
- Enterprise Linux: It's designed for business environments, emphasizing stability, reliability, and long-term support. Enterprises typically prioritize predictability and supportability over having the latest features.
- Common Linux: These distributions cater to a broader audience, including hobbyists, developers, and enthusiasts. They often prioritize bleeding-edge features and community-driven development.
Support Models:
- Enterprise Linux: Typically comes with commercial support options provided by the distribution vendor. This includes assistance with installation, configuration, troubleshooting, and security updates. Support contracts often offer long-term support (e.g., 5-10 years) for each release.
- Common Linux: Support is primarily community-driven, although some common distributions do offer paid support options. Community support can be excellent, but it may not offer the same level of responsiveness or accountability as commercial support.
Release Cycles:
- Enterprise Linux: Follows a slower, more conservative release cycle. Major updates are released at longer intervals, often every few years. This stability is crucial for enterprise environments, where frequent changes can disrupt operations.
- Common Linux: Tends to have more frequent releases, with updates pushed out as soon as new features are ready. This rapid pace allows users to access the latest technologies but can also introduce instability or compatibility issues.
Package Management:
- Enterprise Linux: Typically uses a package management system tailored for stability and security, such as RPM (Red Hat Package Manager) or DEB (used by Debian and Ubuntu). These systems focus on ensuring dependencies are met and updates are applied smoothly without breaking existing configurations.
- Common Linux: While many common distributions also use RPM or DEB, there's often more flexibility in terms of package sources and installation methods. Common Linux distributions may be more open to using bleeding-edge or third-party repositories, which can increase the risk of compatibility issues.
Certifications and Standards:
- Enterprise Linux: Often adheres to various certifications and standards required by industries such as finance, healthcare, and government. Compliance with these standards ensures that enterprise deployments meet regulatory requirements and security best practices.
- Common Linux: While common distributions may also adhere to standards and certifications, the focus is often more on general-purpose computing rather than specific industry requirements.
In summary, Enterprise Linux is tailored for stability, security, and long-term support in professional environments, while
common Linux distributions offer more flexibility and cater to a broader range of users, including hobbyists and enthusiasts.
A few additional details (from me)
- Many times, Enterprise Linux is referred to by the letters EL
- Here is an incomplete list of Enterprise Linux distros: AlmaLinux, CentOS, EuroLinux, Fedora Linux, Oracle Linux, RHEL
(Red Hat Enterprise Linux), Rocky Linux
- Rather than providing you with upgraded new applications, an Enterprise Linux distro will almost always provide
you with the original version number except for this: bug fixes and security problems have been backported.
- Why do it this way?
- Many times, upgrading a program (like the firewalld or httpd to name only two of many) will result in the new app not
starting because it encountered an unsupported, or modified, directive in the associated configuration file.
- Upgrades to database engines like MySQL or MariaDB almost always require the database admin to dump the database before
the upgrade, then import the data after the upgrade. Allowing admins to thoughtlessly update the engine without the
dump-restore ritual almost always leads to some sort of glitch or failure.
- Minor version upgrades to Python3 (eg. Python3.6 to Python3.8) always require the admin staff to install optional packages
via: python3.x -m pip (where 'x' is the minor version number). In this area it is safer to install multiple python
versions then transfer your python apps gracefully.
- Thoughtless upgrades to either ssh or OpenSSL might cause your server to not be able to connect to older servers in your
organization (these are almost always unpatched Windows Servers). For example, my EL7 and EL8 systems are able to connect to
older non-Linux systems run by my employer, while EL9 is causing me some problems.
Comparing three instances of httpd (2024-04-30)
Notes:
- httpd is the Apache server
- EL7 means any Enterprise Linux instance with a major version of 7. Same with EL8 and EL9
- Many Linux installations will also include links to optional distributions. Here are two popular ones:
- epel-release (extra packages for enterprise linux) - more popular
- elrepo-release (enterprise linux repository) - less popular
<<< EL7 (CentOS-7 in this case) >>>
[neil@kawc4n ~]$ yum list installed httpd.x86_64
Installed Packages
httpd.x86_64 2.4.6-99.el7.centos.1 @updates
Notes: patched 99 times -----++
========================================================================
<<< EL8 (AlmaLinux-8 in this case) >>>
[neil@bfdc0d ~]$ yum list installed httpd.x86_64
Installed Packages
httpd.x86_64 2.4.37-62.module_el8.9.0+3646+acd210d0 @appstream
Notes: patched 62 times ------++
========================================================================
<<< EL9 (AlmaLinux-9 in this case) >>>
[neil@kawc3v ~]$ yum list installed httpd.x86_64
Installed Packages
httpd.x86_64 2.4.57-5.el9 @appstream
Notes: patched 5 times -------+
========================================================================
Do not jump to EL9 too soon
- In January of 2024 we were looking at our six EL7 systems (CentOS-7.9 with an EOL of 2024-06-30) and wondering if we should
migrate them to EL8 or EL9
- So I did a backup/restore of one EL7 system then migrated it to EL8. Then did a backup restore of this system then migrated it
to EL9. Then I did a lot of testing.
- Now I need top point out that I'm working behind a firewall, and that all my Linux systems need to be able to communicate
(SSH/SFTP) with older corporate systems (HP-UX, Solaris, z/OS, OpenVMS, etc.) which all under control of other departments.
- EL8 could communicate with everything but EL9 could not. In fact, EL9 cannot even communicate with EL6
note: RHEL-9 cannot communicate with RHEL-6 (and this is by design)
- I have read some really good RedHat technical articles describing that this problem can be fixed by forcing your EL-9 into
LEGACY mode, but also warn that this is a really bad idea. So you should only use this LEGACY feature temporarily if you are
trying to get access to files from an old system.
Links
Back to
Home
Neil Rieck
Waterloo, Ontario, Canada.