I learn that RHEL and Centos has the exact same source code. So my question here is if one application built for RHEL 6.4, could we just install and make it running on Centos 6.4 without any update?
And another question is RHEL and Centos will always use the same version number for the same source code, right?
Yes, software built on RHEL 6.4 should work as-is on CentOS 6.4 (assuming you don't depend on one of the relatively few RHEL-specific details, mostly to do with branding).
CentOS, except where necessary, uses upstream RHEL sources unmodified. When they need to modify a package they indicate that in the release notes and in the release field of the RPM in question.
Related
I have a quick question related to "Kubespray".
Does "Kubespray" support CentOS 8?
I wanted to deploy "Kubespray" on "CentOS" and I came to know that the CentOS 8 has Kernel version 4.18 and If I can use "CentOS 8" for "Kubernetes" deployment, maybe I can get rid of the "c-group" issue which we are currently facing for all the CentOS distribution which has Kernal Version less than 4.18.
Thanks in Advance.
According to the official documentation Kubesprawy provides support for CentOS/RHEL 7 only. The problem is that:
Installing Kubespray on a RHEL8 systems does not work since the
default Python version is 3.6 and thus python3-libselinux should be
installed instead of libselinux-python. Even that python2 is still
available, the libselinux-python package is not.
I hope it helps.
Running a Laravel installation on a RedHat Enterprise Linux 7 server using PHP 7.1. I can see php-pgsql.x86_64 listed in the available yum packages, but it doesn't appear to be compatible with PHP 7.1 (and indeed is listed as version 5.4.16-43.el7_4.1).
On a lark, I tried installing it anyway and physically moved the pgsql.ini and pdo_pgsql.ini files from /etc/php.d into the relevant PHP 7.1 folder /etc/opt/rh/rh-php71/php.d/ (and did the same with the .so files they reference), but that returns an error indicating that the package couldn't be read (undefined symbol: file_globals_id in Unknown on line 0).
Has anyone managed to get PHP 7.1 talking to PostgreSQL on RHEL 7?
The sysadmin who originally created the server for me set me straight. The problem was I was looking in the wrong repository for the packages I needed for my particular PHP installation. Running the following two commands did the trick:
sudo yum install --disablerepo=* --enablerepo=rhui-REGION-rhel-server-rhscl rh-php71-php-odbc
sudo yum install --disablerepo=* --enablerepo=rhui-REGION-rhel-server-rhscl rh-php71-php-pgsql
We then added those two packages to the Ansible playbook so future generations would not suffer needlessly.
I am running a web server based on CentOS 5.8 and I need to upgrade my version of bind to make it PCI compliant. I'm currently running bind 9.3.6 and I need to have bind 9.9.8 or higher. I've tried yum update bind but apparently I already have the latest version according to yum. I did some Googling and I found an RPM file bind-9.10.2-1.el5.i686.rpm which looks like it would work but i don't know if it should try installing it or not. I think I would need bind-devel and bind-libs which I can get from the same site. Am I better off compiling from source? I know CentOS 5 is old but I'm trying to avoid reinstalling the whole server.
Installing binary rpm's from later versions of CentOS is unlikely to work: there are many changes since CentOS5.
Rebuilding a src.rpm locally is one way to see what issues there are.
Meanwhile, upgrading to CentOS6 (at least: CentOS7 uses systemd which takes some study) is often not a whole lot more effort than retrofitting something like bind, and will have other efficiencies. YMMV, everyone's does.
i would like to know, based on what rpm packages upgrade i can upgrade my RHEL version 5.11 to 6.x
We can't use re-installation of RHEL 6.x, so wanted an option(s) to upgrade to RHEL 6.x from 5.x by upgrading all needful packages.
By upgrading kernal or core rhel release rpm, can we upgrade to latest?
Please let me know details. Thank you.
In place upgrades between 4, 5, and 6 are not supported by RedHat and you risk impacting the support that you pay for by doing so. The only supported upgrade path is from 6 to 7. The expectation is that an upgrade path will continue in future releases.
You state that you cannot re-install but don't state why. Is it because the criticality of the system or is it because of the configuration of the application? I'm guessing the latter and that the system is not all that critical (because otherwise you wouldn't want to impact your support agreement). With that said, there is a way to upgrade and the procedure is provided by RedHat but, again, it is not supported by them.
The link is: In place upgrade
I want to upgrade database postgresql from version 8.3 to 9.0 on Jira application.
Which RPM should be used to work with Suse SLES10.3 64bit?
How to install Postgresql 9.0 in parallel to Postgresql 8.1?
The best bet to find packages for SUSE distributions is the openSUSE Build Service. The direct links there are a bit of a pain, so please look for yourself.
Parallel installation of multiple major PostgreSQL versions is not yet possible using SUSE RPMs. If you need to do that, you will probably need to build from source.