DOCSLIB.ORG

Deployment Guide Deployment Guide SUSE Linux Enterprise Server 15

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Deployment Guide Deployment Guide SUSE Linux Enterprise Server 15 SUSE Linux Enterprise Server 15 Deployment Guide Deployment Guide SUSE Linux Enterprise Server 15 This guide details how to install single or multiple systems, and how to exploit the product-inherent capabilities for a deployment infrastructure. Choose from various approaches: local installation from physical installation media, customizing the standard installation images, network installation server, mass deployment using a remote-controlled, highly-customized, automated installation process, and initial system conguration. 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 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 xiii 1 Available Documentation xiii 2 Giving Feedback xv 3 Documentation Conventions xvi 4 Product Life Cycle and Support xviii Support Statement for SUSE Linux Enterprise Server xviii • Technology Previews xix I INSTALLATION PREPARATION 1 1 Planning for SUSE Linux Enterprise Server 2 1.1 Considerations for Deployment of a SUSE Linux Enterprise Server 2 1.2 Deployment of SUSE Linux Enterprise Server 3 1.3 Running SUSE Linux Enterprise Server 3 1.4 Registering SUSE Linux Enterprise Server 4 1.5 Changes in Installation from SUSE Linux Enterprise Server Version 15 4 Unified Installer for SUSE Linux Enterprise-based Products 4 • Installing with Internet Access 5 • Offline Installation 5 2 Installation on AMD64 and Intel 64 6 2.1 Hardware Requirements 6 2.2 Installation Considerations 7 Installation on Hardware or Virtual Machine 8 • Installation Target 8 2.3 Controlling the Installation 8 2.4 Booting the Installation System 9 iii Deployment Guide 2.5 Dealing with Boot and Installation Problems 11 Problems Booting 11 • Problems Installing 12 • Redirecting the Boot Source to the Boot DVD 12 3 Installation on Arm AArch64 13 3.1 Hardware Requirements 13 3.2 Installation Considerations 15 Installation on Hardware or Virtual Machine 15 • Installation Target 15 3.3 Controlling the Installation 15 3.4 Booting the Installation System 16 3.5 Dealing with Boot and Installation Problems 18 Problems Booting 18 • Problems Installing 19 • Redirecting the Boot Source to the Boot DVD 19 4 Installation on IBM POWER 20 4.1 Hardware Requirements 20 4.2 Preparation 21 Installation in a Partition Using IVM 22 • Installation on Servers with no Open Power Abstraction Layer 25 4.3 For More Information 26 5 Installation on IBM Z 28 5.1 System Requirements 28 Hardware 28 • MicroCode Level, APARs, and Fixes 31 • Software 31 5.2 General Information 32 System requirements 32 • Installation Types 36 • IPL Options 37 5.3 Preparing for Installation 38 Making the Installation Data Available 38 • Installation Types 45 • Preparing the IPL of the SUSE Linux Enterprise Server Installation System 47 • IPLing the SUSE Linux Enterprise Server Installation System 50 • Network Configuration 55 • Connecting to the SUSE Linux iv Deployment Guide Enterprise Server Installation System 59 • The SUSE Linux Enterprise Server Boot Procedure on IBM Z 61 5.4 The Parmfile—Automating the System Configuration 62 5.5 Example Parmfiles 62 5.6 Using the vt220 Terminal Emulator 63 5.7 Further In-Depth Information about IBM Z 64 General Documents about Linux on IBM Z 64 • Technical Issues of Linux on IBM Z 64 • Advanced Configurations for Linux on IBM Z 65 6 Installation on Hardware Not Supported at Release 66 6.1 Download Kernel Update 66 6.2 Boot Kernel Update 66 II INSTALLATION PROCEDURE 67 7 Boot Parameters 68 7.1 Using the Default Boot Parameters 68 7.2 PC (AMD64/Intel 64/Arm AArch64) 69 The Boot Screen on Machines Equipped with Traditional BIOS 69 • The Boot Screen on Machines Equipped with UEFI 71 7.3 List of Important Boot Parameters 74 General Boot Parameters 74 • Configuring the Network Interface 75 • Specifying the Installation Source 77 • Specifying Remote Access 77 7.4 Advanced Setups 78 Providing Data to Access an RMT Server 78 • Configuring an Alternative Data Server for supportconfig 80 • Using IPv6 for the Installation 80 • Using a Proxy for the Installation 80 • Enabling SELinux Support 81 • Enabling the Installer Self-Update 81 • Scale User Interface for High DPI 82 v Deployment Guide 7.5 IBM Z 82 7.6 More Information 84 8 Installation Steps 85 8.1 Overview 85 8.2 Installer Self-Update 86 Self-Update Process 87 • Custom Self-Update Repositories 89 8.3 Language, Keyboard, and Product Selection 90 8.4 License Agreement 91 8.5 IBM Z: Disk Activation 92 Configuring DASD Disks 93 • Configuring zFCP Disks 94 8.6 Network Settings 94 8.7 Registration 96 Registering Manually 96 • Loading Registration Codes from USB Storage 98 • Installing without Registration 99 8.8 Extension and Module Selection 101 Selecting Extensions and Modules with Registration 102 • Selecting Extensions and Modules without Registration 105 8.9 Add-On Product 109 8.10 System Role 111 8.11 Partitioning 112 Important Information 112 • Suggested Partitioning 114 8.12 Clock and Time Zone 116 8.13 Create New User 118 8.14 Password for the System Administrator 121 vi Deployment Guide 8.15 Installation Settings 122 Software 123 • Booting 125 • Firewall and SSH 125 • Kdump 126 • IBM Z: Blacklist Devices 126 • Default systemd Target 127 • Import SSH Host Keys and Configuration 127 • System 127 8.16 Performing the Installation 128 IBM Z: IPLing the Installed System 129 • IBM Z: Connecting to the Installed System 130 9 Registering SUSE Linux Enterprise and Managing Modules/Extensions 132 9.1 Registering During the Installation 133 9.2 Registering during Automated Deployment 133 9.3 Registering from the Installed System 133 Registering with YaST 133 • Registering with SUSEConnect 136 9.4 Managing Modules and Extensions in a Running System 137 Adding Modules and Extensions with YaST 137 • Deleting Modules and Extensions with YaST 138 • Adding/Deleting Modules and Extensions with SUSEConnect 139 10 Expert Partitioner 142 10.1 Using the Expert Partitioner 142 Partition Tables 144 • Partitions 145 • Editing a Partition 149 • Expert Options 151 • Advanced Options 151 • More Partitioning Tips 152 • Partitioning and LVM 154 10.2 LVM Configuration 155 Create Physical Volume 155 • Creating Volume Groups 155 • Configuring Logical Volumes 156 10.3 Soft RAID 158 Soft RAID Configuration 158 • Troubleshooting 160 • For More Information 160 vii Deployment Guide 11 Remote Installation 161 11.1 Overview 161 11.2 Scenarios for Remote Installation 162 Installation from DVD via VNC 162 • Installation from Network via VNC 163 • Installation from DVD via SSH 164 • Installation from Network via SSH 165 11.3 Monitoring Installation via VNC 166 Preparing for VNC Installation 166 • Connecting to the Installation Program 167 11.4 Monitoring Installation via SSH 168 Preparing for SSH Installation 168 • Connecting to the Installation Program 168 11.5 Monitoring Installation via Serial Console 169 12 Troubleshooting 170 12.1 Checking Media 170 12.2 No Bootable DVD Drive Available 170 12.3 Booting from Installation Media Fails 171 12.4 Boot Failure 172 12.5 Fails to Launch Graphical Installer 174 12.6 Only Minimalist Boot Screen Started 176 12.7 Log Files 176 III CUSTOMIZING INSTALLATION IMAGES 177 13 Cloning Disk Images 178 13.1 Overview 178 13.2 Cleaning Up Unique System Identifiers 178 viii Deployment Guide 14 Customizing Installation Images with mksusecd 180 14.1 Installing mksusecd 180 14.2 Creating a Minimal Boot Image 181 14.3 Set Default Kernel Boot Parameters 181 14.4 Customize Modules, Extensions, and Repositories 182 14.5 Creating a Minimal Netinstall ISO 183 14.6 Change Default Repository 183 15 Customizing Installation Images Manually 184 IV SETTING UP AN INSTALLATION SERVER 185 16 Setting Up a Network Installation Source 186 16.1 Setting Up an Installation Server Using YaST 186 16.2 Setting Up an NFS Repository Manually 188 16.3 Setting Up an FTP Repository Manually 190 16.4 Setting Up an HTTP Repository Manually 192 16.5 Managing an SMB Repository 193 16.6 Using ISO Images of the Installation Media on the Server 194 17 Preparing Network Boot Environment 195 17.1 Setting Up a DHCP Server 195 Dynamic Address Assignment 196 • Assigning Static IP Addresses 197 • PXE and AutoYaST Installation Failures 197 17.2 Setting Up a TFTP Server 198 Installing a TFTP Server 198 • Installing Files for Boot 199 • Configuring PXELINUX 200 • Preparing PXE Boot for EFI with GRUB2 200 17.3 PXELINUX Configuration Options 201 17.4 Preparing the Target System for PXE Boot 203 ix Deployment Guide 17.5 Using Wake-on-LAN for Remote Wakeups 204 Prerequisites 204 • Verifying Wired Ethernet Support 204 • Verifying Wireless Interface Support 205 • Installing and Testing
Load more

Recommended publications
  • Linux on POWER
    http://ibmsystemsmag.com/CMSTemplates/IBMSystemsMag/Print.aspx?... close window Print May 2016 | by Jaqui Lynch IBM is serious about Linux on POWER. Linux now runs on every POWER8 server, with specialized offerings for Linux. These include the new LC (Linux only, PowerKVM only) servers, the L model (Linux only) servers, Linux IFLs, EasyScale for MSP offerings, and SAP Hana on POWER. Additionally, significant work has been done to encourage ISVs to increase their offerings on Linux on POWER, resulting in a flourishing ecosystem that wasn’t available on POWER five years ago. Power systems are designed for big data and optimized for performance and scalability. They provide great I/O and memory bandwidth with significant reliability and other availability features not available anywhere else except the mainframe. With full support for various levels of RHEL (Redhat Enterprise Linux), SLES (SuSE Linux Enterprise Server) and Ubuntu, it’s a great time to consider migrating to Linux on Power. Here are some decisions to make: 1. Do you want to run Linux alongside other workloads like AIX or IBM i 2. Do you want to run a Linux only server 3. Do you want to use and HMC or virtual HMC to control the server (won’t work with PowerKVM) 4. Do you want to use PowerKVM or PowerVM for virtualization 5. Do you have some dark cores and memory that you would like to run Linux on at a reduced rate 6. Do you have x86 workload running on Linux that you would like to migrate 7. Do you want to reduce costs for IBM software (PVU based licensing) Reducing costs Software can be expensive, especially middleware.
    [Show full text]
  • Linux: IBM Electronic Service Agent for Powerlinux User's Guide Chapter 1
    Linux Version 4.5.5 IBM Electronic Service Agent for PowerLinux User's Guide IBM Note Before using this information and the product it supports, read the information in “Notices” on page 123 . Nineteenth Edition (August 2020) © Copyright International Business Machines Corporation 2020. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents About this document..............................................................................................v Highlighting...................................................................................................................................................v Case-sensitivity in Linux...............................................................................................................................v ISO 9000.......................................................................................................................................................v Chapter 1. IBM Electronic Service Agent................................................................ 1 What's new...................................................................................................................................................1 Overview.......................................................................................................................................................7 Accessing the IBM Electronic Support portal........................................................................................7
    [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]
  • POWER® Processor-Based Systems
    IBM® Power® Systems RAS Introduction to IBM® Power® Reliability, Availability, and Serviceability for POWER9® processor-based systems using IBM PowerVM™ With Updates covering the latest 4+ Socket Power10 processor-based systems IBM Systems Group Daniel Henderson, Irving Baysah Trademarks, Copyrights, Notices and Acknowledgements Trademarks IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. These and other IBM trademarked terms are marked on their first occurrence in this information with the appropriate symbol (® or ™), indicating US registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at http://www.ibm.com/legal/copytrade.shtml The following terms are trademarks of the International Business Machines Corporation in the United States, other countries, or both: Active AIX® POWER® POWER Power Power Systems Memory™ Hypervisor™ Systems™ Software™ Power® POWER POWER7 POWER8™ POWER® PowerLinux™ 7® +™ POWER® PowerHA® POWER6 ® PowerVM System System PowerVC™ POWER Power Architecture™ ® x® z® Hypervisor™ Additional Trademarks may be identified in the body of this document. Other company, product, or service names may be trademarks or service marks of others. Notices The last page of this document contains copyright information, important notices, and other information. Acknowledgements While this whitepaper has two principal authors/editors it is the culmination of the work of a number of different subject matter experts within IBM who contributed ideas, detailed technical information, and the occasional photograph and section of description.
    [Show full text]
  • IBM Powervm Virtualization Introduction and Configuration
    Front cover IBM PowerVM Virtualization Introduction and Configuration Understand PowerVM features and capabilities Plan, implement, and set up PowerVM virtualization Updated to include new POWER7 technologies Mel Cordero Lúcio Correia Hai Lin Vamshikrishna Thatikonda Rodrigo Xavier ibm.com/redbooks International Technical Support Organization IBM PowerVM Virtualization Introduction and Configuration June 2013 SG24-7940-05 Note: Before using this information and the product it supports, read the information in “Notices” on page xxi. Sixth Edition (June 2013) This edition applies to: Version 7, Release 1 of AIX Version 7, Release 1 of IBM i Version 2, Release 2, Modification 2, Fixpack 26 of the Virtual I/O Server Version 7, Release 7, Modification 6 of the HMC Version AL730, release 95 of the POWER7 System Firmware Version AL740, release 95 of the POWER7 System Firmware © Copyright International Business Machines Corporation 2004, 2013. 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 Figures . xi Tables . xix Notices . xxi Trademarks . xxii Preface . xxiii Authors . xxiii Now you can become a published author, too! . xxvi Comments welcome. xxvi Stay connected to IBM Redbooks . .xxvii Summary of changes . xxix June 2013, Sixth Edition. xxix Part 1. Overview . 1 Chapter 1. PowerVM technologies. 3 1.1 The value of PowerVM . 4 1.2 What is PowerVM . 4 1.2.1 New PowerVM features . 6 1.2.2 PowerVM editions . 7 1.2.3 Activating the PowerVM feature . 12 1.3 The POWER Hypervisor . 15 1.4 Logical partitioning technologies . 17 1.4.1 Dedicated LPAR .
    [Show full text]
  • Happy Birthday Linux
    25 Jahre Linux! Am Anfang war der Quellcode Entstehungsgeschichte und Werdegang von Linux Entwicklung und Diversifizierung der Distributionen Der Wert von Linux oder: „Wat nix kost, dat is och nix.“ Andreas Klein ORR 2016 1 Am Anfang war der Quellcode (70er) ● 1969, Ken Thompson u. Dennis Ritchie erstellen die erste Version von Unix in Assembler. ● Von 1969-1971 entwickeln sie gemeinsam die Programmiersprache B. ● Ab 1971 erweiterte in erster Linie Dennis Ritchie B, um weitere Elemente und nannte sie Anfangs NB (new B). ● 1973 waren die Erweiterungen soweit gediehen, das er die stark verbesserte Sprache C nannte (Brian W. Kernighan hat ebenfalls maßgeblich dazu beigetragen). //Unix=25 PCs ● Bis 1974 war das gesamte Betriebssystem UNIX vollständig in C implementiert und wurde mit einem C-Compiler kostenfrei an verschiedene Universitäten verteilt. ● 1978 wurden bereits über 600 Computer mit dem UNIX-Betriebssystemen betrieben. ● Das aufblühende Zeitalter der Computerisierung der 70er Jahre war geprägt vom regen und freien Austausch von Programmen und dessen zugrunde liegenden Ideen. Sinnvoller Weise tauschte man diese als Quellcode untereinander aus. ● 1979 wurde von AT&T die letzte UNIX-Version 7, mit freiem Quellcode veröffentlicht. Andreas Klein ORR 2016 2 Am Anfang war der Quellcode (80er) ● 1980 – 1983 AT&T sowie zahlreiche andere Unternehmen beginnen mit der Kommerzialisierung von UNIX, durch Koppelung an stark beschränkenden Lizenzen und Geheimhaltung des zugrunde liegenden Quelltextes. ● Richard Stallman kündigt am 27. September 1983 in den Newsgroups net.unix-wizards und net.usoft das GNU-Projekt an. ● Am 5. Januar 1984 begann Stallman offiziell mit der Arbeit am GNU-Projekt, nachdem er seine Stelle am MIT gekündigt hatte.
    [Show full text]
  • POWER8: the First Openpower Processor
    POWER8: The first OpenPOWER processor Dr. Michael Gschwind Senior Technical Staff Member & Senior Manager IBM Power Systems #OpenPOWERSummit Join the conversation at #OpenPOWERSummit 1 OpenPOWER is about choice in large-scale data centers The choice to The choice to The choice to differentiate innovate grow . build workload • collaborative • delivered system optimized innovation in open performance solutions ecosystem • new capabilities . use best-of- • with open instead of breed interfaces technology scaling components from an open ecosystem Join the conversation at #OpenPOWERSummit Why Power and Why Now? . Power is optimized for server workloads . Power8 was optimized to simplify application porting . Power8 includes CAPI, the Coherent Accelerator Processor Interconnect • Building on a long history of IBM workload acceleration Join the conversation at #OpenPOWERSummit POWER8 Processor Cores • 12 cores (SMT8) 96 threads per chip • 2X internal data flows/queues • 64K data cache, 32K instruction cache Caches • 512 KB SRAM L2 / core • 96 MB eDRAM shared L3 • Up to 128 MB eDRAM L4 (off-chip) Accelerators • Crypto & memory expansion • Transactional Memory • VMM assist • Data Move / VM Mobility • Coherent Accelerator Processor Interface (CAPI) Join the conversation at #OpenPOWERSummit 4 POWER8 Core •Up to eight hardware threads per core (SMT8) •8 dispatch •10 issue •16 execution pipes: •2 FXU, 2 LSU, 2 LU, 4 FPU, 2 VMX, 1 Crypto, 1 DFU, 1 CR, 1 BR •Larger Issue queues (4 x 16-entry) •Larger global completion, Load/Store reorder queue •Improved branch prediction •Improved unaligned storage access •Improved data prefetch Join the conversation at #OpenPOWERSummit 5 POWER8 Architecture . High-performance LE support – Foundation for a new ecosystem . Organic application growth Power evolution – Instruction Fusion 1600 PowerPC .
    [Show full text]
  • Linux – Das Umfassende Handbuch 1.430 Seiten, Gebunden, Mit CD, 14
    Know-howWissen, wie’s für geht. Kreative. Leseprobe In dieser Leseprobe erhalten Sie einen Einstieg in die Linux-Welt und erfahren, wie Sie Audio und Video unter Linux nutzen. Dar- über hinaus lernen Sie die Kommandozentrale kennen: die Shell. Außerdem können Sie einen Blick in das vollständige Inhalts- und Stichwortverzeichnis des Buches werfen. »Was ist Linux?« »Installationsgrundlagen« »Audio und Video« »Die Shell« »Software- und Paketverwaltung« Inhaltsverzeichnis Index Der Autor Leseprobe weiterempfehlen Michael Kofler Linux – Das umfassende Handbuch 1.430 Seiten, gebunden, mit CD, 14. Auflage 2015 49,90 Euro, ISBN 978-3-8362-3775-8 www.rheinwerk-verlag.de/3855 “buch” — 2015/11/5 — 21:54 — page 25 — #19 1 Kapitel 1 Was ist Linux? Um die einleitende Frage zu beantworten, erkläre ich in diesem Kapitel zuerst einige wichtige Begriffe, die im gesamten Buch immer wieder verwendet werden: Betriebs- system, Unix, Distribution, Kernel etc. Ein knapper Überblick über die Merkmale von Linux und die verfügbaren Programme macht deutlich, wie weit die Anwendungs- möglichkeiten von Linux reichen. Es folgt ein kurzer Ausflug in die Geschichte von Linux: Sie erfahren, wie Linux entstanden ist und auf welchen Komponenten es basiert. Von zentraler Bedeutung ist dabei natürlich die General Public License (kurz GPL), die angibt, unter welchen Bedingungen Linux weitergegeben werden darf. Erst die GPL macht Linux zu einem freien System, wobei »frei« mehr heißt als einfach »kostenlos«. 1.1 Einführung Linux ist ein Unix-ähnliches Betriebssystem. Der wichtigste Unterschied gegenüber historischen Unix-Systemen besteht darin, dass Linux zusammen mit dem vollstän- digen Quellcode frei kopiert werden darf. Ein Betriebssystem ist ein Bündel von Programmen, mit denen die grundlegend- Betriebssystem sten Funktionen eines Rechners realisiert werden: die Schnittstelle zwischen Mensch und Maschine (also konkret: die Verwaltung von Tastatur, Bildschirm etc.) und die Verwaltung der Systemressourcen (CPU-Zeit, Speicher etc.).
    [Show full text]
  • Migrating Linux Applications from X86 to IBM Power Systems a Discussion of Best Practices
    IBM Systems and Technology Computer Services Technical White Paper Migrating Linux applications from x86 to IBM Power Systems A discussion of best practices Executive summary Contents With IBM® Power Systems™ servers and blades based on the IBM POWER® processor architecture, IBM has significantly elevated 1 Executive summary system performance, throughput and resiliency. These servers are capable of running your choice of operating systems (Linux, IBM AIX® and 2 Best practices for workload IBM i) in whatever combination you choose. Most importantly, the new selection architecture also integrates IBM PowerVM® virtualization to provide 6 Best practices during extreme scalability, flexibility and robustness.1 As a result, enterprise workload migration workloads deployed in PowerVM virtual machines (VMs) not only run faster on POWER-based platforms, but they can also scale further and 6 Capabilities be optimized more efficiently. 6 Valuable intellectual property PowerVM is a complete virtualization solution that is integrated and 10 Conclusion packaged with Power Systems. This is a very robust implementation of virtualization developed by IBM, based on best practices learned over the course of four decades of experience with the IBM mainframe. With each new Power Systems generation, IBM continues to grow its virtualization offerings beyond just the hypervisor, using features such as Live Partition Mobility and Active Memory Sharing. Reducing costs, improving service and managing risk are three focus areas virtualization customers are interested
    [Show full text]
  • IBM Power Systems Business Partner Guidebook
    December 2012 CLICK HERE to check for updates Your Roadmap IBM Power to Success with Systems IBM Power Systems Business Partner Guidebook Edited by Jim Hoskins IBM Power Systems Business Partner Guidebook Titles of Interest Other IBM Business Partner Guidebooks • IBM PureSystems Business Partner Guidebook • IBM System x & BladeCenter Business Partner Guidebook • IBM Storage Business Partner Guidebook • SmartCloud Foundation Business Partner Guidebook • IBM Systems Software Business Partner Guidebook • IBM Collaboration Solutions Guidebook For more information email us at [email protected]. IBM Power Systems Business Partner Guidebook Fourth Edition Your Roadmap to Success with IBM Power Systems Edited by Jim Hoskins (version 4.0e) 605 Silverthorn Road Gulf Breeze, FL 32561 maxpress.com Notices Production Manager: Jacquie Wallace Cover Designer: Lauren Smith This publication is designed to provide accurate and authoritative information in regard to the subject matter covered. It is sold with the understanding that the publisher is not engaged in rendering professional services. If legal, accounting, medical, psychological, or any other expert assistance is required, the services of a competent professional person should be sought. ADAPTED FROM A DECLARATION OF PRIN- CIPLES OF A JOINT COMMITTEE OF THE AMERICAN BAR ASSOCIATION AND PUBLISHERS. Copyright 2012 by Maximum Press. All rights reserved. Published simultaneously in Canada. Reproduction or translation of any part of this work beyond that permitted by Section 107 or 108 of the 1976 United States Copyright Act without the permission of the copyright owner is unlawful. Requests for permission or further information should be addressed to the Permissions Department, Maximum Press. This report was sponsored by IBM.
    [Show full text]
  • Common Package and Patch Management for SUSE Linux
    ZYPP common package and patch management for SUSE Linux Duncan Mac-Vicar P. Software Engineer, YaST Agenda ZYPP • Package management • How was it done before • ZYPP • ZYPP features • What is new? • The future © March 9, 2007 Novell Inc. 2 Package management • Automatic resolving of dependencies • Automatic fetching of packages • Handling of different installation medias • Update system with latest software available. YaST pkg-manager, apt, smart... © March 9, 2007 Novell Inc. 3 Problems with old pkg-manager - Only knew about packages - Selections were handled by the YaST UI - Patches were handled by YOU Enterprise path: • ZenWorks used libredcarpet © March 9, 2007 Novell Inc. 4 ZYPP: Overview ZYPP • Abstract resolvables: • packages, patches, messages, scripts, selections, patterns, languages, system, etc. • Better solver • Modern extensible design • new targets, source types, resolvable types, capabilities © March 9, 2007 Novell Inc. 6 ZYPP solver Source (yum) Target (rpm) Source (DVD) Pool Target (modalias) Pool Target (storage) zypp YaST ZenWorks 7 Introducing Capabilities • Grouped in: • requires, conflicts, suggests, freshens, supplements, prerequires, obsoletes, etc • Are created from a resolvable kind, and a parseable string. • Most common case, a package, and a edition: • REQUIRES, package, “kdelibs > 3.2.1” • Crazy case: REQUIRES, system, “uptime:2 years” © March 9, 2007 Novell Inc. 8 Hardware capabilities Provides capabilities based on the running system, like hardware. system PROVIDES: modalias(pci:v0000104Cd0000840[01]sv*sd*bc*sc*i*) (at runtime!) wlan-kmp-default-1_2.6.16.11_4-13.i586.rpm SUPPLEMENTS: modalias(kernel-default:pci:v0000104Cd0000840[01]sv*sd*bc*sc*i*) modalias(kernel-default:pci:v0000104Cd00009066sv*sd*bc*sc*i*) modalias(kernel-default:pci:v000010B7d00006000sv*sd*bc*sc*i*) © March 9, 2007 Novell Inc.
    [Show full text]