RHEL 8 introduces the concept of Application Streams. Multiple versions of user space components are now delivered and updated more frequently than the core operating system packages. This provides greater flexibility to customize Red Hat Enterprise Linux without impacting the underlying stability of the platform or specific deployments. Components made available as Application Streams can be packaged as modules or RPM packages, and are delivered through the AppStream repository in RHEL 8. Each Application Stream has a given life cycle, either the same as RHEL 8 or shorter, more suitable to the particular application. Application Streams with a shorter life cycle are listed in the Red Hat Enterprise Linux 8 Application Streams Life Cycle page. Modules are collections of packages representing a logical unit: an application, a language stack, a database, or a set of tools. These packages are built, tested, and released together. Module streams represent versions of the Application Stream components. For example, two streams (versions) of the PostgreSQL database server are available in the postgresql module: PostgreSQL 10 (the default stream) and PostgreSQL 9.6. Only one module stream can be installed on the system. Different versions can be used in separate containers. Detailed module commands are described in the Installing, managing, and removing user-space components document. For a list of modules available in AppStream, see the Package manifest. yum allows you to perform a complete set of operations with software packages. The following section describes how to use yum to: Use the following procedure to find a package providing a particular application or other content. Procedure
Use the following procedure to list installed and available packages. Procedure
Note that you can filter the results by appending global expressions as arguments. See Specifying global expressions in yum input for more details. Use the following procedure to list enabled and disabled repositories. Procedure
Note that you can filter the results by passing the ID or name of repositories as arguments or by appending global expressions. See Specifying global expressions in yum input for more details. You can display various types of information about a package using YUM, for example version, release, size, loaded plugins, and more. Procedure
Note that you can filter the results by appending global expressions as arguments. See Specifying global expressions in yum input for more details. Use yum to view installed package groups and filter the listing results. Procedure
Note that you can filter the results by appending global expressions as arguments. See Specifying global expressions in yum input for more details. yum commands allow you to filter the results by appending one or more glob expressions as arguments. You have to escape global expressions when passing them as arguments to the yum command. Procedure To ensure global expressions are passed to yum as intended, use one of the following methods:
The following section describes how to use yum to:
Note that you can optimize the package search by explicitly defining how to parse the argument. See Section 12.4.3, “Specifying a package name in YUM input” for more details. The following procedure describes how to install a package group by a group name or by a groupID using yum. Procedure
To optimize the installation and removal process, you can append -n, -na, or -nerva suffixes to yum install and yum remove commands to explicitly define how to parse an argument:
yum allows you to check if your system has any pending updates. You can list packages that need updating and choose to update a single package, multiple packages, or all packages at once. If any of the packages you choose to update have dependencies, they are updated as well. The following section describes how to use yum to:
The following procedure describes how to check the available updates for packages installed on your system using yum. Procedure
Use the following procedure to update a single package and its dependencies using yum.
When applying updates to kernel, yum always installs a new kernel regardless of whether you are using the yum update or yum install command. Use the following procedure to update a group of packages and their dependencies using yum. Procedure
Use the following procedure to update all packages and their dependencies using yum. Procedure
To check and download package updates automatically and regularly, you can use the DNF Automatic tool that is provided by the dnf-automatic package. DNF Automatic is an alternative command-line interface to yum that is suited for automatic and regular execution using systemd timers, cron jobs and other such tools. DNF Automatic synchronizes package metadata as needed and then checks for updates available. After, the tool can perform one of the following actions depending on how you configure it:
The outcome of the operation is then reported by a selected mechanism, such as the standard output or email. The following procedure describes how to install the DNF Automatic tool. Procedure
Verification steps
By default, DNF Automatic uses /etc/dnf/automatic.conf as its configuration file to define its behavior. The configuration file is separated into the following topical sections:
With the default settings of the /etc/dnf/automatic.conf file, DNF Automatic checks for available updates, downloads them, and reports the results as standard output. Settings of the operation mode from the [commands] section are overridden by settings used by a systemd timer unit for all timer units except dnf-automatic.timer. Additional resources
To run DNF Automatic, you always need to enable and start a specific systemd timer unit. You can use one of the timer units provided in the dnf-automatic package, or you can write your own timer unit depending on your needs. The following section describes how to enable DNF Automatic. Prerequisites
For more information on DNF Automatic configuration file, see Section 2.5.6.2, “DNF Automatic configuration file”. Procedure
For downloading available updates, use: # systemctl enable dnf-automatic-download.timer# systemctl start dnf-automatic-download.timerFor downloading and installing available updates, use: # systemctl enable dnf-automatic-install.timer# systemctl start dnf-automatic-install.timerFor reporting about available updates, use: # systemctl enable dnf-automatic-notifyonly.timer# systemctl start dnf-automatic-notifyonly.timerOptionally, you can use: # systemctl enable dnf-automatic.timer# systemctl start dnf-automatic.timerIn terms of downloading and applying updates, this timer unit behaves according to settings in the /etc/dnf/automatic.conf configuration file. The default behavior is similar to dnf-automatic-download.timer: it downloads the updated packages, but it does not install them. Alternatively, you can also run DNF Automatic by executing the /usr/bin/dnf-automatic file directly from the command line or from a custom script. Verification steps
The systemd timer units take precedence and override the settings in the /etc/dnf/automatic.conf configuration file concerning downloading and applying updates. For example if you set the following option in the /etc/dnf/automatic.conf configuration file, but you have activated the dnf-automatic-notifyonly.timer unit, the packages will not be downloaded: download_updates = yesThe dnf-automatic package includes the following systemd timer units: Additional resources
The following section describes how to use yum to:
Use the following procedure to remove a package either by the group name or the groupID. Procedure
yum is not able to remove a package without removing depending packages. Note that you can optimize the package search by explicitly defining how to parse the argument. See Specifying a package name in yum input for more details. Use the following procedure to remove a package either by the group name or the groupID. Procedure
To optimize the installation and removal process, you can append -n, -na, or -nerva suffixes to yum install and yum remove commands to explicitly define how to parse an argument:
A package group is a collection of packages that serve a common purpose (System Tools, Sound and Video). Installing a package group pulls a set of dependent packages, which saves time considerably. The following section describes how to use yum to:
Use yum to view installed package groups and filter the listing results. Procedure
Note that you can filter the results by appending global expressions as arguments. See Specifying global expressions in yum input for more details. The following procedure describes how to install a package group by a group name or by a groupID using yum. Procedure
Use the following procedure to remove a package either by the group name or the groupID. Procedure
yum commands allow you to filter the results by appending one or more glob expressions as arguments. You have to escape global expressions when passing them as arguments to the yum command. Procedure To ensure global expressions are passed to yum as intended, use one of the following methods:
The yum history command allows you to review information about the timeline of yum transactions, dates and times they occurred, the number of packages affected, whether these transactions succeeded or were aborted, and if the RPM database was changed between transactions. yum history command can also be used to undo or redo the transactions. The following section describes how to use yum to:
Use the following procedure to list the latest transactions, the latest operations for a selected package, and details of a particular transaction. Procedure
The following procedure describes how to revert a selected transaction or the last transaction using yum. Procedure
Note that the yum history undo command only reverts the steps that were performed during the transaction. If the transaction installed a new package, the yum history undo command uninstalls it. If the transaction uninstalled a package, the yum history undo command reinstalls it. yum history undo also attempts to downgrade all updated packages to their previous versions, if the older packages are still available. Use the following procedure to repeat a selected transaction or the last transaction using yum. Procedure
Note that the yum history redo command only repeats the steps that were performed during the transaction. yum commands allow you to filter the results by appending one or more glob expressions as arguments. You have to escape global expressions when passing them as arguments to the yum command. Procedure To ensure global expressions are passed to yum as intended, use one of the following methods:
The configuration information for yum and related utilities are stored in the /etc/yum.conf file. This file contains one or more [repository] sections, which allow you to set repository-specific options. It is recommended to define individual repositories in new or existing .repo files in the /etc/yum.repos.d/ directory. Note that the values you define in individual [repository] sections of the /etc/yum.conf file override values set in the [main] section. The following section describes how to:
The /etc/yum.conf configuration file contains the [repository] sections, where repository is a unique repository ID. The [repository] sections allows you to define individual yum repositories. Do not give custom repositories names used by the Red Hat repositories to avoid conflicts. For a complete list of available [repository] options, see the [repository] OPTIONS section of the yum.conf(5) manual page. Procedure To define a new repository, you can:
yum repositories commonly provide their own .repo file. It is recommended to define your repositories in a .repo file instead of /etc/yum.conf as all files with the .repo file extension in this directory are read by yum.
Obtaining and installing software packages from unverified or untrusted sources other than Red Hat certificate-based Content Delivery Network (CDN) constitutes a potential security risk, and could lead to security, stability, compatibility, and maintainability issues. Once you added a `yum`repository to your system, enable it to ensure installation and updates. Procedure
Disable a specific YUM repository to prevent particular packages from installation or update. Procedure
The configuration information for yum and related utilities are stored in the /etc/yum.conf file. This file contains one mandatory [main] section, which enables you to set yum options that have global effect. The following section describes how to:
Use the following procedure to view the current yum configurations. Procedure
The /etc/yum.conf configuration file contains one [main] section. The key-value pairs in this section affect how yum operates and treats repositories. You can add additional options under the [main] section heading in /etc/yum.conf. For a complete list of available [main] options, see the [main] OPTIONS section of the yum.conf(5) manual page. yum provides plug-ins that extend and enhance its operations. Certain plug-ins are installed by default. The following section describes how to enable, configure, and disable yum plug-ins. Procedure The plug-in configuration files always contain a [main] section where the enabled= option controls whether the plug-in is enabled when you run yum commands. If this option is missing, you can add it manually to the file. Every installed plug-in has its own configuration file in the /etc/dnf/plugins/ directory. You can enable or disable plug-in specific options in these files. The following procedure describes how to disable or enable all YUM plug-ins, disable all plug-ins for a particular command, or certain YUM plug-ins for a single command. + Procedure
|