Skip to main content

Understanding Yum in Linux

Understanding Yum in Linux


Yum overview
RPM knows what its dependencies are, and has the ability to download software from FTP and web servers. 
Yum was created by Yellowdog Linux, and has since been adopted by many Red Hat-based distributions including Fedora and CentOS. 
Yum resolves dependencies automatically. This means it downloads and installs all software packages necessary. 
This includes packages that the user didn't specify, if the chosen package requires them. Y
Yum has also the concept of software package groups. A group is a list of software that is usually installed together. 

For instance, we could have a web server group that included the web server, and other tools commonly installed with it. Yum repositories contain RPM software packages. 
The Yum client maintains a local list of software repositories. Users can add repositories by just adding a new Yum configuration file for them. 
The Yum client also maintains a local list of all available software. The package install process using Yum is pretty straightforward. 
First, the Yum client contacts the repositories that it's aware of, and gets their list of software packages. 
These lists are then cached locally, and it updates them during install operations. 
The user then selects a software package that they want to install. Users can select packages to install by using either CLI or GUI tools. 
Yum then calculates dependencies. This would be the requested software package, and any packages that it requires. 
Yum then downloads all software packages and installs them using the RPM libraries, just like the RPM command does. 
Once the install has finished, Yum updates the RPM package database. 
Installing software using Yum couldn't be easier. 
Yum also has the concept of software groups. Yum groups contain multiple software packages. 
These software packages are usually installed together. All software in a group can be installed at once. 
All software in a group can be removed at once. Groups can contain optional software. 
Option software is related software, but not installed by default. Groups make configuring a system quicker. 
Installing a group of software with one command is much easier than installing each package individually.


Yum commands:

1) show package list in repository
yum list <name>

yum list samba

2) Show all version of packages in repository

yum --showduplicates list samba*

3) Get information on package

yum list 
yum info <name>


ex. yum info samba

4) Get info on installed packages

yum list installed

Output Color Codes:

All package in Bold and Underline means -Curent Kernel Version
All package in Bold means -Have updates available
All package in Red means- Package is not in our repository
All package in yellow means -package in installed with higher version that in repository

5) To only download rpm 

yum install -downloadonly -downloaddir=/tmp

6)Get all packages with updates available

yum list updates

7)Get list of packages available in repository

yum list available

Output Color Codes:

Blue: An updated to an installed package
Cyan: Downgrade to a installed package
Green and Underlined: Current Version of installed package


8) Check all package

yum list all

9) Check obsolete package list
yum list obsoletes

10)Check more information on package

yum info <package name>

yum info zip
yum info updates (check information on updates)
yum info obsoletes (check information on obsoletes)

11) Check dependency of a package

yum deplist <package name>
yum deplist zip

12) Checking various package groups

yum group list

13) Checking hidden groups

yum group list hidden

14) Checking group information

yum group info "group name"

yum group info "Development Tools"

15) Searching a package using yum

yum search <package name>

yum search zip

we can also search all which will search description as well

yum search all zip

16) Find which package can provide specific utility

yum provides <package name>

yum provides zip

Comments

Popular posts from this blog

WebLogic migration to OCI using WDT tool

WebLogic migration to OCI using WDT tool Oracle WebLogic Deploy Tool (WDT) is an open-source project designed to simplify and streamline the management of Oracle WebLogic Server domains. With WDT, you can export configuration and application files from one WebLogic Server domain and import them into another, making it a highly effective tool for tasks like migrating on-premises WebLogic configurations to Oracle Cloud. This blog outlines a detailed step-by-step process for using WDT to migrate WebLogic resources and configurations. Supported WLS versions Why Use WDT for Migration? When moving Oracle WebLogic resources from an on-premises environment to Oracle Cloud (or another WebLogic Server), WDT provides an efficient and reliable approach to: Discover and export domain configurations and application binaries. Create reusable models and archives for deployment in a target domain. Key Pre-Requisites Source System: An Oracle WebLogic Server with pre-configured resources such as: Applica...

How to Validate TDE Wallet Password in Oracle Database

How to Validate TDE Wallet Password in Oracle Database Validating the Transparent Data Encryption (TDE) wallet password is crucial, especially when ensuring that the password is correct without using the OPEN or CLOSE commands in the database. This blog post explains a straightforward method to validate the TDE password using the mkstore utility. Steps to Validate TDE Wallet Password Follow these steps to validate the TDE wallet password: Step 1: Copy the Keystore/Wallet File Navigate to your existing TDE wallet directory. Copy only the ewallet.p12 file to a new directory. If a cwallet.sso file exists, do not copy it . The absence of cwallet.sso ensures that the wallet does not use auto-login, forcing the utility to prompt for the password. Step 2: Validate Using mkstore Use the mkstore utility to check the contents of the wallet file. The mkstore utility will prompt you for the TDE wallet password, allowing you to validate its correctness. Command Syntax To display the conten...

Rename a PDB in Oracle Database Multitenant Architecture in TDE and Non TDE Environment

Rename a PDB in Oracle Database Multitenant Architecture I am sharing a step-by-step guide to help you rename a PDB. This approach uses SQL commands. Without TDE or encryption Wallet Initial Check Check the Current Database Name and Open Mode: SQL > SELECT NAME, OPEN_MODE FROM V$DATABASE; NAME OPEN_MODE --------- -------------------- BEECDB READ WRITE List Current PDBs: SQL > SHOW PDBS; CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 2 PDB$SEED READ ONLY NO 3 FUAT READ WRITE NO We need to RENAME FUAT to BEE  Steps to Rename the PDB Step 1: Export ORACLE_SID Set the Oracle SID to the Container Database (CDB): export ORACLE_SID=BEECDB Step 2: Verify Target PDB Name Availability If the target PDB name is different from the current PDB name, ensure no service exists with the target PDB name. Run SQL to Check Exi...