DOCSLIB.ORG

Managing Software with Yum

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Managing Software with Yum Fedora Core 4 Managing software with yum Stuart Ellis Edited by Paul W. Frields Copyright © 2005 Red Hat, Inc. and others. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. The original authors of this document, and Red Hat, designate the Fedora Project as the "Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. For guidelines on the permitted uses of the Fedora trademarks, refer to https:// fedoraproject.org/wiki/Legal:Trademark_guidelines. Linux® is the registered trademark of Linus Torvalds in the United States and other countries. Java® is a registered trademark of Oracle and/or its affiliates. XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. All other trademarks are the property of their respective owners. 1. Introduction ............................................................................................................................. 2 1.1. Purpose ....................................................................................................................... 2 1.2. Audience ..................................................................................................................... 2 1.3. Using This Document ................................................................................................... 2 1.4. Additional Resources .................................................................................................... 3 1 Managing software with yum 2. Software Management Concepts ............................................................................................. 4 2.1. About Packages ........................................................................................................... 4 2.2. About Repositories ....................................................................................................... 4 2.3. About Dependencies .................................................................................................... 5 2.4. Understanding Package Names .................................................................................... 5 3. Software Management Tools in Fedora Core ............................................................................ 6 4. Managing Software with yum ................................................................................................... 7 4.1. Installing New Software with yum .................................................................................. 8 4.2. Updating Software with yum .......................................................................................... 9 4.3. Removing Software with yum ........................................................................................ 9 5. Searching for Packages with yum .......................................................................................... 10 5.1. Searching by Package Name and Attributes ................................................................ 10 5.2. Advanced Searches ................................................................................................... 10 5.3. Understanding Matches .............................................................................................. 11 6. Updating Your System with yum ............................................................................................. 11 6.1. Automatically Updating Your System ........................................................................... 12 7. Using Other Software Repositories ........................................................................................ 12 7.1. Adding a Repository as a Package Source .................................................................. 12 7.2. Manually Authorizing Package Sources ....................................................................... 13 7.3. Understanding Repository Compatibility ....................................................................... 13 8. Installing Software from an Isolated Package .......................................................................... 14 9. Maintaining yum .................................................................................................................... 15 9.1. Disabling or Removing Package Sources .................................................................... 15 9.2. Clearing the yum Caches ............................................................................................ 15 10. Using yum with a Proxy Server ............................................................................................ 15 10.1. Configuring Proxy Server Access .............................................................................. 16 10.2. Configuring Proxy Server Access for a Single User .................................................... 16 11. Acknowledgements .............................................................................................................. 17 Index 17 1. Introduction 1.1. Purpose This document presents basic concepts of software management on Fedora systems. It outlines the major functions of yum, the recommended software management tool for Fedora. 1.2. Audience This document is intended for Fedora users of all levels of experience. 1.3. Using This Document This document is a reference for using yum. You may wish to read some or all of the sections, depending upon your needs and level of experience. If you are a new user, read the Section 2, “Software Management Concepts” before using yum for the first time. Experienced Linux users should start with Section 4, “Managing Software with yum”. 2 Additional Resources Previous Versions of Fedora Core This document describes the configuration of yum on Fedora Core 4 systems. You must perform the additional step noted in Section 7.2, “Manually Authorizing Package Sources” to enable yum on Fedora Core 3. Most of the examples in this document use the package tsclient, which is included with Fedora Core. The tsclient package provides an application for remote desktop access. If you install it successfully you may start the application by choosing Applications → Internet → Terminal Server Client. To use the examples, substitute the name of the relevant package for tsclient. The example commands for Fedora package groups use the MySQL Database group. Avoid Logging in with the Root Account You do not need to log in with the root account in order to manage your Fedora system. All of the commands shown in this tutorial that require root access will prompt you for the root password. The example terminal commands use su -c to provide this facility. 1.4. Additional Resources The yum utility has features and options not discussed in this document. Read the man pages for yum(8) and yum.conf(5) to learn more, using the following commands: man yum man yum.conf Other useful yum resources on the Internet include: Project web site http://linux.duke.edu/projects/yum/ Users mailing list https://lists.dulug.duke.edu/mailman/listinfo/yum/ Development mailing list https://lists.dulug.duke.edu/pipermail/yum-devel/ Check Bugzilla First If you encounter a persistent error with a specific operation, visit http://bugzilla.redhat.com and review the bug reports for the package or packages involved. An error in a package may cause all yum operations that rely on that package to fail. Please file bug reports for Fedora packages, including yum, on this Bugzilla web site. 3 Managing software with yum 2. Software Management Concepts 2.1. About Packages Fedora software and documentation is supplied in the form of files called RPM packages. Each package is a compressed archive containing product information, program files, icons, documentation and management scripts. Management applications use these files to safely locate, install, update and remove software. For example, the Fedora installation process uses the packages supplied with Fedora Core to build or upgrade a system to your requirements. Packages also include a digital signature to prove their source. Software management utilities verify this digital signature by using a GPG public key. The yum and rpm utilities share a common keyring that stores all of the public keys for approved package sources. The system administrator configures these approved package sources. All Fedora Packages are Open Source Software All of the software provided by the Fedora Project is open source software. You may download and install Fedora packages on as many systems as desired. 2.2. About Repositories A repository is a prepared directory or web site that contains software packages and index files. Software management utilities such as yum automatically locate and obtain the correct RPM packages from these repositories. This method frees you from having to manually find and install new applications or updates. You may use a single command to update
Load more

Recommended publications
  • Red Hat Enterprise Linux 8 Installing, Managing, and Removing User-Space Components
    Red Hat Enterprise Linux 8 Installing, managing, and removing user-space components An introduction to AppStream and BaseOS in Red Hat Enterprise Linux 8 Last Updated: 2021-06-25 Red Hat Enterprise Linux 8 Installing, managing, and removing user-space components An introduction to AppStream and BaseOS in Red Hat Enterprise Linux 8 Legal Notice Copyright © 2021 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/ . In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
    [Show full text]
  • Using the Mysql Yum Repository Abstract
    Using the MySQL Yum Repository Abstract This document provides some basic instructions for using the MySQL Yum Repository to install and upgrade MySQL. It is excerpted from the MySQL 5.6 Reference Manual. For legal information, see the Legal Notices. For help with using MySQL, please visit the MySQL Forums, where you can discuss your issues with other MySQL users. Document generated on: 2021-09-23 (revision: 70881) Table of Contents Preface and Legal Notices ............................................................................................................ v 1 Installing MySQL on Linux Using the MySQL Yum Repository ..................................................... 1 2 Replacing a Third-Party Distribution of MySQL Using the MySQL Yum Repository ........................ 5 3 Upgrading MySQL with the MySQL Yum Repository ................................................................... 9 iii iv Preface and Legal Notices This document provides some basic instructions for using the MySQL Yum Repository to install and upgrade MySQL. It is excerpted from the MySQL 5.6 Reference Manual. Licensing information—MySQL 5.6. This product may include third-party software, used under license. If you are using a Commercial release of MySQL 5.6, see the MySQL 5.6 Commercial Release License Information User Manual for licensing information, including licensing information relating to third-party software that may be included in this Commercial release. If you are using a Community release of MySQL 5.6, see the MySQL 5.6 Community Release License Information User Manual for licensing information, including licensing information relating to third-party software that may be included in this Community release. Licensing information—MySQL NDB Cluster 7.3. This product may include third-party software, used under license. If you are using a Commercial release of NDB Cluster 7.3, see the MySQL NDB Cluster 7.3 Commercial Release License Information User Manual for licensing information relating to third-party software that may be included in this Commercial release.
    [Show full text]
  • Migrating-From-Rhn-Classic.Pdf
    Red Hat Subscription Management All Subscription Docs Migrating from RHN Classic to migrate from older Red Hat Network Classic (hosted) to updated subscription management Edition 4 Last Updated: 2018-05-01 Red Hat Subscription Management All Subscription Docs Migrating from RHN Classic to migrate from older Red Hat Network Classic (hosted) to updated subscription management Edition 4 Red Hat Subscription Management Documentation Team [email protected] Legal Notice Copyright © 2016 Red Hat, Inc. This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js ® is an official trademark of Joyent.
    [Show full text]
  • Red Hat Developer Toolset 9 User Guide
    Red Hat Developer Toolset 9 User Guide Installing and Using Red Hat Developer Toolset Last Updated: 2020-08-07 Red Hat Developer Toolset 9 User Guide Installing and Using Red Hat Developer Toolset Zuzana Zoubková Red Hat Customer Content Services Olga Tikhomirova Red Hat Customer Content Services [email protected] Supriya Takkhi Red Hat Customer Content Services Jaromír Hradílek Red Hat Customer Content Services Matt Newsome Red Hat Software Engineering Robert Krátký Red Hat Customer Content Services Vladimír Slávik Red Hat Customer Content Services Legal Notice Copyright © 2020 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/ . In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp.
    [Show full text]
  • Implementing Avaya Integrated Management Release 6.0
    Implementing Avaya Integrated Management Release 6.0 June 2010 Contents Chapter 1: Preface.....................................................................................................................5 Purpose.............................................................................................................................................................5 Support resources.............................................................................................................................................5 Avaya Professional Services....................................................................................................................6 Avaya Global Services Delivery...............................................................................................................7 Avaya Global Technical Services.............................................................................................................7 Customized management solutions for Avaya Integrated Management..................................................7 Contact information for Avaya support services.......................................................................................8 Related documentation.....................................................................................................................................8 Chapter 2: Application environment......................................................................................11 Integrated Management overview...................................................................................................................11
    [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]
  • Sudo Subscription-Manager Repos \ --Enable Rhel-7-Server-Rpms
    Buy the book on Amazon https://www.amazon.co.uk/dp/B08CF33XM2 50 yum repository details in /etc/yum.repos.d • Under /etc/yum.repos.d are the files which define the repositories to be used; for the CentOS 8 distribution these include: ♦ CentOS-Base.repo - contains the BaseOS repository details. ♦ CentOS-AppStream.repo - used to install AppStream packages from the distribution. • For our own in-house courses, the above repo files have been edited on the training systems so that the machine looks only to the training server vespa on the local network when installing or updating packages; this can be seen as follows: $ yum -v repolist • There should be three main repositories: Repo-id : AppStream-FA Repo-name : CentOS-8 - AppStream from FA server Repo-revision : 8.3.2011 Repo-distro-tags : [cpe:/o:centos:centos:8]: , 8, C, O, S, e, n, t Repo-updated : Tue 15 Dec 2020 03:05:32 PM GMT Repo-pkgs : 5,754 Repo-available-pkgs : 5,058 Repo-size : 6.9 G Repo-baseurl : http://192.168.200.41/centos/8/AppStream Repo-expire : 172,800 second(s) (last: Thu 31 Dec 2020 05:34:39 PM GMT) 50 of 617 First Alternative 2021 51 Repo-filename : /etc/yum.repos.d/CentOS-AppStream.repo Repo-id : BaseOS-FA Repo-name : CentOS-8 - Base on FA local http server Repo-revision : 8.3.2011 Repo-distro-tags : [cpe:/o:centos:centos:8]: , 8, C, O, S, e, n, t Repo-updated : Tue 15 Dec 2020 03:05:26 PM GMT Repo-pkgs : 1,697 Repo-available-pkgs : 1,695 Repo-size : 1.1 G Repo-baseurl : http://192.168.200.41/centos/8/BaseOS Repo-expire : 172,800 second(s) (last: Thu 31 Dec 2020 05:34:41
    [Show full text]
  • Foot Prints Feel the Freedom of Fedora!
    The Fedora Project: Foot Prints Feel The Freedom of Fedora! RRaahhuull SSuunnddaarraamm SSuunnddaarraamm@@ffeeddoorraapprroojjeecctt..oorrgg FFrreeee ((aass iinn ssppeeeecchh aanndd bbeeeerr)) AAddvviiccee 101011:: KKeeeepp iitt iinntteerraaccttiivvee!! Credit: Based on previous Fedora presentations from Red Hat and various community members. Using the age old wisdom and Indian, Free software tradition of standing on the shoulders of giants. Who the heck is Rahul? ( my favorite part of this presentation) ✔ Self elected Fedora project monkey and noisemaker ✔ Fedora Project Board Member ✔ Fedora Ambassadors steering committee member. ✔ Fedora Ambassador for India.. ✔ Editor for Fedora weekly reports. ✔ Fedora Websites, Documentation and Bug Triaging projects volunteer and miscellaneous few grunt work. Agenda ● Red Hat Linux to Fedora & RHEL - Why? ● What is Fedora ? ● What is the Fedora Project ? ● Who is behind the Fedora Project ? ● Primary Principles. ● What are the Fedora projects? ● Features, Future – Fedora Core 5 ... The beginning: Red Hat Linux 1994-2003 ● Released about every 6 months ● More stable “ .2” releases about every 18 months ● Rapid innovation ● Problems with retail channel sales model ● Impossible to support long-term ● Community Participation: ● Upstream Projects ● Beta Team / Bug Reporting The big split: Fedora and RHEL Red Hat had two separate, irreconcilable goals: ● To innovate rapidly. To provide stability for the long-term ● Red Hat Enterprise Linux (RHEL) ● Stable and supported for 7 years plus. A platform for 3rd party standardization ● Free as in speech ● Fedora Project / Fedora Core ● Rapid releases of Fedora Core, every 6 months ● Space to innovate. Fedora Core in the tradition of Red Hat Linux (“ FC1 == RHL10” ) Free as in speech, free as in beer, free as in community support ● Built and sponsored by Red Hat ● ...with increased community contributions.
    [Show full text]
  • Dell Update Packages Version 6.5 User's Guide
    Dell Update Packages Version 6.5 for Operating Systems User’s Guide Notes and Cautions NOTE: A NOTE indicates important information that helps you make better use of your computer. CAUTION: A CAUTION indicates potential damage to hardware or loss of data if instructions are not followed. ____________________ Information in this document is subject to change without notice. © 2012 Dell Inc. All rights reserved. Reproduction of these materials in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden. Trademarks used in this text: Dell™, the DELL™ logo, PowerEdge™ and Dell OpenManage™ are trademarks of Dell Inc. Microsoft®, XWindows® and Windows® are either trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries. Intel® is a registered trademark of Intel Corporation in the United States and other countries. Red Hat® and Red Hat Enterprise Linux® are registered trademarks of Red Hat, Inc. in the United States and other countries; SUSE™ is a trademark of Novell, Inc. in the United States and other countries. VMware® and ESX Server® are registered trademarks or trademarks of VMware, Inc. in the United States and/ or other jurisdictions. Citrix® and XenServer® are either trademarks or registered trademarks of Citrix Systems, Inc. in the United States and/or other countries. Other trademarks and trade names may be used in this document to refer to either the entities claiming the marks and names or their products. Dell Inc. disclaims any proprietary interest in trademarks and trade names other than its own. 2012-02 Contents 1 Getting Started With Dell Update Packages 7 Overview .
    [Show full text]
  • VNC Instruction for GNU/Linux
    VNC Instruction for GNU/Linux 1. Install “ TigerVNC Viewer ”. You can get it with package manager command line as below: • On Ubuntu / Mint / Debian sudo apt-get install vncviewer • On Fedora / CentOS / Scientific Linux sudo yum install tigervnc • On Arch Linux sudo pacman -Syy tigervnc 2. Open “Terminal”, and ssh to “csevnc.cse.csusb.edu” using the following command: ssh -L 5900:localhost:5900 <YourCoyoteID>@csevnc.cse.csusb.edu (Note: Replace “<YourCoyoteID>” with your Coyote ID) 3. If this is the first time you remote access to this server, you may see the following information. When you see that, just type “yes” and hit “Enter”. 4. Type in your Coyote password and hit Enter. 5. Open TigerVNC Viewer. Here are 2 ways to open it: ● From Application: Click on the icon shown in the applications list. ● From command line: Keep the current terminal tab from Step 2 open, and open a new tab or a new terminal window. Then, run command vncviewer in the new tab or window. CSUSB School of CSE 01/19/2018 hn 6. In the pop-up window, type in “localhost”, then hit Enter (or click on “Connect” ). (The pop-up window may vary depending on the distribution of Linux system) 7. Now you should see the GUI of the remote computer. Login with your Coyote ID as Username and Coyote password as Password. 8. Once you have done your work, close the VNC viewer window, and run command exit in the terminal tab from Step 2 to log out from the remote server. CSUSB School of CSE 01/19/2018 hn.
    [Show full text]
  • Noprianto Instalasi Pprogramrogram
    UTAMA Noprianto Instalasi PProgramrogram eiring dengan semakin banyaknya Linux digunakan, teknologi Syang memudahkan instalasi program di Linux ddii LLinuxinux pun bertambah. Kita akan membahasnya di tulisan ini. Suatu sistem yang solid adalah impian contoh, di sistem berbasis RPM, kita me- sendiri-sendiri. Selain karena alasan tidak semua pengguna komputer. Baik pengguna ngenal program yang dipaketkan sebagai ingin adanya redundansi yang tidak diper- komputer di server besar sampai perangkat fi le dengan ekstensi rpm yang dapat diin- lukan, juga karena kemungkinan terjadinya genggam. Permasalahannya adalah sistem stal. Atau, di sistem berbasis DPKG, kita inkompatibilitas versi pustaka. operasi yang telah terinstal tidak dapat mengenal program yang dipaketkan sebagai Oleh karena itu, sebuah paket barangkali memenuhi kebutuhan semua pengguna. fi le dengan ekstensi .deb. Dan masih banyak akan membutuhkan paket lainnya. Dan, pa- Baik saat pertama penggunaan ataupun di lagi. ket tersebut juga mungkin dibutuhkan oleh waktu yang akan datang. Oleh karena itu, Khususnya di Linux, masalah instalasi paket lainnya. Beberapa package manage- sistem operasi modern mengizinkan insta- program menjadi sangat istimewa karena ment modern sudah mengatasi masalah lasi aplikasi tambahan, baik yang berjalan adanya keinginan untuk mengumpulkan dependency ini, namun sempat menjadi isu sepenuhnya di user space ataupun yang me- semua pustaka di satu atau beberapa tem- yang sangat rumit di beberapa waktu yang nyentuh kernel space. pat yang disepakati bersama. Demikian lalu ataupun di beberapa sistem saat ini. Instalasi program dapat dilakukan juga dengan lokasi executable program. Di Kebutuhan akan versi pustaka yang ber- dengan berbagai cara. Di sistem operasi Linux, kita tidak disarankan untuk menggu- beda-beda juga bisa menjadi masalah besar.
    [Show full text]
  • Dell System Update Version 1.0 Preview Guide Notes, Cautions, and Warnings
    Dell System Update Version 1.0 Preview Guide Notes, Cautions, and Warnings NOTE: A NOTE indicates important information that helps you make better use of your computer. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. Copyright © 2015 Dell Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. Dell™ and the Dell logo are trademarks of Dell Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies. 2015–01 Rev. A00 Contents 1 Overview.................................................................................................................4 Transitioning from DLR to DSU............................................................................................................ 4 Other documents you might need................................................................................................. 5 2 Prerequisites for installing the Dell System Update.......................................6 Supported hardware and operating system.........................................................................................6 Supported hardware........................................................................................................................6 Supported operating system...........................................................................................................6
    [Show full text]