DOCSLIB.ORG

Installing Red Hat Enterprise Linux 5.0

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Installing Red Hat Enterprise Linux 5.0 Avaya Integrated Management Release 5.2 System Management Installation and Upgrade Issue 5 May 2009 © 2009 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information in this document was complete and accurate at the time of printing, Avaya Inc. can assume no liability for any errors. Changes and corrections to the information in this document may be incorporated in future releases. For full legal page information, please see the complete document, Avaya Legal Page for Software Documentation, Document number 03-600758. To locate this document on the website, simply go to http://www.avaya.com/support and search for the document number in the search box. Documentation disclaimer Avaya Inc. is not responsible for any modifications, additions, or deletions to the original published version of this documentation unless such modifications, additions, or deletions were performed by Avaya. Customer and/or End User agree to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation to the extent made by the Customer or End User. Link disclaimer Avaya Inc. is not responsible for the contents or reliability of any linked Web sites referenced elsewhere within this documentation, and Avaya does not necessarily endorse the products, services, or information described or offered within them. We cannot guarantee that these links will work all of the time and we have no control over the availability of the linked pages. Warranty Avaya Inc. provides a limited warranty on this product. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya’s standard warranty language, as well as information regarding support for this product, while under warranty, is available through the following Web site: http://www.avaya.com/support Copyright Except where expressly stated otherwise, the Product is protected by copyright and other laws respecting proprietary rights. Unauthorized reproduction, transfer, and or use can be a criminal, as well as a civil, offense under the applicable law. Avaya support Avaya provides a telephone number for you to use to report problems or to ask questions about your product. The support telephone number is 1-800-242-2121 in the United States. For additional support telephone numbers, see the Avaya Web site: http://www.avaya.com/support Contents Chapter 1: Introduction . 5 Purpose. 5 Prerequisites . 5 Intended audience . 5 Conventions used in this book . 6 Support resources. 6 Avaya Technology and Consulting . 6 Avaya Professional Services . 6 Avaya Global Services Delivery . 8 Avaya Global Technical Services. 8 Customized management solutions for Avaya Integrated Management. 8 Avaya contact information . 9 Product documentation . 9 How to access books on the Web . 9 Chapter 2: Overview . 11 System Management . 11 New SM installation and upgrade features. 11 System Management CD . 11 Preinstallation tasks . 12 Chapter 3: System Management Installation . 13 Overview . 13 Linux server requirements . 13 Client PC requirements . 14 Verifying the current Red Hat Linux version . 15 Configuring the /etc/hosts file . 15 Configuring the openLDAP server . 16 Installating an SM application in a customer specified directory . 16 Generating a random password for the SM administrator user . 16 Using the randomly generated password . 17 System Management upgrade installations . 18 Upgrading multiple Linux servers . 19 Installing the software in console mode . 20 Upgrading to Release 5.2 . 21 Installing Release 5.2 . 27 Auditing the Fault and Performance Manager database . 32 Configuring the Integrated Management Database . 32 Issue 5 May 2009 3 Contents Backing up System Management. 33 Backing up data using the GUI utility . 33 Scheduling backups using the GUI utility . 34 Cancelling scheduled backups using the GUI utility . 36 Backing up data using the Command Line method . 36 Restoring System Management . 37 Restoring data using the GUI utility . 37 Restoring data using the Command Line method. 38 up2date or YUM support for Red Hat Linux platforms . 39 Issue . 39 Resolution . 39 Uninstalling System Management . 40 Allowing Avaya Services remote access. 41 Configuring the Integrated Management server . 42 Changing an application link on the Avaya Integrated Management Launch Page . 42 Changing security settings . 43 Appendix A: Linux server installation . 45 Overview . 45 Installing Red Hat Enterprise Linux 5.0 . 45 Installing RHEL in the text mode . 49 Upgrading Red Hat Enterprise Linux ES 4.0 or AS 4.0 to Red Hat Enterprise Linux 5.0 . 50 Using kickstart for Red Hat Enterprise Linux installations . 51 Selecting an installation method . 51 CD-ROM . 51 HTTP . 52 Diskette . 52 Initiating a kickstart installation . 52 Starting a kickstart installation . 53 Verifying installation of required RPM files . 53 Installing required RPM files . 54 RPM files installed by System Management R5.2 . 55 Warning for unsupported versions of third-party RPMs . 55 Security considerations . 56 Index . 57 4 Avaya Integrated Management System Management Installation and Upgrade Chapter 1: Introduction Purpose This book provides the following information: l Hardware and software requirements for Linux servers. l Preinstallation tasks to be completed before installation. l Procedure to install System Management products on the Linux server. Prerequisites System administrators who install the System Management software should be experienced in installing software on Linux operating systems in a converged network environment. Intended audience This guide is meant for the use of system administrators who are responsible for installing software on Linux servers. May 2009 5 Introduction Conventions used in this book The following typographical conventions are used: l Bold type is used to indicate selections from menus, buttons in a window, and the Enter key on the keyboard. It is also used for emphasis. l Courier bold font is used to indicate commands that you type. l Courier bold italic font is used to indicate variable information within the commands that you type. l Courier font is used to indicate information that appears as command results, or ouput. l Arrows indicate options that you select from cascading menus; for example, Click File > Open means click the Open option from the File menu. Support resources Avaya provides many planning, consulting, and technical services. The following sections describe the resources and services that are available to Avaya customers. Avaya Technology and Consulting Avaya Technology and Consulting (ATAC) works with client teams to develop detailed solutions for connectivity to Avaya Communication Manager solutions. ATAC also designs network configurations. Due to configuration complexities, we strongly recommend that you contract for professional implementation services for the following Avaya Integrated Management products: l Avaya MultiSite Administration l Avaya Fault and Performance Manager Avaya Professional Services The Avaya Professional Services (APS) team of Avaya Integrated Management (AIM) consultants offers customers the following services: l Platform readiness verification l AIM architectural planning, design, and overview 6 Avaya Integrated Management System Management Installation and Upgrade Avaya Professional Services l Remote turnkey implementation and installation l AIM server configuration l Customer acceptance verification l Custom on-site services l On-site and remote knowledge transfer The APS Data Group consists of the following teams: l Avaya Integrated Management Consultants The Avaya Integrated Management (AIM) consulting team offers planning, design, implementation, consulting, and knowledge transfer services for the entire Avaya Integrated Management suite. This includes ASA, Val Manager, VMM, NMC with SUM, MSA, and FPM. The thrust of the APS team is to bring the correct methodology to these complex application deployments that span various regions, and to provide continuity to the overall project. Through proper integration and consulting, our customers can leverage the AIM suite to lower the total cost of ownership, and proactively manage their VoIP network comfortably and confidently. l Data Network Implementation Engineering The Data Network Implementation Engineering (formerly RNIS) team implements and upgrades or upgrades, existing or new data networks. This team analyzes the network design requirements and performance expectations of the customer. The team then creates the hardware and software installation specification used to implement data devices that include Cajun, VPN, Wireless LAN, Secure Gateways, Extreme, Juniper, and multivendor data equipment. The APS Data Group provides support on a contract basis. Contact your local Avaya Account Team or Business Partner to purchase any implementation offer from the team. For more information, see Table 1: Customer-Accessible Resources on page 9, or contact Jon Machak at 248-213-3788 or [email protected] May 2009 7 Introduction Avaya Global Services Delivery Avaya Global Services Delivery (GSD) provides support to the Avaya Integrated Management client teams, field technicians, and customers. GSD will bill customers for support on a time and materials basis if the following conditions exist: l Customers do not provide remote access. l Customers do not have a current maintenance agreement.
Load more

Recommended publications
  • Creating Rpms Guide
    CREATING RPMS (Student version) v1.0 Featuring 36 pages of lecture and a 48 page lab exercise This docu m e n t serves two purpose s: 1. Representative sample to allow evaluation of our courseware manuals 2. Make available high quality RPM documentation to Linux administrators A bout this m aterial : The blue background you see simulates the custom paper that all Guru Labs course w are is printed on. This student version does not contain the instructor notes and teaching tips present in the instructor version. For more information on all the features of our unique layout, see: http://ww w . g urulabs.co m /courseware/course w are_layout.php For more freely available Guru Labs content (and the latest version of this file), see: http://www.gurulabs.co m/goodies/ This sample validated on: Red Hat Enterprise Linux 4 & Fedora Core v3 SUSE Linux Enterprise Server 9 & SUSE Linux Professional 9.2 About Guru Labs: Guru Labs is a Linux training company started in 199 9 by Linux experts to produce the best Linux training and course w are available. For a complete list, visit our website at: http://www.gurulabs.co m/ This work is copyrighted Guru Labs, L.C. 2005 and is licensed under the Creative Common s Attribution- NonCom mer cial- NoDerivs License. To view a copy of this license, visit http://creativecom m o n s.org/licenses/by- nc- nd/2.0/ or send a letter to Creative Commons, 559 Nathan Abbott Way, Stanford, California 943 0 5, USA. Guru Labs 801 N 500 W Ste 202 Bountiful, UT 84010 Ph: 801-298-5227 WWW.GURULABS.COM Objectives: • Understand
    [Show full text]
  • CIT 470: Advanced Network and System Administration Slide #1 CIT 470: Advanced Network and System Administration Slide #2
    Topics 1. The Problem of Software Installation 2. Package Management Systems CIT 470: Advanced Network and 3. Using RPM System Administration 4. Finding RPMs Package Management 5. Building RPMs CIT 470: Advanced Network and System Administration Slide #1 CIT 470: Advanced Network and System Administration Slide #2 Software Installation What’s the problem? 1. Customization What prerequisites does your software have? Select options like language. What prereqs do your prereq packages have? Select file set. How do you handle conflicts? What if two programs install/modify same file? 2. Install new files in appropriate locations. Does your install work on every type of computer? 3. Modify existing configuration files. How do you handle upgrades? 4. Make software available to user. What if user has customized configuration? Shell configuration (PATH, etc.) What if ownerships/permissions have changed? GUI configuration (menu, icons, etc.) What if user needs old and new versions? How do you uninstall software? CIT 470: Advanced Network and System Administration Slide #3 CIT 470: Advanced Network and System Administration Slide #4 Package Manager Features UNIX Package Management Systems • Build management. deb: Debian system uses dpkg and APT. • Dependency tracking. pkgadd: Solaris packaging system. • Querying. portage: Gentoo uses with emerge. • Reversibility. ports: BSD ports system. • Verification. RPM: Redhat packaging system. • Version control. tgz: Tarballs used by Slackware. CIT 470: Advanced Network and System Administration Slide #5 CIT 470: Advanced Network and System Administration Slide #6 1 RPM RPM Package Names RPM Package Manager <name>-<version>-<release>.<arch>.rpm – Originally stood for Red Hat Package Manager – Came with Red Hat Linux 2.0 in 1995.
    [Show full text]
  • Kernel Module Packages Manual for SUSE Linux Enterprise 12 SP2 Or Later and SUSE Linux Enterprise 15
    SUSE Best Practices Kernel Module Packages Manual for SUSE Linux Enterprise 12 SP2 or later and SUSE Linux Enterprise 15 SUSE Linux Enterprise 12 SP2+, 15 Document Owner: Ann Davis, Senior Software Engineer, SUSE Kernel Module Packages Manual for SUSE Linux Enterprise 12 SP2 or later and SUSE Linux 1 Enterprise 15 SUSE-based distributions use the RPM Package Manager for software management. As such, any external kernel modules (these are kernel modules not included in SUSE kernel packages) should be packaged in RPM packages. These RPMs should be built in accordance with specic guidelines to ensure that the resulting Kernel Module Packages (KMPs) can be installed and updated appropriately, in synchronization with kernel updates. This document species the requirements for RPM packages that contain kernel modules, and describes the processes surrounding those packages including building, signing, installing and upgrading. A complete example is given and explained. This version of the Kernel Module Packages Manual applies to SUSE Linux Enterprise Server 12 (Service Pack 2 and later), and SUSE Linux Enterprise Server 15, and all products based on these versions. Publication Date: July 31, 2019 Contents 1 Scope 4 2 Background 4 3 Kernel Packages 6 4 Kernel Modules 7 5 Kernel Module Packages 8 6 RPM Provides and Requires 12 7 Building Kernel Module Packages 12 8 Signing 14 9 Deploying Kernel Module Packages 18 10 System Installation and Kernel Module Packages 18 Kernel Module Packages Manual for SUSE Linux Enterprise 12 SP2 or later and SUSE
    [Show full text]
  • Forcepoint DLP Supported File Formats and Size Limits
    Forcepoint DLP Supported File Formats and Size Limits Supported File Formats and Size Limits | Forcepoint DLP | v8.8.1 This article provides a list of the file formats that can be analyzed by Forcepoint DLP, file formats from which content and meta data can be extracted, and the file size limits for network, endpoint, and discovery functions. See: ● Supported File Formats ● File Size Limits © 2021 Forcepoint LLC Supported File Formats Supported File Formats and Size Limits | Forcepoint DLP | v8.8.1 The following tables lists the file formats supported by Forcepoint DLP. File formats are in alphabetical order by format group. ● Archive For mats, page 3 ● Backup Formats, page 7 ● Business Intelligence (BI) and Analysis Formats, page 8 ● Computer-Aided Design Formats, page 9 ● Cryptography Formats, page 12 ● Database Formats, page 14 ● Desktop publishing formats, page 16 ● eBook/Audio book formats, page 17 ● Executable formats, page 18 ● Font formats, page 20 ● Graphics formats - general, page 21 ● Graphics formats - vector graphics, page 26 ● Library formats, page 29 ● Log formats, page 30 ● Mail formats, page 31 ● Multimedia formats, page 32 ● Object formats, page 37 ● Presentation formats, page 38 ● Project management formats, page 40 ● Spreadsheet formats, page 41 ● Text and markup formats, page 43 ● Word processing formats, page 45 ● Miscellaneous formats, page 53 Supported file formats are added and updated frequently. Key to support tables Symbol Description Y The format is supported N The format is not supported P Partial metadata
    [Show full text]
  • Linux Package Management
    Welcome A Basic Overview and Introduction to Linux Package Management By Stan Reichardt [email protected] October 2009 Disclaimer ● ...like a locomotive ● Many (similar but different) ● Fast moving ● Complex parts ● Another one coming any minute ● I have ridden locomotives ● I am NOT a locomotive engineer 2 Begin The Train Wreck 3 Definitions ● A file archiver is a computer program that combines a number of files together into one archive file, or a series of archive files, for easier transportation or storage. ● Metadata is data (or information) about other data (or information). 4 File Archivers Front Ends Base Package Tool CLI GUI tar .tar, tar tar file roller .tar.gz, .tgz, .tar.Z, .taz, .tar.bz2,.tbz2, .tbz, .tb2, .tar.lzma,.tlz, .tar.xz, .txz, .tz zip .zip zip zip file roller gzip gzip gunzip gunzip ● Archive file http://en.wikipedia.org/wiki/Archive_file ● Comparison of file archivers http://en.wikipedia.org/wiki/Comparison_of_file_archivers 5 tar ● These files end with .tar suffix. ● Compressed tar files end with “.t” variations: .tar.gz, .tgz, .tar.Z, .taz, .tar.bz2, .tbz2, .tbz, .tb2, .tar.lzma, .tlz, .tar.xz, .txz, .tz ● Originally intended for transferring files to and from tape, it is still used on disk-based storage to combine files before they are compressed. ● tar (file format) http://en.wikipedia.org/wiki/.tar 6 tarball ● A tar file or compressed tar file is commonly referred to as a tarball. ● The "tarball" format combines tar archives with a file-based compression scheme (usually gzip). ● Commonly used for source and binary distribution on Unix-like platforms, widely available elsewhere.
    [Show full text]
  • Package Management Security
    Package Management Security Justin Cappos, Justin Samuel, Scott Baker, John H. Hartman University of Arizona Computer Science Department {justin, jsamuel, bakers, jhh}@cs.arizona.edu Abstract Package management is the task of determining which packages should be installed on a host and then downloading and installing those packages. This paper examines the popular package managers APT and YUM and presents nine feasible attacks on them. There are attacks that install malicious packages, deny users package updates, or cause the host to crash. This work identifies three rules of package management security: don’t trust the repository, the trusted entity with the most information should be the one who signs, and don’t install untrusted packages. The violation of these rules leads to the described vulnerabilities. Unfortunately, many of the flaws are architectural in nature, so repair requires more than patches to APT and YUM. While the rules of package management security argue that the design of existing package managers is insufficient, they do not prescribe how to provide security. This led to the development of three de- sign principles for building a secure package manager: selective trust delegation, customized repository views, and explicitly treating the repository as untrusted. These principles were used to construct a pack- age manager Stork which is not vulnerable to the attacks identified for YUM and APT. Stork has been in use for four years and has managed over half a million clients. 1 Introduction Package managers are a popular way to distribute software (bundled into archives called packages) for modern operating systems [4, 11, 37].
    [Show full text]
  • Fedora 13 Alpha Arrives Ami
    Fedora 13 alpha arrives amid controversy http://www.desktoplinux.com/news/NS8716234495.html Home | News | Articles | Forum | Polls | Blogs | Videos | Resource Library Keywords: Match: Fedora 13 alpha arrives amid controversy Got a HOT tip? please tell us! Mar. 12, 2010 ADVERTISEMENT (Advertise here) The Fedora project has released an alpha version of Fedora 13 featuring automatic print-driver installation, the Btrfs filesystem, Resource Library enhanced 3D driver support, and much more. Meanwhile, on LWN.net, Jonathan Corbet reports on the growing controversy in the Fedora community over the quantity and quality of updates. This techie-focused Fedora is known as a cutting-edge, community-driven upstream contributor to Red Hat Enterprise Linux (RHEL). Expected to ship in final form in Popular recent stories: Visit the... • Linux an equal Flash player May, Fedora 13 follows the final release of Fedora 12 in November. Fedora 12 • Linux, netbooks threaten Microsoft's fat profits added speed optimizations for i686 CPUs and the Intel Atom, and enhanced • gOS 3.0 goes gold support for IPv6, Bluetooth, virtualization, multimedia, and power management • Browser swallows OS • Lenovo denies ditching Linux features. Fedora 12 also added support for the netbook-oriented Moblin desktop • Lightweight, Linux-compatible browser evolves environment, in the form of a Fedora 12 Moblin Fedora Remix edition. • GNOME 2.24 gains "Empathy" IM • Review: Pardus Linux • Ubuntu to fund Linux development Plug and play printing -- yea! • Ubuntu "Intrepid Ibex" available From the end-user perspective, one of the most noticeable improvements to Fedora All-time Classics: • Choosing a desktop Linux distro 13 is automatic print driver installation.
    [Show full text]
  • RPM Packages
    RPM Packaging Guide Adam Miller, Maxim Svistunov, Marie Doleželová, et al. Table of Contents Introduction. 1 PDF Version . 1 Document Conventions. 1 Contributing to this guide . 2 Prerequisites . 3 Why Package Software with RPM?. 4 Your First RPM Package . 5 Preparing Software for Packaging . 7 What is Source Code? . 7 How Programs Are Made . 8 Natively Compiled Code . 8 Interpreted Code . 8 Building Software from Source . 9 Natively Compiled Code . 9 Interpreted Code . 10 Patching Software . 12 Installing Arbitrary Artifacts. 14 Using the install command . 14 Using the make install command . 15 Preparing Source Code for Packaging. 16 Putting Source Code into Tarball . 16 bello . 17 pello . 17 cello. 18 Packaging Software . 20 RPM Packages . 20 What is an RPM? . 20 RPM Packaging Tools . 20 RPM Packaging Workspace . 21 What is a SPEC File? . 21 BuildRoots . 23 RPM Macros . 24 Working with SPEC files. 25 Building RPMS . 44 Source RPMs . 45 Binary RPMS . 45 Checking RPMs For Sanity . 47 Checking the bello SPEC File. 47 Checking the bello Binary RPM . 48 Checking the pello SPEC File. 48 Checking the pello Binary RPM . 49 Checking the cello SPEC File . 50 Checking the cello Binary RPM . 51 Advanced Topics. 52 Signing Packages . 52 Adding a Signature to a Package . 52 Replacing a Package Signature. 53 Build-time Signing. 54 Mock . 55 Version Control Systems. 59 tito . ..
    [Show full text]
  • 07 RPM, Boot Loaders, and Kickstart
    Certification RPM, Boot Loaders, and Kickstart UNIT 7 RPM, Boot Loaders, and Kickstart 1 Rev RH133-9.0-1 Copyright © 2003 Red Hat, Inc. UNIT 7: Objectives Upon completion of this unit the student should be able to: · Use RPM to install, remove, update, and query packages · Describe how to configure a multi-boot system · Configure the GRUB and LILO boot loaders · Configure Kickstart and perform automated installations 2 Rev RH133-9.0-1 Copyright © 2003 Red Hat, Inc. UNIT 7: Agenda · Using RPM · Installing Red Hat Linux on a multi-boot system · Configuring a boot loader · Deploying an installation server · Installation using Kickstart 3 Rev RH133-9.0-1 Copyright © 2003 Red Hat, Inc. The RPM Way ? Package installation is never interactive ? Applies to all sw (core OS and add-ons) ? No such thing as a patch to a package 4 Rev RH133-9.0-1 Copyright © 2003 Red Hat, Inc. RPM Package Manager · RPM Components · local database · rpm and related executables · package files · rpmfind and metadirectories · Primary Functions · install/remove · query · verify · build 5 Rev RH133-9.0-1 Copyright © 2003 Red Hat, Inc. Installing and Removing Software · Installing and Removing Software · Install: rpm -i, --install · Upgrade: rpm -U, --upgrade · Freshen: rpm -F, --freshen · Erase: rpm -e, --erase · Common Options · Output options: -v, -h · Preconditions: --nodeps, --replacefiles, --force · Relocating: --excludepath, --prefix, --relocate, --badreloc, --root · URL support: ftp (with globbing), http 6 Rev RH133-9.0-1 Copyright © 2003 Red Hat, Inc. Updating a Kernel RPM ? Make sure to install kernel updates ? Do not use rpm -U ! – rpm -ivh kernel-version.arch.rpm – Boot new kernel to test – Revert to old kernel if a problem arises – rpm -e kernel-oldversion if no problems 7 Rev RH133-9.0-1 Copyright © 2003 Red Hat, Inc.
    [Show full text]
  • PUID Název Verze Přípona MIMETYPE Kategorie Výstupní
    PUID Název Verze Přípona MIMETYPE Kategorie Výstupní formát Výstupní formát alternativně I Výstupní formát alternativně II Originál vždy (doporučeno) Komentář x-fmt/1 Microsoft Word for Macintosh Document 3.0 mcw application/msword Word Processing § 23 odst. 2 fmt/100 Hypertext Markup Language 4.01 htm,html text/html Text (Mark-up) § 23 odst. 2 ano x-fmt/59 AutoCAD Last Saved Layer State las CAD ponechat x-fmt/2 Microsoft Word for Macintosh Document 6.0 Word Processing § 23 odst. 2 fmt/262 Microsoft Works Spreadsheet for DOS 3 Spreadsheet § 23 odst. 2 § 23 odst. 6 ano x-fmt/3 Online Description Tool Format odt Text (Structured) § 23 odst. 2 fmt/263 Microsoft Works Spreadsheet for DOS 3a Spreadsheet § 23 odst. 2 § 23 odst. 6 ano x-fmt/4 Write for Windows Document 3.1 wri Word Processing § 23 odst. 2 fmt/264 Microsoft Works Spreadsheet for DOS 3b Spreadsheet § 23 odst. 2 § 23 odst. 6 ano x-fmt/5 Works for Macintosh Document 4.0 Word Processing § 23 odst. 2 fmt/265 Microsoft Works Word Processor DOS 3 Word Processing § 23 odst. 2 x-fmt/6 FoxPro Database 2.0 dbf Database § 23 odst. 6 individuální posouzení archivem Pokud je součástí Shapefile, použít reprezentaci ve VDF (§ 23 odst. 2, 3) společně pro celý model. fmt/266 Microsoft Works Word Processor DOS 3a Word Processing § 23 odst. 2 x-fmt/7 FoxPro Database 2.5 dbf Database § 23 odst. 6 individuální posouzení archivem Pokud je součástí Shapefile, použít reprezentaci ve VDF (§ 23 odst. 2, 3) společně pro celý model.
    [Show full text]
  • Package Management Yum and Rpm
    Package Management yum and rpm Presented by Prabin Kumar Datta 4th Year 8th Semester, IT, GCECT Copyright (C) 2011 prabindatta GNU General Public License http://www.gnu.org/licenses/ PackageKit PackageKit, the default package manager front-end on Fedora PackageKit Front-ends: There are three front-ends for PackageKit: gnome-packagekit to be used in the GNOME desktop. kpackagekit to be used in the KDE desktop. pkcon to be used on the command line. PackageKit Back-ends There are number of back-ends for PackageKit. Few of them are: YUM Opkg Simple Package Manager Advanced Packaging Tool Yellowdog Updater Modified Yellowdog Updater Modified (YUM) is an open- source command-line package-management utility for RPM-compatible Linux operating systems Yum is System administration commands (usually only for root) RPM Package Manager RPM stand for Redhat Package Manager. Features of RPM include: RPM packages can be cryptographically verified with GPG and MD5 Original source archive(s) (e.g. .tar.gz, .tar.bz2) are included in SRPMs, making verification easier PatchRPMs, the RPM equivalent of a patch file, can incrementally update RPM-installed software Automatic build-time dependency evaluation. Few Commands Install packages: # rpm -ivh <package_name> The above command has inability to resolve dependencies. # yum install <package_name> The yum application can call upon several repositories for dependency resolution. Few Commands Install packages: (continue) # yum localinstall <rpmfile> This command will install the local rpm file and also search for
    [Show full text]
  • Packages Used by Major Linux Distributions
    Packages used by major linux distributions Michael Kluge June 25, 2013 Michael Kluge Packages used by major linux distributions June 25, 2013 1 / 24 Meaning of different box colors /path/to/some/file Content of the file or just parts of it. Shell commands Can be executed on the shell. Green box definition Definitions or examples. Michael Kluge Packages used by major linux distributions June 25, 2013 2 / 24 Introduction Introduction Michael Kluge Packages used by major linux distributions June 25, 2013 3 / 24 Introduction What is a package? Opensuse package definition Packages are archives of files that include all the files making up a piece of software and, eventually, instructions on the way to make them work. http://en.opensuse.org/Package_management Debian FAQ definition Packages generally contain all of the files necessary to implement a set of related commands or features. http://www.debian.org/doc/manuals/debian-faq/ch-pkg_basics.en.html Michael Kluge Packages used by major linux distributions June 25, 2013 4 / 24 Introduction How to install a package without a package manager? I tarball is an gziped tar archive (tar.gz file) I normally contains source code and a makefile I but content is not standardized and may be different I common method before package management systems emerged unpack, configure, compile & install tar -xzf node-v10.12.tar.gz cd node-v10.12 ./configure make make install Michael Kluge Packages used by major linux distributions June 25, 2013 5 / 24 Introduction Pros & cons + source code can be modified by user + can be used
    [Show full text]