Day 7 : Understanding package manager and systemctl
Day 7 of our learning journey delves into the intricacies of package management and the powerful capabilities of systemctl. Whether you are a beginner seeking to grasp the fundamentals or a seasoned user looking to expand your knowledge, this article will provide you with a comprehensive understanding of these essential tools.
In the vast world of Linux and Unix-based operating systems, there are two crucial tools that every aspiring system administrator or Linux enthusiast must familiarize themselves with: the package manager and the systemctl command. These tools form the backbone of software management and system control, enabling users to effortlessly install, update, and remove packages, as well as manage and control system services.
What is a Package Manager in Linux?
In simpler words, Package manager is a tool that allows users to install, remove, upgrade, configure and manage software packages on an operating system.
You’ll often find me using the term ‘package’ in tutorials and articles, To understand package manager, you must understand what a package is.
What is a package?
A package is usually referred to an application but it could be a GUI application, cmd line tool or a software library (required by other software programs).
A package is essentially an archive file containing the binary executable, configuration file and sometimes information about the dependencies.
Different kinds of package managers
Package Managers differ based on packaging system but same packaging system may have more than one package manager.
For example, RPM has Yum and DNF package managers. For DEB, you have apt-get, aptitude command line based package managers.
What is systemctl and systemd?
systemctl is used to examine and control the state of “systemd” system and service manager.
systemd is system and service manager for Unix like operating systems(most of the distributions, not all).
We performed below tasks to get a better hands-on :
- Install Docker and Jenkins, Checked the status of docker and Jenkins.
