DOCSLIB.ORG

Opensuse Leap 15.3 Start-Up Start-Up Opensuse Leap 15.3

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Opensuse Leap 15.3 Start-Up Start-Up Opensuse Leap 15.3 openSUSE Leap 15.3 Start-Up Start-Up openSUSE Leap 15.3 Publication Date: June 22, 2021 SUSE LLC 1800 South Novell Place Provo, UT 84606 USA https://documentation.suse.com Copyright © 2006– 2021 SUSE LLC and contributors. All rights reserved. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or (at your option) version 1.3; with the Invariant Section being this copyright notice and license. A copy of the license version 1.2 is included in the section entitled “GNU Free Documentation License”. For SUSE trademarks, see https://www.suse.com/company/legal/ . All other third-party trademarks are the property of their respective owners. Trademark symbols (®, ™ etc.) denote trademarks of SUSE and its aliates. Asterisks (*) denote third-party trademarks. All information found in this book has been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. Neither SUSE LLC, its aliates, the authors nor the translators shall be held liable for possible errors or the consequences thereof. Contents About this guide xi 1 Available documentation xi 2 Improving the documentation xii 3 Documentation conventions xiii 4 Source code xiv 5 Acknowledgments xiv I INSTALLATION 1 1 Installation Quick Start 2 1.1 Welcome to openSUSE Leap 2 Minimum system requirements 2 • Installing openSUSE Leap 2 2 Boot parameters 17 2.1 Using the default boot parameters 17 2.2 PC (AMD64/Intel 64/Arm AArch64) 17 The boot screen on machines equipped with traditional BIOS 18 • The boot screen on machines equipped with UEFI 20 2.3 List of important boot parameters 23 General boot parameters 23 • Configuring the network interface 24 • Specifying the installation source 26 • Specifying remote access 27 2.4 Advanced setups 27 Using IPv6 for the installation 27 • Using a proxy for the installation 28 • Enabling SELinux support 29 • Enabling the installer self-update 29 • Scale user interface for high DPI 29 • Using CPU mitigations 29 iii Start-Up 2.5 More information 30 3 Installation steps 31 3.1 Overview 31 3.2 Installer self-update 32 Self-update process 33 • Custom self-update repositories 35 3.3 Language, keyboard, and license agreement 36 3.4 Network settings 37 3.5 Online repositories 38 3.6 System role 40 3.7 Partitioning 43 Important information 43 • Suggested partitioning 45 3.8 Clock and time zone 47 3.9 Create new user 49 3.10 Authentication for the system administrator root 52 3.11 Installation settings 54 Software 54 • Booting 56 • Security 56 • Network configuration 57 • Default systemd target 57 • Import SSH host keys and configuration 58 • System 58 3.12 Performing the installation 59 4 Troubleshooting 60 4.1 Checking media 60 4.2 No bootable drive available 60 4.3 Booting from installation media fails 61 4.4 Boot failure 62 4.5 Fails to launch graphical installer 64 4.6 Only minimalist boot screen started 65 iv Start-Up II ADMINISTRATION 67 5 Managing users with YaST 68 5.1 User and group administration dialog 68 5.2 Managing user accounts 70 5.3 Additional options for user accounts 71 Automatic login and passwordless login 72 • Enforcing password policies 72 • Managing quotas 73 5.4 Changing default settings for local users 75 5.5 Assigning users to groups 76 5.6 Managing groups 76 5.7 Changing the user authentication method 77 5.8 Default system users 79 6 Changing language and country settings with YaST 81 6.1 Changing the system language 81 Modifying system languages with YaST 82 • Switching the default system language 84 • Switching languages for standard X and GNOME applications 85 6.2 Changing the country and time settings 85 7 Setting up hardware components with YaST 89 7.1 Setting up your system keyboard layout 89 7.2 Setting up sound cards 89 7.3 Setting up a printer 93 Configuring printers 93 • Configuring printing via the network with YaST 96 • Sharing printers over the network 98 7.4 Setting up a scanner 99 Configuring an HP all-in-one device 99 • Sharing a scanner over the network 100 • Scanning over the network 100 v Start-Up 8 Printer operation 101 8.1 The CUPS workflow 102 8.2 Methods and protocols for connecting printers 103 8.3 Installing the software 103 8.4 Network printers 104 8.5 Configuring CUPS with command line tools 105 8.6 Printing from the command line 106 8.7 Special features in openSUSE Leap 107 CUPS and firewall 107 • Browsing for network printers 107 • PPD files in various packages 108 8.8 Troubleshooting 109 Printers without standard printer language support 109 • No suitable PPD file available for a PostScript printer 110 • Network printer connections 110 • Defective printouts without error message 112 • Disabled queues 112 • CUPS browsing: deleting print jobs 113 • Defective print jobs and data transfer errors 113 • Debugging CUPS 114 • More information 114 9 Accessing file systems with FUSE 115 9.1 Configuring FUSE 115 9.2 Mounting an NTFS partition 115 9.3 Mounting remote file system with SSHFS 116 9.4 Mounting an ISO file system 116 9.5 Available FUSE plug-ins 117 9.6 More information 118 III MANAGING AND UPDATING SOFTWARE 119 10 Installing or removing software 120 10.1 Definition of terms 120 vi Start-Up 10.2 Using the YaST software manager 122 Searching software 122 • Installing and removing packages or patterns 123 • Updating packages 125 • Package dependencies 127 • Handling of package recommendations 128 10.3 Managing software repositories and services 129 Adding software repositories 129 • Managing repository properties 131 • Managing repository keys 132 10.4 The GNOME package updater 132 10.5 Updating packages with GNOME Software 135 11 Installing add-on products 137 11.1 Add-ons 137 11.2 Binary drivers 138 12 YaST online update 139 12.1 The online update dialog 139 12.2 Installing patches 141 12.3 Automatic online update 142 13 Upgrading the system and system changes 145 13.1 Upgrading the system 145 Preparations 146 • Possible problems 146 • Upgrading with YaST 147 • Distribution upgrade with Zypper 154 • Updating individual packages 157 13.2 More information 157 IV THE BASH SHELL 159 14 Shell basics 160 14.1 Starting a shell 160 vii Start-Up 14.2 Entering commands 161 Using commands without options 162 • Using commands with options 162 • Bash shortcut keys 164 14.3 Getting help 164 14.4 Working with files and directories 165 Examples for working with files and directories 167 14.5 Becoming root 170 Using su 170 • Using sudo 170 14.6 File access permissions 171 Permissions for user, group and others 171 • Files and folders 173 • Modifying file permissions 174 14.7 Time-saving features of Bash 176 Examples for using history, completion and wildcards 178 14.8 Editing texts 180 Example: editing with vi 181 14.9 Searching for files or contents 181 Examples for searching 182 14.10 Viewing text files 182 14.11 Redirection and pipes 183 Examples for redirection and pipe 184 14.12 Starting programs and handling processes 185 14.13 Archives and data compression 186 14.14 Important Linux commands 188 File commands 188 • System commands 194 • More information 197 15 Bash and Bash scripts 198 15.1 What is “the shell”? 198 Bash configuration files 198 • The directory structure 201 15.2 Writing shell scripts 205 viii Start-Up 15.3 Redirecting command events 206 15.4 Using aliases 207 15.5 Using variables in Bash 208 Using argument variables 209 • Using variable substitution 209 15.6 Grouping and combining commands 210 15.7 Working with common flow constructs 211 The if control command 211 • Creating loops with the for command 212 15.8 More information 212 V HELP AND TROUBLESHOOTING 213 16 Help and documentation 214 16.1 Documentation directory 214 SUSE manuals 215 • Package documentation 215 16.2 Man pages 216 16.3 Info pages 217 16.4 Online resources 218 17 Common problems and their solutions 219 17.1 Finding and gathering information 219 17.2 Boot problems 222 The GRUB 2 boot loader fails to load 222 • No login or prompt appears 223 • No graphical login 224 • Root Btrfs partition cannot be mounted 224 • Force checking root partitions 224 • Disable swap to enable booting 225 • GRUB 2 fails during reboot on a dual-boot system 225 17.3 Login problems 225 Valid user name and password combinations fail 225 • Valid user name and password not accepted 226 • Login to encrypted home partition fails 229 • GNOME desktop has issues 229 ix Start-Up 17.4 Network problems 230 NetworkManager problems 234 17.5 Data problems 235 Managing partition images 235 • Using the rescue system 235 A GNU licenses 243 x Start-Up About this guide This manual will see you through your initial contact with openSUSE® Leap. Learn how to install, use and enjoy your system. Installation Guides you through the installation process and the basic conguration of your system. The Quick Start section shows a quick walk through the installation using default values. The second part of this chapter provides details for every installation step. Administration Introduces YaST, the central tool for installation and conguration of your system. Learn how to initially set up your system and how to modify key components of your system. Managing and updating software Understand how to install or remove software with either YaST or using the command line, how to use the 1-Click Install feature, and how to keep your system up-to-date. The Bash shell Learn how to work with the bash shell, the default command line interpreter on openSUSE Leap.
Load more

Recommended publications
  • Current Status of OFED in SUSE Linux Enterprise Server
    Current Status of OFED in SUSE Linux Enterprise Server John Jolly Senior Software Engineer SUSE Agenda 2 λAbout SUSE λAbout SUSE Linux Enterprise Server λOFED Integration into SLES λFuture Direction of OFED in SLES SUSE and the Attachmate Group λSUSE , headquartered in Nürnberg / Germany, λis an independently operating business unit of λThe Attachmate Group, Inc. λThe Attachmate Group is a privately held λ1 billion+ $ revenue software company λwith four brands: •Cloud Infrastructure •Enterprise Computing •Integrated Systems SUSE® Linux Enterprise How We Build It Online Repository Source Package Image OBS OBS user submits source to OBS and gets a product SUSE® Linux Enterprise Server 12 Lifecyle Model •13-year lifecycle (10 years general support, 3 years extended support) •5-year lifecycle per Service Pack (2 years general + 3 years extended support) •Long Term Service Pack Support (LTSS) available for all versions, including GA http://www.suse.com/lifecycle/ Unique Tools Included λAppArmor Security Framework -Application confinement λFree High Availability Extension -Cluster Framework, Cluster FS, DRBD, GEO-cluster* λYaST2 systems management -Install, deploy, and configure every aspect of the server λSubscription Management Tool -Subscription and patch management, proxy/mirroring/staging λStarter System for System z -A pre-built installation server, deployable with z/VM tools Features of SLES 12 λLinux Kernel 3.12 λOnly 64-bit kernel -Support of 32-bit application through execution environment λYaST modules written in Ruby λOFED 3.12 -Significant
    [Show full text]
  • Monitoring Glacial Advance and Retreat of the Skaftafellsjökull Glacier, Iceland
    Monitoring Glacial Advance and Retreat of the Skaftafellsjökull Glacier, Iceland Bryce L. Carmichael Amber E. Smith Elizabeth City State University North Carolina Central University Abstract- Visual documentation of glaciers can provide package gPhoto2 was installed to the Linux board daily, seasonal, and yearly statistics concerning their [www.gphoto.org]. Next, we wrote a set of custom scripts advance and retreat, as well as contribute to historical that ran periodically to capture photographs and archive them. record. Recognizing how glaciers change will improve glacier models, which leads to a better understanding of An all-weather case for the camera had to be climate and ice-sheet interactions. Obtaining frequent constructed in order to provide the device with protection and images of glaciers can be difficult since they are often power when out in the field. The picture feedback was located in remote locations with rugged terrain and harsh required to have protection also, so silica packs were placed in weather conditions. Access can be arduous even during the case to prevent moisture build-up on the camera lens. warm weather months. To overcome this obstacle, we propose building an autonomous imaging device that is II. BACKGROUND powered by solar panels and can withstand the harsh weather. The imaging device will have the ability to The Center for Remote Sensing of Ice Sheets capture images of the glacier at specified times, store them (CReSIS) Science and Technology Center was established by for uploading, and send them over a radio link to an the National Science Foundation (NSF) in 2005. The Internet access point.
    [Show full text]
  • Suse Linux Enterprise Server 12 - Administration Guide Pdf, Epub, Ebook
    SUSE LINUX ENTERPRISE SERVER 12 - ADMINISTRATION GUIDE PDF, EPUB, EBOOK Admin Guide Contributors | 630 pages | 28 Apr 2016 | Samurai Media Limited | 9789888406500 | English | none SUSE Linux Enterprise Server 12 - Administration Guide PDF Book To prevent the conflicts, before starting the migration, execute the following as a super user:. PA, IA In todays service oriented IT zero downtime becomes more and more a most wanted feature. If you want to change actions for single packages, right-click a package in the package view and choose an action. When debugging a problem, you sometimes need to temporarily install a lot of -debuginfo packages which give you more information about running processes. If you are only reading the release notes of the current release, you could miss important changes. However, this can be changed through macro configuration. In this case, the oldest zswap pages are written back to disk-based swap. YaST snapshots are labeled as zypp y2base in the Description column ; Zypper snapshots are labeled zypp zypper. Global variables, or environment variables, can be accessed in all shells. If it is 0 zero the command was successful, everything else marks an error which is specific to the command. The installation medium must be inserted in the HMC. Maintaining netgroup data. This option fetches changes in repositories, but keeps the disabled repositories in the same state—disabled. The rollback snapshots are therefore automatically deleted when the set number of snapshots is reached. The visible physical entity, as it is typically mounted to a motherboard or an equivalent. When using the self-signed certificate, you need to confirm its signature before the first connection.
    [Show full text]
  • Mysql and Linux/Unix Abstract
    MySQL and Linux/Unix Abstract This is the MySQL Linux extract 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 Unix/Linux Using Generic Binaries ............................................................... 1 2 Installing MySQL on Linux ......................................................................................................... 5 2.1 Installing MySQL on Linux Using the MySQL Yum Repository ........................................... 6 2.2 Replacing a Third-Party Distribution of MySQL Using the MySQL Yum Repository .............. 9 2.3 Installing MySQL on Linux Using the MySQL APT Repository ......................................... 11 2.4 Installing MySQL on Linux Using the MySQL SLES Repository ....................................... 11 2.5 Installing MySQL on Linux Using RPM Packages from Oracle ......................................... 12 2.6 Installing MySQL on Linux Using Debian Packages from Oracle ...................................... 15 2.7 Installing MySQL on Linux from the Native Software Repositories .................................... 16 2.8 Deploying MySQL on Linux with Docker .......................................................................
    [Show full text]
  • Best Practices and Getting Started Guide for Oracle on IBM Linuxone
    Front cover Best practices and Getting Started Guide for Oracle on IBM LinuxONE Susan Adamovich Sam Amsavelu Srujan Jagarlamudi Raghu Malige Michael Morgan Paul Novak David J Simpson Redpaper International Technical Support Organization Best practices and Getting Started Guide for Oracle on IBM LinuxONE June 2020 REDP-5499-00 Note: Before using this information and the product it supports, read the information in “Notices” on page vii. First Edition (June 2020) This edition applies to Oracle 12c, Release 2. This document was created or updated on June 2, 2020. © Copyright International Business Machines Corporation 2020. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . vii Trademarks . viii Preface . 1 Authors. 1 Now you can become a published author, too! . 2 Comments welcome. 3 Stay connected to IBM Redbooks . 3 Chapter 1. Running Linux virtual servers under IBM z/VM . 5 1.1 z/VM fundamentals . 6 1.2 Pre-requisites and assumptions . 6 1.2.1 Pre-requisites . 6 1.2.2 Assumptions . 6 1.3 Configuring a workstation for mainframe access . 7 1.3.1 3270 emulators . 7 1.3.2 Virtual Network Computing client . 7 1.3.3 Connecting from a Linux workstation . 8 1.3.4 Connecting from a MacOS workstation. 8 1.3.5 Connecting from a Windows workstation . 9 1.4 Service validation and notice subscription . 10 1.4.1 RSU validation . 10 1.4.2 Subscribing to service notifications. 10 1.5 Tailoring z/VM for Linux workloads .
    [Show full text]
  • 1. D-Bus a D-Bus FAQ Szerint D-Bus Egy Interprocessz-Kommunikációs Protokoll, És Annak Referenciamegvalósítása
    Az Udev / D-Bus rendszer - a modern asztali Linuxok alapja A D-Bus rendszer minden modern Linux disztribúcióban jelen van, sőt mára már a Linux, és más UNIX jellegű, sőt nem UNIX rendszerek (különösen a desktopon futó változatok) egyik legalapvetőbb technológiája, és az ismerete a rendszergazdák számára lehetővé tesz néhány rendkívül hasznos trükköt, az alkalmazásfejlesztőknek pedig egyszerűen KÖTELEZŐ ismerniük. Miért ilyen fontos a D-Bus? Mit csinál? D-Bus alapú technológiát teszik lehetővé többek között azt, hogy közönséges felhasználóként a kedvenc asztali környezetünkbe bejelentkezve olyan feladatokat hajtsunk végre, amiket a kernel csak a root felasználónak engedne meg. Felmountolunk egy USB meghajtót? NetworkManagerrel konfiguráljuk a WiFi-t, a 3G internetet vagy bármilyen más hálózati csatolót, és kapcsolódunk egy hálózathoz? Figyelmeztetést kapunk a rendszertől, hogy új szoftverfrissítések érkeztek, majd telepítjük ezeket? Hibernáljuk, felfüggesztjük a gépet? A legtöbb esetben ma már D-Bus alapú technológiát használunk ilyen esetben. A D-Bus lehetővé teszi, hogy egymástól függetlenül, jellemzően más UID alatt indított szoftverösszetevők szabványos és biztonságos módon igénybe vegyék egymás szolgáltatásait. Ha valaha lesz a Linuxhoz professzionális desktop tűzfal vagy vírusirtó megoldás, a dolgok jelenlegi állasa szerint annak is D- Bus technológiát kell használnia. A D-Bus technológia legfontosabb ihletője a KDE DCOP rendszere volt, és mára a D-Bus leváltotta a DCOP-ot, csakúgy, mint a Gnome Bonobo technológiáját. 1. D-Bus A D-Bus FAQ szerint D-Bus egy interprocessz-kommunikációs protokoll, és annak referenciamegvalósítása. Ezen referenciamegvalósítás egyik összetevője, a libdbus könyvtár a D- Bus szabványnak megfelelő kommunikáció megvalósítását segíti. Egy másik összetevő, a dbus- daemon a D-Bus üzenetek routolásáért, szórásáért felelős.
    [Show full text]
  • SUSE® Linux Enterprise Server ("SLES ™")11 SP1 Novell® Software License Agreement
    SUSE® Linux Enterprise Server ("SLES ™")11 SP1 Novell® Software License Agreement PLEASE READ THIS AGREEMENT CAREFULLY. BY INSTALLING OR OTHERWISE USING THE SOFTWARE (INCLUDING ITS COMPONENTS), YOU AGREE TO THE TERMS OF THIS AGREEMENT. IF YOU DO NOT AGREE WITH THESE TERMS, DO NOT DOWNLOAD, INSTALL OR USE THE SOFTWARE. RIGHTS AND LICENSES This Novell Software License Agreement (“Agreement”) is a legal agreement between You (an entity or a person) and Novell, Inc. (“Novell”). The software product identified in the title of this Agreement, any media and accompanying documentation (collectively the “Software”) is protected by the copyright laws and treaties of the United States (“U.S.”) and other countries and is subject to the terms of this Agreement. Any update or support release to the Software that You may download or receive that is not accompanied by a license agreement expressly superseding this Agreement is Software and governed by this Agreement. If the Software is an update or support release, then You must have validly licensed the version and quantity of the Software being updated or supported in order to install or use the update or support release. The Software is a modular operating system comprised of numerous components that may be accompanied by separate license terms. The Software is a collective work of Novell; although Novell does not own the copyright to every component of the Software, Novell owns the collective work copyright for the Software. Most of the components are open source packages, developed independently, and accompanied by separate license terms. Your license rights with respect to individual components accompanied by separate license terms are defined by those terms; nothing in this agreement shall restrict, limit, or otherwise affect any rights or obligations You may have, or conditions to which You may be subject, under such license terms; however, if You distribute copies of any component independent of the Software, You must remove all Novell trademarks, trade dress, and logos from each copy.
    [Show full text]
  • A U T O M at E D I N S Ta L L At
    Proceedings of LISA '99: 13th Systems Administration Conference Seattle, Washington, USA, November 7–12, 1999 A U T O M AT E D I N S TA L L AT I O N O F L I N U X S Y S T E M S U S I N G YA S T Dirk Hohndel and Fabian Herschel THE ADVANCED COMPUTING SYSTEMS ASSOCIATION © 1999 by The USENIX Association All Rights Reserved For more information about the USENIX Association: Phone: 1 510 528 8649 FAX: 1 510 548 5738 Email: [email protected] WWW: http://www.usenix.org Rights to individual papers remain with the author or the author's employer. Permission is granted for noncommercial reproduction of the work for educational or research purposes. This copyright notice must be included in the reproduced paper. USENIX acknowledges all trademarks herein. Automated Installation of Linux Systems Using YaST Dirk Hohndel and Fabian Herschel – SuSE Rhein/Main AG ABSTRACT The paper describes how to allow a customized automated installation of Linux. This is possible via CDRom, network or tape, using a special boot disk that describes the system that should be set up and either standard SuSE Linux CDs, customized install CDs, an appropriately configured installation server, or a tape backup of an existing machine. A control file on the boot disk and additional (optional) control files on the install medium specify which settings should be used and which packages should be installed. This includes settings like language, key table, network setup, hard disk partitioning, packages to install, etc. After giving a quick overview of the syntax and capabilities of this installation method, considerations about how to plan the automated installation at larger sites are presented.
    [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]
  • Chapter 7 Package Management
    Chapter 7 Package Management CERTIFICATION OBJECTIVES 7.01 The Red Hat Package Manager ✓ Two-Minute Drill 7.02 More RPM Commands Q&A Self Test 7.03 Dependencies and the yum Command 7.04 More Package Management Tools fter installation is complete, systems are secured, filesystems are configured, and other initial setup tasks are completed, you still have work to do. Almost certainly before your system is in the state you desire, you will be required to install or remove packages. To make sure the right updates are installed, you need to know how to get a system working with ARed Hat Subscription Management (RHSM) or the repository associated with a rebuild distribution. To accomplish these tasks, you need to understand how to use the rpm and yum commands in detail. Although these are “just” two commands, they are rich in detail. Entire books have been dedicated to the rpm command, such as the Red Hat RPM Guide by Eric 344 Chapter 7 Package Management Foster-Johnson. For many, that degree of in-depth knowledge of the rpm command is no longer necessary, given the capabilities of the yum command and the additional package management tools provided in RHEL 7. CERTIFICATION OBJECTIVE 7.01 The Red Hat Package Manager One of the major duties of a system administrator is software management. New applications are installed. Services are updated. Kernels are patched. Without the right tools, it can be difficult to figure out what software is on a system, what is the latest update, and what applications depend on other software.
    [Show full text]
  • SUSE Linux Enterprise Server 11 SP4 System Analysis and Tuning Guide System Analysis and Tuning Guide SUSE Linux Enterprise Server 11 SP4
    SUSE Linux Enterprise Server 11 SP4 System Analysis and Tuning Guide System Analysis and Tuning Guide SUSE Linux Enterprise Server 11 SP4 Publication Date: September 24, 2021 SUSE LLC 1800 South Novell Place Provo, UT 84606 USA https://documentation.suse.com Copyright © 2006– 2021 SUSE LLC and contributors. All rights reserved. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or (at your option) version 1.3; with the Invariant Section being this copyright notice and license. A copy of the license version 1.2 is included in the section entitled “GNU Free Documentation License”. For SUSE trademarks, see http://www.suse.com/company/legal/ . All other third party trademarks are the property of their respective owners. A trademark symbol (®, ™ etc.) denotes a SUSE or Novell trademark; an asterisk (*) denotes a third party trademark. All information found in this book has been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. Neither SUSE LLC, its aliates, the authors nor the translators shall be held liable for possible errors or the consequences thereof. Contents About This Guide xi 1 Available Documentation xii 2 Feedback xiv 3 Documentation Conventions xv I BASICS 1 1 General Notes on System Tuning 2 1.1 Be Sure What Problem to Solve 2 1.2 Rule Out Common Problems 3 1.3 Finding the Bottleneck 3 1.4 Step-by-step Tuning 4 II SYSTEM MONITORING 5 2 System Monitoring Utilities 6 2.1 Multi-Purpose Tools 6 vmstat 7
    [Show full text]
  • Automatic Dependency Management for Scientific Applications on Clusters
    Automatic Dependency Management for Scientific Applications on Clusters Ben Tovar, Nicholas Hazekamp, Nathaniel Kremer-Herman, and Douglas Thain btovar,nhazekam,nkremerh,dthain @nd.edu { } Department of Computer Science and Engineering University of Notre Dame Abstract—Software installation remains a challenge in scien- are unprivileged, and multiple incompatible versions may need tific computing. End users require custom software stacks that to exist simultaneously. are not provided through commodity channels. The resulting To address this problem, we present VC3-Builder, a user- effort needed to install software delays research in the first place, and creates friction for moving applications to new resources level system for managing software dependencies across mul- and new users. Ideally, end-users should be able to manage their tiple clusters. VC3-Builder shares some elements of design own software stacks without requiring administrator privileges. with recent systems such as Nix [8] and Spack [10], but it To that end, we describe VC3-Builder, a tool for deploying is more suited for rapid deployment by exploiting pre-existing software environments automatically on clusters. Its primary software where available and using the resources of the cluster application comes in cloud and opportunistic computing, where deployment must be performed in batch as a side effect of job itself to perform parallel and distributed builds. execution. VC3-Builder uses workflow technologies as a means We demonstrate VC3-Builder by several case studies of of exploiting cluster resources for building in a portable way. We complex applications that present a challenge for users to build demonstrate the use of VC3-Builder on three applications with and deploy manually: the MAKER bioinformatics pipeline, the complex dependencies: MAKER, Octave, and CVMFS, building CVMFS distributed filesystem, and the Octave mathematics and running on three different cluster facilities in sequential, parallel, and distributed modes.
    [Show full text]