What Is The Relationship Between CentOS, RHEL, and Fedora?

Hello All,

Thanks a Lot to Nicky Helmkamp from InterWorx for contribution to All Linux User’s Blog.

This article submitted by Nicky Helmkamp using http://www.tejasbarot.com/submit-an-article/ . 

While there are a large number of RPM-based distributions available, three are more prominent than the others and are more likely to be considered for server operating systems: CentOS, Red Hat Enterprise Linux, and Fedora. Each of these operating systems is related to the others and they are in many ways similar, but the differences between them are worth understanding if you want to choose the most reliable and secure option for your web server.
We’re going to have a quick look at how each of these distributions came into being, what their intended use cases are, and whether they are a good choice for a server operating system.

Linux Logos
Linux Logos

Fedora

Fedora is a community-supported distribution owned by Red Hat, one of the most successful of the enterprise-focused open source software companies.
Fedora is important because it is the upstream distribution for both CentOS and Red Hat Enterprise Linux. However, Fedora is significantly different from both of its downstream offspring, because, while it is a fully functional operating system and certainly can be used as either a server or a desktop system, one of its major purposes is as a testbed for future versions of Red Hat Enterprise Linux.
For server operating systems, stability and predictability are important. Because Fedora includes cutting-edge largely untested software and because it has a very short development and support cycle, it tends to change significantly and frequently. Fedora usually has a new major update every 6 months and each release is supported for a maximum of 18 months. It is a great desktop operating system, because users get the newest software versions soon after they are released, but its volatility causes it to be less suitable for enterprise applications and servers. For those developing enterprise applications, Fedora’s constantly shifting APIs and short lifespan make it less than ideal.

Red Hat Enterprise Linux

RHEL is Red Hat’s official distribution, and all of the Red Hat support services, service level agreements, and certification programs are based on it. RHEL is intended to be an enterprise-grade, stable, and secure OS. It is much less subject to change than Fedora, with major versions having a normal support cycle length of 7 years with an option to extend that to 10 years.
Although Red Hat Enterprise Linux is open source, and all of the source code is made available by Red Hat, it is not free to use because the main reason a company would choose RHEL for their servers is because of the support services offered by Red Hat. As you might imagine, those support services are not free and cost anything from a few hundred dollars to many thousands of dollars.
If you are looking for a stable enterprise-grade server distribution with an excellent support package and service-level agreement, RHEL is an excellent choice, but if you have prefer to buy support from a different vendor or use in-house support, CentOS is the better option.

CentOS

CentOS is a binary compatible community-developed “clone” of RHEL. It’s basically Red Hat Enterprise Linux without the support services and branding and with some very minor configuration differences. CentOS is more or less a free drop-in replacement for RHEL.
CentOS also comes with the same long support lifecycles as RHEL, with the most recent version, CentOS 6, being supported up until the end of 2020.
CentOS does tend to lag a little behind RHEL with releases: for minor releases that may be hours or days and for major releases it can be several months, but for companies that think in terms of multiple year lifespans for their servers and software, the difference is trivial.
Which Should You Choose?
If you don’t care about long-term support and stability, Fedora is a perfectly fine option. If that is an issue and you also want to use Red Hat’s support services, then RHEL is your best bet. If you need an enterprise-grade platform that will be supported for many years without the cost of Red Hat’s support packages, then CentOS is the best option.

You can also submit your articles like Nicky Helmkamp.

All Linux User’s Blog Mobile Applications :- http://www.tejasbarot.com/download-mobile-apps/

Please Keep in Touch with Social Networking :- 

Facebook Page :- https://www.facebook.com/AllLinuxUsersBlog

Enjoy Linux 🙂 Enjoy Open Source 🙂

Install and Configure MRTG Graphs Linux / Network Graphs / Open Source

Hi All,

Article Submitted by Mr. Vishal Girish Joshi. I want to Thank him for his contribution for All Linux User’s Blog.

Ever wondered how you can easily graph your traffic load on network links through a simple grapher called MRTG.

Follow the below steps to configure mrtg to monitor your network usage and for misc troubleshooting in adverse times.

MRTG Graph
MRTG Graph

1) We just need a mrtg source / rpm file into our machine.

# yum install mrtg

2) Ensure snmp is enabled on the devices/servers we want to monitor

3) Create a directory of your wish in your www root folder (generally, /var/www/html)

In my scenario, i am monitoring my router/switches, so we need to enable snmp in that too. Also make sure that you have set the same community name (generally, `public`) on both sides.

After installing mrtg, we need to create configuration files using an in-built utility. So for that, go to your directory, created previously, and run the below commands.

# cfgmaker –global ’WorkDir: /var/www/html/Cisco-MRTG’ public@1.1.1.1 > mrtg.cfg ( You can give any name to the config file)

This will create the cfg file, have a look into it. this file will have the mrtg configuration pulled from the respective remote end (via snmp).

4) After this, we need to create the index files using the utility, indexmaker, this will display the output of mrtg.cfg file in the html format.

# indexmaker mrtg.cfg > index.html ( Be sure you are in your respective newly created directory )

5) Now, sometimes you can directly run the mrtg command to start the mrtg. But sometimes, it fails. So here is the workaround.

# env LANG=C /usr/bin/mrtg /var/www/html/Cisco-MRTG/mrtg.cfg (This will build up your first mrtg graphs and webpage)

If still errors, then run the above command for 2-3 times. Error will be gone automatically.

6) Also put the below code into your crontab

*/5 * * * * env LANG=C /usr/bin/mrtg /var/www/html/Cisco-MRTG/mrtg.cfg

7) Open the browser and type-in your url

For eg: 1.1.1.1/mrtg

If you are not able to access the url, go to /etc/httpd/conf.d/mrtg.conf. Here you can set different directives of apache, like,
Alias, Location, Authentication, etc according to your needs.

I generally prefer as setting Alias directive as ` Alias /mrtg /var/www/html/Cisco-MRTG ` and then allow the ip addresses you want to allow to view the mrtg graphs. You can also set the authentication parameters as per your requirement over htaccess, ldap, etc.

Hope this guide successfully helps you to set up mrtg for your organization.

Have a nice day and enjoy Linux.

Thanks to Mr. Vishal Joshi for the article.

You can also Submit Article by Visiting http://www.tejasbarot.com/submit-an-article/

Hope this will helps you all, If you face any issue regarding the same or its not working for you some how then please raise your questions / issues then comment down below.

If you like this then Please Click Google +1 Button and Show Your Support. Your Support will encourage me to write more articles.

All Linux User’s Blog Mobile Applications :- http://www.tejasbarot.com/download-mobile-apps/

Please Keep in Touch with Social Networking :- 

Facebook Page :- https://www.facebook.com/AllLinuxUsersBlog

Enjoy MRTG :) Enjoy Network Graphing 🙂 Enjoy Linux :) Enjoy Open Source :)