In this lesson, you’ll learn how to manage packaged module streams in RHEL 8. Application streams (or app streams) allow you to select from multiple versions of software packages grouped as modules, offering greater flexibility and compatibility for your environment. A module is a collection of packages that are typically installed together, while a profile is a subset of that module tailored for a specific purpose—for example, server configuration, client setup, or development environment. Module streams can be active (enabled) or inactive (disabled), and only one version of a module stream can be active at any given time. This setup ensures that only the designated version of a package and its dependencies are installed, with the YUM package manager handling all dependencies automatically.Documentation Index
Fetch the complete documentation index at: https://notes.kodekloud.com/llms.txt
Use this file to discover all available pages before exploring further.
If you ever need to verify which modules are available or currently active, the YUM package manager provides commands to list module streams and their profiles.
Viewing Available Modules
To display all available module streams, run the following command:Detailed Module Information and Installation
For more detailed information about a specific module, you can search within its listings. For instance, the Node.js module may list several versions (such as 10, 12, 14, and 16). By default, installing Node.js without specifying a version will install version 10 with the common profile. To install a specific version with a designated profile—for example, Node.js version 14 using the development profile—execute:Resetting Module Streams
If you need to revert to the default module settings—for example, to switch back to Node.js version 10 with the common profile—you can use the reset command:This lesson covered how to view available modules, install a specific module stream with a chosen profile, and reset module streams in RHEL 8 using the YUM package manager.