RH124 - ch13s05

Bookmark this page

P 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

Managing Software Updates with yum

yum is used to install and update software packages.

Objectives

After completing this section, students should be able to find, install, and update software packages using the yum command.

Working with yum

Using yum

yum is a powerful command-line tool that can be used to more flexibly manage (install, update, remove, and query) software packages. Official Red Hat packages are normally downloaded from Red Hat's content distribution network. Registering a system to the subscription management service automatically configures access to software repositories based on the attached subscriptions.

Finding software with yum

yum help will display usage information.

yum list displays installed and available packages.

[root@serverX ~]# yum list 'http*'
Loaded plugins: langpacks
Available Packages
httpcomponents-client.noarch                4.2.5-4.el7                 rhel_dvd
httpcomponents-core.noarch                  4.2.4-6.el7                 rhel_dvd
httpd.x86_64                                2.4.6-17.el7                rhel_dvd
httpd-devel.x86_64                          2.4.6-17.el7                rhel_dvd
httpd-manual.noarch                         2.4.6-17.el7                rhel_dvd
httpd-tools.x86_64                          2.4.6-17.el7                rhel_dvd

yum search KEYWORD lists packages by keywords found in the name and summary fields only.

To search for packages that have "web server" in their name, summary, and description fields, use search all:

[root@serverX ~]# yum search all 'web server'
Loaded plugins: langpacks
============================= Matched: web server ==============================
freeradius.x86_64 : High-performance and highly configurable free RADIUS server
hsqldb.noarch : HyperSQL Database Engine
httpd.x86_64 : Apache HTTP Server
libcurl.i686 : A library for getting files from web servers
libcurl.x86_64 : A library for getting files from web servers
mod_revocator.x86_64 : CRL retrieval module for the Apache HTTP server
mod_security.x86_64 : Security module for the Apache HTTP Server
python-paste.noarch : Tools for using a Web Server Gateway Interface stack

yum info PACKAGENAME gives detailed information about a package, including the disk space needed for installation.

To get information on the Apache HTTP Server:

[root@serverX ~]# yum info httpd
Loaded plugins: langpacks
Available Packages
Name        : httpd
Arch        : x86_64
Version     : 2.4.6
Release     : 17.el7
Size        : 1.1 M
Repo        : rhel_dvd
Summary     : Apache HTTP Server
URL         : http://httpd.apache.org/
License     : ASL 2.0
Description : The Apache HTTP Server is a powerful, efficient, and extensible
            : web server.

yum provides PATHNAME displays packages that match the pathname specified (which often include wildcard characters).

To find packages that provide the /var/www/html directory, use:

[root@serverX ~]# yum provides /var/www/html
Loaded plugins: langpacks
httpd-2.4.6-17.el7.x86_64 : Apache HTTP Server
Repo        : rhel_dvd
Matched from:
Filename    : /var/www/html



1:php-pear-1.9.4-21.el7.noarch : PHP Extension and Application Repository
                               : framework
Repo        : rhel_dvd
Matched from:
Filename    : /var/www/html

Installing and removing software with yum

yum install PACKAGENAME obtains and installs a software package, including any dependencies.

[root@serverX ~]# yum install httpd
Loaded plugins: langpacks
Resolving Dependencies
--> Running transaction check
---> Package httpd.x86_64 0:2.4.6-17.el7 will be installed
--> Processing Dependency: httpd-tools = 2.4.6-17.el7 for package: httpd-2.4.6-17.el7.x86_64
--> Processing Dependency: /etc/mime.types for package: httpd-2.4.6-17.el7.x86_64
--> Processing Dependency: libapr-1.so.0()(64bit) for package: httpd-2.4.6-17.el7.x86_64
--> Processing Dependency: libaprutil-1.so.0()(64bit) for package: httpd-2.4.6-17.el7.x86_64
--> Running transaction check
---> Package apr.x86_64 0:1.4.8-3.el7 will be installed
---> Package apr-util.x86_64 0:1.5.2-6.el7 will be installed
---> Package httpd-tools.x86_64 0:2.4.6-17.el7 will be installed
---> Package mailcap.noarch 0:2.1.41-2.el7 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
 Package             Arch           Version              Repository        Size
================================================================================
Installing:
 httpd               x86_64         2.4.6-17.el7         rhel_dvd         1.1 M
Installing for dependencies:
 apr                 x86_64         1.4.8-3.el7          rhel_dvd         100 k
 apr-util            x86_64         1.5.2-6.el7          rhel_dvd          90 k
 httpd-tools         x86_64         2.4.6-17.el7         rhel_dvd          76 k
 mailcap             noarch         2.1.41-2.el7         rhel_dvd          31 k

Transaction Summary
================================================================================
Install  1 Package (+4 Dependent packages)

Total download size: 1.4 M
Installed size: 4.3 M
Is this ok [y/d/N]:

yum update PACKAGENAME obtains and installs a newer version of the software package, including any dependencies. Generally the process tries to preserve configuration files in place, but in some cases, they may be renamed if the packager thinks the old one will not work after the update. With no PACKAGENAME specified, it will install all relevant updates.
```
[root@serverX ~]# yum update
```
Since a new kernel can only be tested by booting to that kernel, the package is specifically designed so that multiple versions may be installed at once. If the new kernel fails to boot, the old kernel is still available. Using yum update kernel will actually install the new kernel. The configuration files hold a list of packages to "always install" even if the administrator requests an update.
Note
Use yum list kernel to list all installed and available kernels. To view the currently running kernel, use the uname command. The -r option will show only the kernel version and release, and the -a option will show the kernel release and additional information.
```
[root@serverX ~]# yum list kernel
Loaded plugins: langpacks
Installed Packages
kernel.x86_64             3.10.0-123.0.1.el7             @anaconda/7.0          
kernel.x86_64             3.10.0-84.el7                  @rhel-7-server-htb-rpms
[root@serverX ~]# uname -r
3.10.0-123.el7.x86_64
[root@serverX ~]# uname -a
Linux demo.example.com 3.10.0-123.el7.x86_64 #1 SMP Tue Nov 26 16:51:22 EST 2013 x86_64 x86_64 x86_64 GNU/Linux
	
```
yum remove PACKAGENAME removes an installed software package, including any supported packages.
```
[root@serverX ~]# yum remove httpd
```
Warning
yum remove will remove the package(s) listed and any package that requires the package(s) being removed (and package(s) which require those packages, and so on). This can lead to unexpected removal of packages, so carefully check the list of packages to be removed.

Installing and removing groups of software with yum

yum also has the concept of groups, which are collections of related software installed together for a particular purpose. In Red Hat Enterprise Linux 7, there are two kinds of groups. Regular groups are collections of packages. Environment groups are collections of other groups which include their own packages. The packages or groups provided by a group may be mandatory (must be installed if the group is installed), default (are normally installed if the group is installed), or optional (are not installed when the group is unless asked for specifically).
Like yum list, the yum group list (or yum grouplist) command will show the names of installed and available groups. Some groups are normally installed through environment groups and are hidden by default. These hidden groups can also be listed with the yum group list hidden command. If the ids option is added, the group ID will also be shown. Groups can be installed, updated, removed, and otherwise queried by name or ID.
```
[root@serverX ~]# yum group list
Loaded plugins: langpacks
Available environment groups:
   Minimal install
   Infrastructure Server
   File and Print Server
   Web Server
   Virtualization Host
   Server with GUI
Installed groups:
   Base
   Desktop Debugging and Performance Tools
   Dial-up Networking Support
   Fonts
   Input Methods
   Internet Browser
   PostgreSQL Database server
   Printing client
   X Window System
Available Groups:
   Additional Development
   Backup Client
   Backup Server
...
```

Information about a group is displayed with yum group info (or yum groupinfo). It includes a list of mandatory, default, and optional package names or group IDs. The package names or group IDs may have a marker in front of them.

Marker	Meaning
`=`	Package is installed, was installed as part of the group
`+`	Package isn't installed, will be if the group is installed or updated
`-`	Package isn't installed, will not be if the group is installed or updated
no marker	Package is installed, but was not installed through the group.

[root@serverX ~]# yum group info "Identity Management Server"
Loaded plugins: langpacks

Group: Identity Management Server
 Group-Id: identity-management-server
 Description: Centralized management of users, servers and authentication policies.
 Default Packages:
   +389-ds-base
   +ipa-admintools
   +ipa-server
   +pki-ca
 Optional Packages:
   +ipa-server-trust-ad
   +nuxwdog
   +slapi-nis

The yum group install (or yum groupinstall) command will install a group which will install its mandatory and default packages and the packages they depend on.

[root@serverX ~]# yum group install "Infiniband Support"
...
Transaction Summary
================================================================================
Install  17 Packages (+7 Dependent packages)

Total download size: 9.0 M
Installed size: 33 M
Is this ok [y/d/N]:
...

Important

The behavior of yum groups has changed in Red Hat Enterprise Linux 7 from Red Hat Enterprise Linux 6 and earlier. In RHEL 7, groups are treated as objects, and are tracked by the system. If an installed group is updated, and new mandatory or default packages have been added to the group by the yum repository, those new packages will be installed on update.

RHEL 6 and earlier consider a group to be installed if all its mandatory packages have been installed; or if it had no mandatory packages, if any default or optional packages in the group are installed. In RHEL 7, a group is considered to be installed only if yum group install was used to install it. A new command in RHEL 7, yum group mark install GROUPNAME can be used to mark a group as installed, and any missing packages and their dependencies will be installed on the next update.

Finally, RHEL 6 and earlier did not have the two-word form of the yum group commands. In other words, in RHEL 6 the command yum grouplist existed, but the equivalent RHEL 7 command yum group list did not.

Viewing transaction history

All install and remove transactions are logged in /var/log/yum.log.

[root@serverX ~]# tail -5 /var/log/yum.log
Feb 16 14:10:41 Installed: libnes-1.1.3-5.el7.x86_64
Feb 16 14:10:42 Installed: libmthca-1.0.6-10.el7.x86_64
Feb 16 14:10:43 Installed: libmlx4-1.0.5-7.el7.x86_64
Feb 16 14:10:43 Installed: libibcm-1.0.5-8.el7.x86_64
Feb 16 14:10:45 Installed: rdma-7.0_3.13_rc8-3.el7.noarch

A summary of install and remove transactions can be viewed with yum history.

[root@serverX ~]# yum history
Loaded plugins: langpacks
ID     | Login user               | Date and time    | Action(s)      | Altered
-------------------------------------------------------------------------------
     6 | Student User <student>   | 2014-02-16 14:09 | Install        |   25   
     5 | Student User <student>   | 2014-02-16 14:01 | Install        |    1   
     4 | System <unset>           | 2014-02-08 22:33 | Install        | 1112 EE
     3 | System <unset>           | 2013-12-16 13:13 | Erase          |    4   
     2 | System <unset>           | 2013-12-16 13:13 | Erase          |    1   
     1 | System <unset>           | 2013-12-16 13:08 | Install        |  266   
history list

A transaction can be reversed with the history undo options:

[root@serverX ~]# yum history undo 6
Loaded plugins: langpacks
Undoing transaction 6, from Sun Feb 16 14:09:51 2014
    Install     dapl-2.0.39-2.el7.x86_64              @rhel-7-server-htb-rpms
    Dep-Install graphviz-2.30.1-18.el7.x86_64         @rhel-7-server-htb-rpms
    Dep-Install graphviz-tcl-2.30.1-18.el7.x86_64     @rhel-7-server-htb-rpms
    Install     ibacm-1.0.8-4.el7.x86_64              @rhel-7-server-htb-rpms
    Install     ibutils-1.5.7-9.el7.x86_64            @rhel-7-server-htb-rpms
    Dep-Install ibutils-libs-1.5.7-9.el7.x86_64       @rhel-7-server-htb-rpms   
...

Summary of yum commands

Packages can be located, installed, updated, and removed by name or by package groups.

Task:	Command:
List installed and available packages by name	yum list [NAME-PATTERN]
List installed and available groups	yum grouplist
Search for a package by keyword	yum search KEYWORD
Show details of a package	yum info PACKAGENAME
Install a package	yum install PACKAGENAME
Install a package group	yum groupinstall "GROUPNAME"
Update all packages	yum update
Remove a package	yum remove PACKAGENAME
Display transaction history	yum history

References

yum(1) and yum.conf(5) man pages

Additional information on yum may be available in the Red Hat Enterprise Linux System Administrator's Guide for Red Hat Enterprise Linux 7, which can be found at https://access.redhat.com/documentation/

Discuss Red Hat System Administration I

Go to community

RH124 Chapter 15 Lab 3: Install zsh Package

VictoriaB97

16 sty 2024

Hello,I am trying to finish up Lab 3 of the Chapter 15 Comprehensive Review Labs in RH124, and when I type in sudo dnf install zsh for the 6th specification of the lab, I get an error message basically saying that it failed to download metadata for the repo 'ansible-2.9-for-rhel-9-x86_64-rpms', and that they could not download repomd.xml. It provided a 404 status code.Can someone please let me know what the problem is, and if there is a current workaround? Thanks.

378

Red Hat System Administration I | Guided Exercise: Explain and Investigate RPM Software Pack

AbeHiero

10 lis 2023

I cannot start the lab with command: lab start software-rpm. I get this error:ModuleNotFoundError: No module named 'rhcsa-classroom'Script software-rpm not in course library rhcsa-classroom Anyone else see this?

172

Red Hat System Administration I (RH124)

Haley_Ruccio

19 lip 2023

The first of two courses covering the core system administration tasks needed to manage Red Hat Enterprise Linux serversRed Hat System Administration I (RH124) is designed for IT professionals without previous Linux system administration experience. The course provides students with Linux administration competence by focusing on core administration tasks. This course also provides a foundation for students who plan to become full-time Linux system administrators by introducing key command-line concepts and enterprise-level tools. This course is the first of a two-course series that takes a computer professional without Linux system administration knowledge to become a fully capable Linux administrator. These concepts are further developed in the follow-on course, Red Hat System Administration II (RH134).This course is based on Red Hat® Enterprise Linux 9.0.Course content summaryIntroduce Linux and the Red Hat Enterprise Linux ecosystem.Run commands and view shell environments.Manage, organize, and secure files.Manage users, groups and user security policies.Control and monitor systemd services.Configure remote access using the web console and SSH.Configure network interfaces and settings.Manage software using DNFAudience for this courseThe primary persona is a technical professional with current or pending responsibilities as a Linux enterprise or cloud system administrator.This course is popular in Red Hat Academy, and is targeted at the student who is planning to become a technical professional using Linux.Prerequisites for this courseBasic technical user skills with computer applications on some operating systems are expected.Take our free assessment to gauge whether this offering is the best fit for your skills.Technology considerationsThere are no special technical requirements for this course.This course is not designed for bring your own device (BYOD).Internet access is not required but is recommended so that students can research and browse Red Hat online resources.

336

Revision: rh124-7-1b00421

Red Hat System Administration I