The document discusses different methods for getting and managing software on Linux systems. It describes how PackageKit makes it easy to install, remove, and manage software packages. It also explains how to use the RPM and YUM package managers to install software packages and their advantages over using tarballs, which do not track dependencies and versions as easily.
The document discusses different methods for getting and managing software on Linux systems. It describes how PackageKit makes it easy to install, remove, and manage software packages. It also explains how to use the RPM and YUM package managers to install software packages and their advantages over using tarballs, which do not track dependencies and versions as easily.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 16
SUBJECT NAME:-
SYSTEM & NETWORK
ADMINISTRATION PRESENTATION TOPIC:- GETTING AND MANAGING SOFTWARE PRESENTED BY:- NAMRAIZA ASLAM 02 SODAH NASEEM 10 SYEDA MUBEEN FATIMA 18 SYEDA MUNTAHA BATOOL 22 MAHNOOR SALEEM 27 PRESENTED TO:- MA’M MARIYA Getting and Managing Software Linux software management is so easy these days is a credit to the Linux community, which has worked diligently to create packaging formats, complex installation tools, and high-quality software packages. Not only is it easy to get the software, but once it’s installed, it’s easy to manage, query, update, and remove it. Managing Software with PackageKit PackageKit is a set of programs that provide graphical windows, and other components, for installing, removing, and otherwise managing software in Fedora and Red Hat Enterprise Linux. Ubuntu uses components of PackageKit, but not the entire interface. Tarball
A tarball, containing executable files
(commands), documentation, configuration files, and libraries. (A tarball is a single file in which multiple files are gathered together for convenient storage or distribution.) When you install software from a tarball, the files from that tarball might be spread across your Linux system in appropriate directories (/usr/share/man, /etc, /bin, and /lib, to name a few). Difficulties with Tarball
Get dependent software —You
would need to know if the software you were installing depended on other software being installed for your software to work. Then you would have to track down that software and install that too (which might itself have some dependencies). List the software — Even if you knew the name of the command, you might not know where its documentation or configuration files were located when you looked for it later. Remove the software — Unless you kept the original tarball or a list of files, you wouldn’t know where all the files were when it came time to remove them. Even if you knew, you would have to remove each one individually. Update the software — Tarballs are not designed to hold metadata about the contents they contain. Once the contents of a tarball are installed, you may not have a way to tell what version of the software you are using, making it difficult to track down bugs and get new versions of your software. RPM(Red Hat Package Manager)
RPM (Red Hat Package Manager) is an
default open source and most popular package management utility for Red Hat based systems like (RHEL, CentOS and Fedora). • The tool allows system administrators and users to install, update, uninstall, query, verify and manage system software packages in Unix/Linux operating systems. • The RPM formerly known as .rpm file Facts about RPM
• RPM is free and released under GPL (General
Public License). • RPM keeps the information of all the installed packages under /var/lib/rpm database. • RPM is the only way to install packages under Linux systems, if you’ve installed packages using source code, then rpm won’t manage it. • RPM deals with .rpm files, which contains the actual information about the packages such as: what it is, from where it comes, dependencies info, version info etc. There are generally two ways to install RPM files manually. using a file previously downloaded to your hard drive install the RPM from some sort of removable media such as a CD-ROM drive . Where .rpm is an extension of an RPM file. There are five basic modes for RPM command • Install : It is used to install any RPM package. • Remove : It is used to erase, remove or un- install any RPM package. • Upgrade : It is used to update the existing RPM package. • Verify : It is used to query about different RPM packages. • Query : It is used for the verification of any RPM package. What is in an RPM
To find out the name of an RPM package
currently installed on your system (such as the Firefox web browser). # rpm -q firefox firefox-10.0.3-1.el6_2.x86_64 From this, you can tell that the basename of the package is firefox. The release number is10.0.3, the version number is 1, The firefox package was built for Red Hat Enterprise Linux 6.2 (el6_2) and is compiled for the X86 64-bit architecture (x86_64). YUM(YellowDog Updater Modified) YUM (Yellowdog Updater Modified) is an open source command-line as well as graphical based package management tool for RPM (RedHat Package Manager) based Linux systems. It allows users and system administrator to easily install, update, remove or search software packages on a systems. Working With YUM
Search for a package when you know the name
$ yum list 'foo‘ Search for a package when you're not sure of the name $ yum search 'foo*‘ $ yum search '*foo?‘ install and remove a package or multiple packages # yum install 'foo‘ # yum remove 'foo‘ # yum install 'foo fie fofum‘ # yum remove 'foo fie fofum' Update an installed package # yum update 'foo‘
List available updates for installed packages
# yum list updates
Update the whole system:
# yum update RPM YUM RPM can install only single YUM can install multiple Package at a time. packages at a time. RPM cannot resolve the YUM can resolve dependencies. dependencies automatically. YUM can Rollback any Cannot Rollback with changes. RPM.