DOCSLIB.ORG

Best Practices Best Practices

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Best Practices Best Practices Best Practices Best Practices Publication Date: 2019-09-03 SUSE LLC 10 Canal Park Drive Suite 200 Cambridge MA 02141 USA https://www.suse.com/documentation Contents 1 Introduction 1 1.1 What’s Covered in this Guide? 1 1.2 Prerequisites 1 1.3 Network Requirements 3 1.4 Hardware Recommendations 6 2 Managing Your Subscriptions 9 2.1 SUSE Customer Center (SCC) 9 2.2 Disconnected Setup with RMT or SMT (DMZ) 9 Repository Management Tool (RMT) and Disconnected Setup (DMZ) 10 • Repository Management Tool (SMT) and Disconnected Setup (DMZ) 11 • Updating Repositories on SUSE Manager From Storage Media 12 • Refreshing Data on the Storage Medium 13 3 Expanded Support 15 3.1 Managing Red Hat Enterprise Linux Clients 15 Server Configuration for Red Hat Enterprise Linux Channels 15 • Red Hat Enterprise Linux Channel Management Tips 16 • Mirroring RHEL Media into a Channel 16 • Registering RES Salt Minions with SUSE Manager 17 • Register a Salt Minion via Bootstrap 19 • Manual Salt Minion Registration 20 3.2 Preparing Channels and Repositories for CentOS Traditional Clients 20 3.3 Registering CentOS Salt Minions with SUSE Manager 23 3.4 Managing Ubuntu Clients 24 3.5 Prepare to Register Ubuntu Clients 25 iii Best Practices 4 Salt Formulas and SUSE Manager 28 4.1 What are Salt Formulas? 28 4.2 Installing Salt Formulas via RPM 28 4.3 File Structure Overview 30 4.4 Editing Pillar Data in SUSE Manager 31 Simple edit-group Example 38 4.5 Writing Salt Formulas 41 4.6 Separating Data 42 4.7 SUSE Manager Generated Pillar Data 43 4.8 Formula Requirements 44 4.9 Using Salt Formulas with SUSE Manager 45 4.10 SUSE Manager for Retail Salt Formulas 46 Pxe Formula 46 • Branch Network Formula 48 • Saltboot Formula 50 • Image Sync Formula 53 4.11 Salt Formulas Coming with SUSE Manager 53 Locale 53 • Domain Name System (Bind) 53 • Dhcpd 59 • Tftpd 61 • Vsftpd 62 5 Configuration Management with Salt 65 5.1 Configuration Management Overview 65 5.2 State Data: Levels of Hierarchy 65 5.3 Salt States Storage Locations 66 5.4 SUSE Manager States 66 5.5 Pillar Data 67 5.6 Group States 67 6 Salt Minion Scalability 69 6.1 Salt Minion Onboarding Rate 69 iv Best Practices 6.2 Minions Running with Unaccepted Salt Keys 69 6.3 Salt Timeouts 69 Presence Ping Timeout 70 6.4 Batching 71 Salt SSH Minions (SSH Push) 72 7 Activation Key Management 73 7.1 What are Activation Keys? 73 7.2 Provisioning and Configuration 74 7.3 Activation Keys Best Practices 74 Key Label Naming 75 • Channels which will be Included 75 7.4 Combining Activation Keys 76 7.5 Using Activation Keys and Bootstrap with Traditional Clients (Non- Salt) 77 7.6 Using Activation Keys when Registering Salt Minions 78 Using an Activation Key and Custom Grains File 78 • Using an Activation Key in the Minion Configuration File 79 8 Contact Methods 80 8.1 Selecting a Contact Method 80 8.2 Traditional Contact Method (rhnsd) 80 Configuring SUSE Manager rhnsd Daemon or Timer 81 • Viewing rhnsd Daemon or Timer Status 82 8.3 Push via SSH 82 Configuring the Server for Push via SSH 83 • Using sudo with Push via SSH 84 • Client Registration 85 • API Support for Push via SSH 86 • Proxy Support with Push via SSH 87 8.4 Push via Salt SSH 87 Overview 88 • Requirements 88 • Bootstrapping 89 • Configuration 90 • Action Execution 90 • Known Limitation 90 • For More Information 90 v Best Practices 8.5 OSAD 91 Enabling and Configuring OSAD 92 9 Advanced Patch Lifecycle Management 94 10 Live Patching with SUSE Manager 95 10.1 Introduction 95 10.2 Initial Setup Requirements 95 10.3 Live Patching Setup 95 10.4 Cloning Channels 97 10.5 Removing Non-live Kernel Patches from the Cloned Channels 98 10.6 Promoting Channels 98 10.7 Applying Live Patches to a Kernel 99 11 SUSE Manager Server Migration 101 11.1 Service Pack Migration Introduction 101 11.2 Service Pack Migration 101 11.3 Upgrading PostgreSQL to Version 9.6 102 11.4 Updating SUSE Manager 102 11.5 Migrating SUSE Manager version 3.1 to 3.2 103 Using YaST 104 • Using zypper 105 11.6 SUSE Manager Migration from Version 2.1 to Version 3 106 Prerequisites 107 • Setup the Target Machine 108 • Performing the Migration 109 • Speeding up the Migration 110 • Packages on External Storage 111 • Troubleshooting a Broken Web UI after Migration 111 • Example Session 111 vi Best Practices 12 Client Migration 117 12.1 Upgrading SLE 12 SPx to version 15 117 System Upgrade Preparation 118 • Sample Autoinstallation Script for System Upgrade (SLES 12 SP4 to SLES 15) 120 12.2 Migrating SLE 12 or later to version 12 SP4 121 13 PostgreSQL Database Migration 129 13.1 New SUSE Manager Installations 129 13.2 Migrating an Existing Installation 129 13.3 Performing a Fast Migration 130 13.4 Typical Migration Sample Session 131 14 Backup and Restore 135 14.1 Backing up SUSE Manager 135 14.2 Administering the Database with smdba 137 14.3 Database Backup with smdba 138 Performing a Manual Database Backup 139 • Scheduling Automatic Backups 140 14.4 Restoring from Backup 141 14.5 Archive Log Settings 141 14.6 Retrieving an Overview of Occupied Database Space 142 14.7 Moving the Database 143 14.8 Recovering from a Crashed Root Partition 144 14.9 Database Connection Information 145 15 Authentication Methods 146 15.1 Authentication Via PAM 146 15.2 Authentication Via eDirectory and PAM 147 vii Best Practices 15.3 Example Quest VAS Active Directory Authentication Template 148 16 Using a Custom SSL Certificate 149 16.1 Prerequisites 149 16.2 Setup 149 16.3 Using a Custom Certificate with SUSE Manager Proxy 150 17 Troubleshooting 151 17.1 Registering Cloned Salt Minions 151 17.2 Registering Cloned Traditional Systems 152 17.3 Typical OSAD/jabberd Challenges 154 Open File Count Exceeded 154 • jabberd Database Corruption 155 • Capturing XMPP Network Data for Debugging Purposes 156 • Engineering Notes: Analyzing Captured Data 157 17.4 Gathering Information with spacewalk-report 158 17.5 RPC Connection Timeout Settings 161 17.6 Client/Server Package Inconsistency 162 17.7 Corrupted Repository Data 163 17.8 Unable to Get Local Issuer Certificate 163 18 Additional Resources 164 18.1 Learning YAML Syntax for Salt States 164 18.2 Getting Started with Jinja Templates 164 18.3 Salt Best Practices 164 19 A SUSE Manager 2.1 and 3.2 Product Comparison 165 A GNU Licenses 169 20 GNU Free Documentation License 170 viii Best Practices 1 Introduction This document targets system administrators. 1.1 What’s Covered in this Guide? This document describes SUSE recommended best practices for SUSE Manager. This information has been collected from a large number of successful SUSE Manager real world implementations and includes feedback provided by product management, sales and engineering. Note: SUSE Manager Version Information In this manual if not other specified, SUSE Manager version 3.2 is assumed and this version is required if a feature is discussed. SUSE Manager 3.2 and SUSE Manager 3.2 Proxy were originally released as a SLES 12 SP3 extension. With the next maintenance update (December 2018), SUSE Manager 3.2 and SUSE Manager 3.2 Proxy will be based on SLES 12 SP4 and support SLE 12 SP4 clients officially. In the following sections and chapters, it is highly recommended to use SLE 12 SP4 instead of SP3. Whenever features of the SUSE Manager 3.2 host operating system are documented and not other specified version 12 SP4 is assumed. This chapter will discuss the following topics: Prerequisites Network Requirements Hardware Requirements 1.2 Prerequisites Purchased Registration Keys. During initial setup SUSE Manager will request a product Regis- tration Key . This key will be provided to you after purchasing the product. You can nd your key located under your SUSE Customer Center account. Log-in with your SUSE Customer Center credentials or register for a new account. -https://scc.suse.com 1 What’s Covered in this Guide? Evaluation Keys. If you wish to run a test system (non-production) a 60 day evaluation key may be obtained. On the SUSE Manager product page click TRY SUSE MANAGER. The evaluation key limits the number of systems that may be registered with SUSE Manager to 10. For more information see: https://www.suse.com/products/suse-manager/ SCC Organization Credentials. During setup you will also be asked to enter your SUSE Customer Center Organization Credentials . Users and Passwords. During both the SUSE Linux Enterprise installation and setup of SUSE Manager several users and passwords will be created: SUSE Linux Enterprise root user account PostgreSQL database user and password Certificate of Authority password SUSE Manager administrator user and password Tip: Safe Passwords Maintain security by creating safe passwords. Store passwords within a secure location. Use the following guidelines when creating your passwords. At least 8 characters long Should contain uppercase characters A B C Should contain lowercase characters a b c Should contain numbers 1 2 3 Should contain symbols ~ ! @ # 2 Prerequisites 1.3 Network Requirements SUSE Manager and SUSE Manager Proxy both contact several external addresses in order to maintain updates and subscriptions. The following lists provide the up-to-date hostnames for each service requiring permission when used in combination with corporate firewall and content filters. SUSE CUSTOMER CENTER HOSTNAMES (REQUIRED) https://scc.suse.com https://updates.suse.com NOVELL CUSTOMER CENTER HOSTNAMES (LEGACY) https://secure-www.novell.com https://nu.novell.com For SUSE Manager to function properly it requires the following pre-configured components within your network.
Load more

Recommended publications
  • Fedora Core Works--Without the Fluff That Bogs Down Other Books and Help/How-To Web Sites
    Fedora Linux By Chris Tyler ............................................... Publisher: O'Reilly Pub Date: October 01, 2006 ISBN-10: 0-596-52682-2 ISBN-13: 978-0-596-52682-5 Pages: 504 Table of Contents | Index "Neither a "Starting Linux" book nor a dry reference manual, this book has a lot to offer to those coming to Fedora from other operating systems or distros." -- Behdad Esfahbod, Fedora developer This book will get you up to speed quickly on Fedora Linux, a securely-designed Linux distribution that includes a massive selection of free software packages. Fedora is hardened out-of-the-box, it's easy to install, and extensively customizable - and this book shows you how to make Fedora work for you. Fedora Linux: A Complete Guide to Red Hat's Community Distribution will take you deep into essential Fedora tasks and activities by presenting them in easy-to-learn modules. From installation and configuration through advanced topics such as administration, security, and virtualization, this book captures the important details of how Fedora Core works--without the fluff that bogs down other books and help/how-to web sites. Instead, you can learn from a concise task-based approach to using Fedora as both a desktop and server operating system. In this book, you'll learn how to: Install Fedora and perform basic administrative tasks Configure the KDE and GNOME desktops Get power management working on your notebook computer and hop on a wired or wireless network Find, install, and update any of the thousands of packages available for Fedora Perform backups, increase reliability with RAID, and manage your disks with logical volumes Set up a server with file sharing, DNS, DHCP, email, a Web server, and more Work with Fedora's security features including SELinux, PAM, and Access Control Lists (ACLs) Whether you are running the stable version of Fedora Core or bleeding-edge Rawhide releases, this book has something for every level of user.
    [Show full text]
  • Spacewalk 2.4 for Oracle® Linux Concepts and Getting Started Guide
    Spacewalk 2.4 for Oracle® Linux Concepts and Getting Started Guide E71709-03 January 2017 Oracle Legal Notices Copyright © 2017, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S.
    [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]
  • Openshift Virtualization Aka Container-Native Virtualization (CNV)
    OpenShift virtualization Aka Container-native virtualization (CNV) Robert Bohne SR. SPECIALIST SOLUTION ARCHITECT | OPENSHIFT Twitter: @RobertBohne 1 Red Hat OpenShift and OpenShift virtualization Modernize workloads and support mixed applications consisting of VMs, containers, and serverless ● Accelerate application delivery with a single platform that can manage “mixed VMs Containers applications” with the same tools and teams Red Hat OpenShift Container Platform ● Add VMs to new and existing applications ● Modernize legacy VM applications over Red Hat Enterprise Linux CoreOS time, or maintain them as VMs Physical machine 2 V0000000 KVM-based (containerized) VMs ● KVM is a part of the Red Hat Enterprise Linux kernel OTHER APPS libvirt ● QEMU uses KVM to execute virtual machines QEMU ● libvirt provides a management abstraction RHEL layer KVM ● Red Hat Virtualization, Red Hat OpenStack DRIVER DRIVER DRIVER Platform, and OpenShift virtualization all leverage KVM, QEMU, and libvirt CPU/RAM STORAGE NETWORK HARDWARE 3 Containerized virtual machines ● Inherit many features and functions from Kubernetes ○ Scheduling, high availability, attach/detach resources ● Containerized virtual machines have the same limitations as non-containerized ○ CPU, RAM, etc. limitations dictated by libvirt and QEMU ○ Linux and Windows guest operating systems ● Storage ○ Use Persistent Volumes Claims (PVCs) for VM disks ○ Containerized Data Importer (CDI) import VM images ● Network ○ Inherit pod network by default 4 ○ Multus enables direct connection to external network Architectural Overview kubelet (DaemonSet) Pod VM Pod Other Pod(s) API Server virt-handler virt-launcher container 1 virt-controller libvirtd container 2 VM container n Cluster Services Nodes 5 KubeVirt ▸ Open Source, Go ▸ Initiated in 2016 by Red Hat ▸ Contributions by other companies e.g (v)GPU support by Nvidia ▸ CNCF sandbox project since 2019 ▸ Provides an API for running KVM based virtual machines in Kubernetes ▸ Goal: run those VMs alongside with containerized workloads, using the same networks / storage etc.
    [Show full text]
  • Openshift Container Platform 4.6 Architecture
    OpenShift Container Platform 4.6 Architecture An overview of the architecture for OpenShift Container Platform Last Updated: 2021-09-22 OpenShift Container Platform 4.6 Architecture An overview of the architecture for OpenShift Container Platform 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. Node.js ® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
    [Show full text]
  • Fedora (Operating System) 1 Fedora (Operating System)
    Fedora (operating system) 1 Fedora (operating system) Fedora Fedora 17 (Beefy Miracle) running GNOME Shell 3.4 Company / developer Fedora Project, (sponsored by Red Hat, Inc.) OS family Unix-like (based on Red Hat Linux) Working state Current [1] Source model Free and open source software (with exceptions) [2] Initial release 2003-11-16 It was codenamed Yarrow. Fedora Core 1 was based on Red Hat Linux 9 and shipped with version 2.4.19 [3] of the Linux kernel, version 2.4 of the GNOME desktop environment, and K Desktop Environment 3.1. Latest stable release 17 (Beefy Miracle) / May 29, 2012 Available language(s) Multilingual Update method Yum (PackageKit) Package manager RPM Package Manager Supported platforms i686, x86-64 Kernel type Monolithic (Linux) Userland GNU Default user interface GNOME 3 [1] License Various free software licenses, plus proprietary binary blobs. Official website [4] www.fedoraproject.org Fedora ( /fɪˈdɒr.ə/), formerly Fedora Core, is an RPM-based, general purpose collection of software, including an operating system based on the Linux kernel, developed by the community-supported Fedora Project and sponsored by Red Hat. Fedora’s flexibility makes it capable of serving as a digital repository for a variety of use cases. The Fedora Project's mission is to lead the advancement of free and open source software and content as a collaborative community.[5] One of Fedora's main objectives is not only to contain software distributed under a free and open source license, but also to be on the leading edge of such technologies.[6][7] Fedora developers prefer to make upstream changes instead of applying fixes specifically for Fedora—this ensures that their updates are available to all Linux distributions.[8] Compared to more mainstream non-Linux operating systems, Fedora has a short life cycle.
    [Show full text]
  • How to Modernize AIX Applications In- Place Using Red Hat Openshift
    January 2021 How to Modernize AIX Applications In- place Using Red Hat OpenShift By: Angshuman Roy [email protected] IBM IT Economics Consulting & Research © 2021 IBM Corporation Enterprises are modernizing their application to bring in cloud-native capabilities that work in a Hybrid Multicloud environment. In its Total Economic Impact study, Forrester found that clients accelerated development cycles by up to 66% by modernizing (ibm.co/3fvl8d2). Quite often, these organizations are looking at multiple cloud providers to host different parts of their applications while keeping mission critical workloads in-house. According to Flexera 2020 State of the Cloud Report (bit.ly/3iYCCR4), 93% of enterprises are pursuing a multicloud strategy, which helps them from being tied to a single vendor. To make an application more portable across multiple clouds, it must run on a unifying platform. Red Hat® OpenShift® is that platform. OpenShift extends the Kubernetes with built-in tools to enhance app lifecycle development, operations and security. With OpenShift, clients can consistently deploy workloads across multiple public or private clouds with ease. This article will break down how my team modernized a banking application running on AIX®. We built a new User Interface and deployed it on Red Hat OpenShift running on the existing IBM Power Systems™ server, while the business logic continued to run on the AIX backend. We added new functionality that ran on three different public clouds: IBM Cloud™, Amazon Web Services and Microsoft® Azure. All these environments were managed using IBM Cloud Pak® for Multicloud Management, also running on POWER®. Advantages of Containers in App Modernization One of the most common approaches to modernizing legacy applications starts by containerizing them so that they can be migrated to cloud.
    [Show full text]
  • Cobbler Documentation Release 2.8.5
    Cobbler Documentation Release 2.8.5 Jörgen Maas Nov 19, 2020 Contents 1 About 3 1.1 Release Notes.........................................3 1.2 Distribution Support......................................5 1.3 Distribution Notes.......................................7 1.4 How We Model Things..................................... 13 2 Installation 15 2.1 Prerequisites.......................................... 15 2.2 Installing from packages.................................... 16 2.3 Installing from Source..................................... 18 2.4 Configuration Files....................................... 20 2.5 Relocating your installation.................................. 21 3 General 23 3.1 Cobbler Primitives....................................... 23 3.2 Cobbler Direct Commands................................... 54 3.3 Cobbler Settings........................................ 69 3.4 Managing Services with Cobbler............................... 90 3.5 Kickstart Templating...................................... 94 3.6 Snippets............................................ 102 3.7 Package Management and Mirroring............................. 112 3.8 File System Information.................................... 114 4 Advanced 119 4.1 Advanced Networking..................................... 119 4.2 SELinux............................................ 122 4.3 Configuration Management.................................. 123 4.4 Extending cobbler....................................... 131 4.5 Power Management...................................... 135 4.6
    [Show full text]
  • Openshift Container Platform 4.6 Release Notes
    OpenShift Container Platform 4.6 Release notes Highlights of what is new and what has changed with this OpenShift Container Platform release Last Updated: 2021-09-22 OpenShift Container Platform 4.6 Release notes Highlights of what is new and what has changed with this OpenShift Container Platform release 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. Node.js ® is an official trademark of Joyent.
    [Show full text]
  • Scientific Linux - the Future of DESY Linux (?)
    Scientific Linux - The Future of DESY Linux (?) Stephan Wiesand DESY -DV - September 14, 2004 Outline What DESY Linux (DL) is What Scientific Linux (SL) is What Scientific Linux DESY (SLD) will be What the status of SLD3 is What will change from the user's point of view When it's going to happen DESY Linux base distribution criteria: usability, size, lifetime (availability of security fixes), use/acceptance in HEP, ISV support + bug fixes example: make screen lock usable in kerberized environment + customization examples: HEPiX, HEPiX11, continuity for users + additional software /opt/products + automatic installation, configuration and maintenance VAMOS/sue/cfengine Base Distribution Candidates: debian lifetime: 12 months after next release release cycle completely undefined when we picked the DL5 base distro last year, we wondered whether a new debian stable would be released the same year it wasn't, and the question remains the same debian stable is completely out of date not usable on current hardware not available for amd64 (platform younger than distro) not widely accepted in HEP debian is not for us Candidates: SuSE Professional current choice for DL5 8.2 9.0 for notebooks, amd64 defined release cycle: every 6 months defined lifetime: 2 years barely enough after release, security fixes only no bug fixes or enhancements not widely accepted in HEP acquisition by Novell may improve acceptance in US Candidates: SuSE Enterprise release cycle: 12-18 months lifetime: 5 years security fixes bug fixes, enhancements for < 5 years much shorter
    [Show full text]
  • Contents at a Glance
    04_579495 ftoc.qxd 12/27/04 9:52 PM Page xii Contents at a Glance Preface . vii Acknowledgments . xi Part I: Linux First Steps. 1 Chapter 1: Starting with Linux . 3 Chapter 2: Running Commands from the Shell . 29 Chapter 3: Getting into the Desktop . 77 Part II: Running the Show . 123 Chapter 4: Learning Basic Administration . 125 Chapter 5: Getting on the Internet . 169 Chapter 6: Securing Linux . 191 Part III: Choosing and Installing a Linux Distribution . 241 Chapter 7: Installing Linux . 243 Chapter 8: Running Fedora Core and Red Hat Enterprise Linux . 273 Chapter 9: Running Debian GNU/Linux . 295 Chapter 10: Running SUSE Linux . 315 Chapter 11: Running KNOPPIX . 329 Chapter 12: Running Yellow Dog Linux . 351 Chapter 13: Running Gentoo Linux . 367 Chapter 14: Running Slackware Linux . 383 Chapter 15: Running Linspire . 399 Chapter 16: Running Mandrakelinux . 409 Chapter 17: Running a Linux Firewall/Router . 423 Chapter 18: RunningCOPYRIGHTED Bootable Linux Distributions MATERIAL . 447 Part IV: Running Applications . 459 Chapter 19: Playing Music and Video . 461 Chapter 20: Working with Words and Images . 501 Chapter 21: E-Mailing and Web Browsing . 541 Chapter 22:Gaming Alone and Online . 569 04_579495 ftoc.qxd 12/27/04 9:52 PM Page xiii Part V:Running Servers . 593 Chapter 23: Running a Linux, Apache, MySQL, and PHP (LAMP) Server . 595 Chapter 24: Running a Mail Server . 617 Chapter 25: Running a Print Server . 635 Chapter 26: Running a File Server . 659 Part VI: Programming in Linux. 693 Chapter 27: Programming Environments and Interfaces . 695 Chapter 28: Programming Tools and Utilities .
    [Show full text]
  • Fedora Infrastructure Best Practices Documentation Release 1.0.0
    Fedora Infrastructure Best Practices Documentation Release 1.0.0 The Fedora Infrastructure Team Sep 09, 2021 Full Table of Contents: 1 Getting Started 3 1.1 Create a Fedora Account.........................................3 1.2 Subscribe to the Mailing List......................................3 1.3 Join IRC.................................................3 1.4 Next Steps................................................4 2 Full Table of Contents 5 2.1 Developer Guide.............................................5 2.2 System Administrator Guide....................................... 28 2.3 (Old) System Administrator Guides................................... 317 3 Indices and tables 335 i ii Fedora Infrastructure Best Practices Documentation, Release 1.0.0 This contains a development and system administration guide for the Fedora Infrastructure team. The development guide covers how to get started with application development as well as application best practices. You will also find several sample projects that serve as demonstrations of these best practices and as an excellent starting point for new projects. The system administration guide covers how to get involved in the system administration side of Fedora Infrastructure as well as the standard operating procedures (SOPs) we use. The source repository for this documentation is maintained here: https://pagure.io/infra-docs Full Table of Contents: 1 Fedora Infrastructure Best Practices Documentation, Release 1.0.0 2 Full Table of Contents: CHAPTER 1 Getting Started Fedora Infrastructure is full of projects that need help. In fact, there is so much work to do, it can be a little over- whelming. This document is intended to help you get ready to contribute to the Fedora Infrastructure. 1.1 Create a Fedora Account The first thing you should do is create a Fedora account.
    [Show full text]