The dependency between software packages is A headache for administrators in Linux system maintenance. It is often because you want to install software A. However, when compiling, it tells you that software B is required before software X is installed, when you install the Y software, you will be told that the Z library is required-it is hard to install the Z library, and the version is found to be faulty ...... many of my friends may have had this experience. In fact, the open-source community has already tried to solve this problem. Different releases have released their own tools, such as YUM and Debian of YellowDog.
The dependency between software packages is A headache for administrators in Linux system maintenance. It is often because you want to install software A. However, when compiling, it tells you that software B is required before software X is installed, when you install the Y software, you will be told that the Z library is required-it is hard to install the Z library, and the version is found to be faulty ...... many of my friends may have had this experience. In fact, the open-source community has already tried to solve this problem. Different releases have released their own tools, such as YUM of Yellow Dog and APT (Advanced Packaging Tool) of Debian. These software has been gradually transplanted to other releases by open-source software enthusiasts.
The upgrade of RedHat Enterprise Linux often brings many problems to administrators: the website download speed is too slow and not safe enough ...... of course, more people cannot be updated-copyright issues. After a period of comparison, we feel that using APT to maintain RHEL has special convenience. (Some friends may say that YUM is also good! Yes, YUM does do a good job in many cases. However, if Linux is RHEL, it is difficult to find a database suitable for YUM. "It's hard to find a database without rice ".) Now we will introduce the specific methods for your reference.
APT Introduction
Debian GNU/Linux is the creator of APT. The original intention is to use tools to solve the dependency problem during software installation. The working principle is roughly as follows: the user installs the APT client tool, searches for the RPM software package information on the database (repositories) of the APT server, analyzes the dependencies between the software packages, downloads and installs them.
Installation and configuration
First, let's install the APT tool:
# wget redhat.uni-klu.ac.at/el3/apt.i386.rpm # rpm -Uvh apt.i386.rpm
|
Is the installation simple enough? Edit the configuration file:
#vi /etc/apt/sources.list.d/dag.list
|
Add the following content (Database-related information ):
rpm afs.caspur.it/ afs/italia/project/linux /cern/slc302/i386/apt os updates extras rpm redhat.uni-klu.ac.at redhat/dag/el3/i386 dag rpm-src redhat.uni-klu.ac.at redhat/dag/el3/i386 dag rpm apt.sw.be redhat/el3/en/i386 dag rpm-src apt.sw.be redhat/el3/en/i386 dag
|
Note: The first database of afs. caspur. it/is almost the content of the Redhat official site. It is valid when writing this article. If you want to update the Kernel, you can add kernel26 after the first one.