Fundamentals for Using an Application Package Manager and Other Lab Assignments
Objectives: ➢ Learn the fundamentals for using an application package manager. ➢ Understand the Red Hat Package Manager (RPM) command and options. ➢ Demonstrate the use of RPM to install, update, and remove packages.
Resources Needed
➢ One classroom workstation, lab workstation, or home PC. ➢ One NETW-240 hard drive loaded with Fedora Linux or iLab access. ➢ Week 2 Lab 2 assignment with attached answer sheet. ➢ Internet access from the Linux workstation
Deliverables:
➢ Using the rpm command and options to load fedora package modules. ➢ Completion of steps included in the Procedures below. ➢ Submittal of lab answer sheet to the instructor for grading.
The Red Hat Package Manager (RPM), recently renamed the Resource Package Manager (RPM), is an easy-to-use tool that automatically installs, updates, or removes Linux software packages. RPM is designed to work with source (un-compiled) or binary (pre-compiled) code placed in a package consisting of an application package name and release number. Packages always end in .rpm.
An example of the RPM naming convention is: dhcp-3.0.1-11.i386.rpm
The rpm name consists of a four-part naming convention. Each part is separated by either a dash or a period in the form of name-version-release.architecture_ type.rpm.
In the above rpm naming convention example, the package name, dhcp, is followed by a dash. The version number follows the package name. In the example the version number is 3.0.1 followed by a dash. The package’s release number is 11 (this is the 11th release for version 3.0.1) followed by a period. The subsequent name part, i386, identifies the hardware architectural type that the release is written to run on, and the last name part identifies the file as an rpm file.
Once an rpm package is loaded, it drops the architecture (i386) and rpm extension name parts.
The rpm database is found in /var/lib/rpm
The command for installing a
Resources Needed
➢ One classroom workstation, lab workstation, or home PC. ➢ One NETW-240 hard drive loaded with Fedora Linux or iLab access. ➢ Week 2 Lab 2 assignment with attached answer sheet. ➢ Internet access from the Linux workstation
Deliverables:
➢ Using the rpm command and options to load fedora package modules. ➢ Completion of steps included in the Procedures below. ➢ Submittal of lab answer sheet to the instructor for grading.
The Red Hat Package Manager (RPM), recently renamed the Resource Package Manager (RPM), is an easy-to-use tool that automatically installs, updates, or removes Linux software packages. RPM is designed to work with source (un-compiled) or binary (pre-compiled) code placed in a package consisting of an application package name and release number. Packages always end in .rpm.
An example of the RPM naming convention is: dhcp-3.0.1-11.i386.rpm
The rpm name consists of a four-part naming convention. Each part is separated by either a dash or a period in the form of name-version-release.architecture_ type.rpm.
In the above rpm naming convention example, the package name, dhcp, is followed by a dash. The version number follows the package name. In the example the version number is 3.0.1 followed by a dash. The package’s release number is 11 (this is the 11th release for version 3.0.1) followed by a period. The subsequent name part, i386, identifies the hardware architectural type that the release is written to run on, and the last name part identifies the file as an rpm file.
Once an rpm package is loaded, it drops the architecture (i386) and rpm extension name parts.
The rpm database is found in /var/lib/rpm
The command for installing a