Birmingham mumbai

RPM 
packages
 for their distributions, and the 
dnf
 command to manage them. First, let's 
discuss Debian packages.
Debian packages
Debian packages
 have been the main type of package in Ubuntu for the entire 
existence of the distribution so far. When you search online for how to install 
something in Ubuntu, chances are, you're going to be installing a Debian package. 
These packages are known as Debian packages because Ubuntu is built from Debian 
sources and utilizes the same commands in order to install these packages. So even 
though Ubuntu is not Debian (Debian is a completely different distribution), they 
both use the same package format primarily.
The naming may be confusing for newcomers, because if Ubuntu is considered 
a different distribution than Debian, then why refer to its packages as "Debian" 
packages? Debian packages have a filename that ends in 
.deb
, and this package 
format originated in Debian. Ubuntu didn't develop its own package type; it uses 
the same package format as Debian. Therefore, whether we are installing packages 
in Debian or Ubuntu using a command such as 
apt
, Debian packages are the type of 
packages used for both.
If you've worked with Ubuntu before reading this book, then chances are, you've 
already used the 
apt
 series of commands to carry out some package management. 
Debian packages are great, because when paired with the 
apt
 command, they are 
easy to use and handle dependency resolution for you. However, they present some 
challenges and major drawbacks.
First, the majority of the distribution is made up of Debian packages. This means 
that the Linux kernel, system packages, libraries, and security updates are all Debian 
packages that are installed when you install Ubuntu Server. When you install 
security updates, Debian packages are installed. The reason this may be a problem is 
that other software you'll be installing, such as Apache, MariaDB, and so on, are also 
Debian packages, and may conflict with system packages when one package requires 
a pre-requisite package that conflicts with another. This can lead to a situation where 
you can't install packages at all. Package maintainers are generally good at avoiding 
this scenario, so conflicts aren't incredibly common nowadays.

---

Chapter 3