CVS Version on RHEL5 - linux

Currently I have CVS version 1.11.17 installed on RHEL4 server in my workspace. Now, my company is planning to upgrade to RHEL5.
Is the CVS version compatible with RHEL5, or we'll need to upgrade that too?

CVS has not changed in years. Development stopped 10 years ago. The cvs versions in RHEL4,5,6,7 will all be compatible.
In general:
1.11.x = The latest stable version
1.12.x = A newer version that was never declared 'stable' and then development on CVS stopped. In RHEL you will not be given the 1.12.x version. In some other distributions you may be.

Related

Apache version upgrade issue

At present we are on Apache/2.2.15 (UNIX) version. To fix the vulnerabilities we are suggested to upgrade to new version. I got new version from online using "wget" command and followed steps mentioned on this link http://httpd.apache.org/docs/2.2/install.html#download.
Once I am done, checked version using httpd -v. It gives me old version Apache/2.2.15 (UNIX). If I check using /usr/local/apache2/bin/httpd - v. It gives me new version. Did I successfully upgraded the version or not? If not what should I do?
I tried "yum install httpd" - It says "Nothing to do".
You now have two versions of Apache installed. You have the one installed with the system package manager (yum) in /usr/sbin/httpd. You have one installed manually in /usr/local/apache2/....
Which one you get will be determined entirely by which path you use.
In general, mixing system-managed packages with manually installed packages is a recipe for trouble. If you want to stick with the newer version in /usr/local, you should remove the system version, and realize that you will lose some manageability. For example, you will no longer be able to use yum install ... to install new Apache modules, and you will not be able to verify the installed files using tools like rpmverify.
If your distribution currently has Apache 2.2.x, that suggests your distribution is fairly old. For example, RHEL (and CentOS) 7 (and similar variants) have version 2.4.6 packaged, so you may want to update your host to something newer than whatever you're running now.
Yes, its successfully upgraded as per the screenshot.
httpd 2.2.15 is the version with RHEL 6 repository, here HTTPD_HOME is /etc/httpd (Highest version provided for HTTPD via RPM RHEL 6 is 2.2.15)
httpd 2.4.6 is the version with EPEL-HTTPD24 repository, here HTTPD_HOME is /usr/local/apache2/

RedHawk 2.0 final release

I previously installed the RedHawk 2.0 version dated 29 Oct 2015 but I now see on the RedHawk home page that there is a RedHawk 2.0 final release dated from Dec 2015. I downloaded the tar.gz, which has the same name as the one I installed before but a different sha1 checksum. So I untar'ed it and tried to update using yum but it found that no rpm's had new version numbers and so it said nothing to be done (yet diff says nearly every file has changed). How do I update to this newer release? If this is newer why didn't the version number go to 2.0.1 or at least the version numbers of the rpm's change?
Don't know what the deal is, but easiest thing to do would be remove all current redhawk stuff and replace with new:
sudo yum remove redhawk*
cd <redhawk-2.0.0...>
sudo yum install *rpm

How do I use yum to download software only from Centos 5.4 and not the latest

Requirement is to download software from Centos 5.4. When I do yum install , I get the latest version and not the one available for Centos 5.4.
How do I configure yum to download only from 5.4 repo?
As I said in my answer to your other question you need to find a repository that has a maintained, static entry for 5.4.
Most repositories have just one repository for each major version and upgrade it as new minor versions are released. But some keep specific repositories for each version independently (at least for a little while).
I would start with checking whether your current repository has an explicitly 5.4 repository (by using the URL in the yum.conf or /etc/yum.repos.d/*.repo file for the repository).
If that doesn't work out you get to try other mirrors as listed on the CentOS mirrors website.
As a fallback, and I encourage you to try to find a valid mirror first, you can find this sort of minor version specific repository on http://vault.centos.org.

removing older version of Ubuntu OS

I have installed ubuntu 10.x in my virtual box. From that i am upgrading the ubuntu machine to 12.04. Will the older versions[10.x] still remain in my machine or only the latest version will be available. If older versions available then how to clear my older versions of ubuntu? Please don't tell that install a new version of ubuntu. Because my data will be lost when i install a newer version of ubuntu.
Properly made upgrade process converts and replaces your old installation. That involves replacing libraries with never versions, updating sources list, converting and replacing configuration files etc. Some problems can appear, if you have not supported software installed (e.g. some PPA's can be not maintained for newer OS versions), but usually that is not a big issue.
All your private files and folders (your home folder) will survive this operation.
There are plenty of "how-tos" about upgrading Ubuntu to newer versions. Just take a look at how-do-i-upgrade-to-a-newer-version-of-ubuntu at AskUbuntu; after successfull upgrade you'll log into new version, no older version will remain on disk.
Of course, keep in mind that upgrading can take much more time than making a backup of your private files, doing clean install of new Ubuntu and getting your files back from backup.

Minor Version on libgcc_s.so.1 on Linux

I have noticed that on SLES SP1 and Ubuntu 10.04 they only have a major version of libgcc_s in /lib64. However on RHEL 6.1 they have the major version point to a minor version with the date appended to the minor version of the library. I need the minor version for a matrix I am providing to customer support. How do you obtain the minor version of libgcc in both Ubuntu and SLES?
The easiest way to handle this is to just rebuild on the other systems. Failing that, extract the tarball from the gcc SRPM and then use the commands in the spec file to rebuild it.

Resources