DOCSLIB.ORG

SUSE Linux Enterprise Server 11 SP4 Administration Guide Administration Guide SUSE Linux Enterprise Server 11 SP4

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

SUSE Linux Enterprise Server 11 SP4 Administration Guide Administration 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 xix 1 Available Documentation xx 2 Feedback xxii 3 Documentation Conventions xxii I SUPPORT AND COMMON TASKS 1 1 YaST Online Update 2 1.1 The Online Update Dialog 3 KDE Interface (Qt) 3 • GNOME Interface (GTK) 4 1.2 Installing Patches 6 1.3 Automatic Online Update 7 2 Gathering System Information for Support 9 2.1 Collecting System Information with Supportconfig 9 Creating a Service Request Number 9 • Upload Targets 10 • Creating a Supportconfig Archive with YaST 10 • Creating a Supportconfig Archive from Command Line 12 • Common Supportconfig Options 12 2.2 Submitting Information to Global Technical Support 13 2.3 Support of Kernel Modules 15 Technical Background 16 • Working with Unsupported Modules 16 2.4 For More Information 17 3 YaST in Text Mode 18 3.1 Navigation in Modules 19 3.2 Restriction of Key Combinations 21 iii Administration Guide 3.3 YaST Command Line Options 21 Starting the Individual Modules 21 • Installing Packages from the Command Line 22 • Command Line Parameters of the YaST Modules 22 4 Snapshots/Rollback with Snapper 23 4.1 Requirements 23 Snapshots and Disk Space 23 4.2 Using Snapper to Undo System Changes 24 Undoing YaST and Zypper Changes 25 • Using Snapper to Restore Files from Hourly Backups 30 • Creating and Modifying Snapper Configurations 31 • Disabling Automatic Snapshots 35 4.3 Manually Creating and Managing Snapshots 35 Snapshot Metadata 36 • Creating Snapshots 37 • Modifying Snapshot Metadata 38 • Deleting Snapshots 39 4.4 Limitations 39 Data Consistency 40 • Reverting User Additions 40 • No Rollback on / boot and Boot Loader Changes 40 4.5 Frequently Asked Questions 41 4.6 Using Snapper on Thin-Provisioned LVM Volumes 41 5 Remote Access with VNC 43 5.1 One-time VNC Sessions 43 Initiating a One-time VNC Session 44 • Configuring One-time VNC Sessions 44 5.2 Persistent VNC Sessions 45 Connecting to a Persistent VNC Session 47 • Configuring Persistent VNC Sessions 47 6 Managing Software with Command Line Tools 48 6.1 Using Zypper 48 General Usage 48 • Installing and Removing Software with Zypper 49 • Updating Software with Zypper 52 • Distribution Upgrade iv Administration Guide with zypper 55 • Managing Repositories with zypper 59 • Querying Repositories and Packages with Zypper 61 • Configuring Zypper 62 • Troubleshooting 63 • Zypper Rollback Feature on btrfs File System 63 6.2 RPM—the Package Manager 63 Verifying Package Authenticity 64 • Managing Packages: Install, Update, and Uninstall 64 • RPM and Patches 66 • Delta RPM Packages 67 • RPM Queries 68 • Installing and Compiling Source Packages 71 • Compiling RPM Packages with build 73 • Tools for RPM Archives and the RPM Database 73 7 Bash and Bash Scripts 74 7.1 What is “The Shell”? 74 Knowing The Bash Configuration Files 74 • The Directory Structure 75 7.2 Writing Shell Scripts 79 7.3 Redirecting Command Events 80 7.4 Using Aliases 81 7.5 Using Variables in Bash 82 Using Argument Variables 83 • Using Variable Substitution 83 7.6 Grouping And Combining Commands 84 7.7 Working with Common Flow Constructs 85 The if Control Command 85 • Creating Loops With the For Command 86 7.8 For More Information 86 8 Using Third-Party Software 87 II SYSTEM 88 9 32-Bit and 64-Bit Applications in a 64-Bit System Environment 89 9.1 Runtime Support 89 9.2 Software Development 90 v Administration Guide 9.3 Software Compilation on Biarch Platforms 91 9.4 Kernel Specifications 92 10 Booting and Configuring a Linux System 94 10.1 The Linux Boot Process 94 initramfs 95 • init on initramfs 96 10.2 The init Process 98 Runlevels 98 • Init Scripts 101 • Configuring System Services (Runlevel) with YaST 104 10.3 System Configuration via /etc/sysconfig 106 Changing the System Configuration Using the YaST sysconfig Editor 107 • Changing the System Configuration Manually 108 11 The Boot Loader GRUB 109 11.1 Booting with GRUB 110 The File /boot/grub/menu.lst 111 • The File device.map 116 • The File / etc/grub.conf 117 • The File /etc/sysconfig/bootloader 118 • Setting a Boot Password 119 11.2 Configuring the Boot Loader with YaST 120 Adjusting the Default Boot Entry 121 • Modifying the Boot Loader Location 122 • Changing the Boot Loader Time-Out 122 • Setting a Boot Password 123 • Adjusting the Disk Order 123 • Configuring Advanced Options 124 • Changing Boot Loader Type 125 11.3 Uninstalling the Linux Boot Loader 126 11.4 Creating Boot CDs 126 11.5 The Graphical SUSE Screen 128 11.6 Troubleshooting 128 11.7 For More Information 130 vi Administration Guide 12 UEFI (Unified Extensible Firmware Interface) 131 12.1 Secure Boot 131 Implementation on SUSE Linux Enterprise 132 • MOK (Machine Owner Key) 135 • Booting a Custom Kernel 135 • Using Non-Inbox Drivers 137 • Limitations 138 12.2 For More Information 138 13 Special System Features 139 13.1 Information about Special Software Packages 139 The bash Package and /etc/profile 139 • The cron Package 140 • Log Files: Package logrotate 141 • The locate Command 142 • The ulimit Command 142 • The free Command 143 • Man Pages and Info Pages 144 • Selecting Man Pages Using the man Command 144 • Settings for GNU Emacs 144 13.2 Virtual Consoles 145 13.3 Keyboard Mapping 146 13.4 Language and Country-Specific Settings 146 Some Examples 147 • Locale Settings in ~/.i18n 149 • Settings for Language Support 149 • For More Information 150 14 Printer Operation 151 14.1 The Workflow of the Printing System 152 14.2 Methods and Protocols for Connecting Printers 153 14.3 Installing the Software 153 14.4 Network Printers 154 Configuring CUPS with Command Line Tools 155 14.5 Printing from the Command Line 157 14.6 Special Features in SUSE Linux Enterprise Server 157 CUPS and Firewall 157 • PPD Files in Various Packages 158 vii Administration Guide 14.7 Troubleshooting 159 Printers without Standard Printer Language Support 159 • No Suitable PPD File Available for a PostScript Printer 160 • Parallel Ports 160 • Network Printer Connections 161 • Defective Printouts without Error Message 164 • Disabled Queues 164 • CUPS Browsing: Deleting Print Jobs 164 • Defective Print Jobs and Data Transfer Errors 165 • Debugging the CUPS Print System 165 • For More Information 166 15 Dynamic Kernel Device Management with udev 167 15.1 The /dev Directory 167 15.2 Kernel uevents and udev 167 15.3 Drivers, Kernel Modules and Devices 168 15.4 Booting and Initial Device Setup 168 15.5 Monitoring the Running udev Daemon 169 15.6 Influencing Kernel Device Event Handling with udev Rules 170 Using Operators in udev Rules 172 • Using Substitutions in udev Rules 173 • Using udev Match Keys 174 • Using udev Assign Keys 175 15.7 Persistent Device Naming 176 15.8 Files used by udev 177 15.9 For More Information 178 16 The X Window System 179 16.1 Manually Configuring the X Window System 179 Screen Section 183 • Device Section 184 • Monitor and Modes Section 185 16.2 Installing and Configuring Fonts 186 X11 Core Fonts 187 • Xft 188 16.3 For More Information 192 17 Accessing File Systems with FUSE 193 17.1 Configuring FUSE 193 viii Administration Guide 17.2 Available FUSE Plug-ins 193 17.3 For More Information 194 III MOBILE COMPUTERS 195 18 Mobile Computing with Linux 196 18.1 Laptops 196 Power Conservation 196 • Integration in Changing Operating Environments 197 • Software Options 200 • Data Security 202 18.2 Mobile Hardware 203 18.3 Cellular Phones and PDAs 204 18.4 For More Information 204 19 Wireless LAN 206 19.1 WLAN Standards 206 19.2 Operating Modes 207 19.3 Authentication 208 19.4 Encryption 209 19.5 Configuration with YaST 210 Deactivating NetworkManager 211 • Configuration for Access Points 211 • Establishing an Ad-Hoc Network 215 • Setting Additional Configuration Parameters 216 19.6 Tips and Tricks for Setting Up a WLAN 217 Utilities 217 • Stability and Speed 217 • Security 218 19.7 Troubleshooting 219 Check the Network Status 219 • Multiple Network Devices 220 • Problems with Prism2 Cards 220 19.8 For More Information 220 ix Administration Guide 20 Power Management 222 20.1 Power Saving Functions 222 20.2 Advanced Configuration and Power Interface (ACPI) 223 Controlling the CPU Performance 223 • Troubleshooting 224 20.3 Rest for the Hard Disk 225 20.4 Troubleshooting 227 ACPI Activated with Hardware Support but Functions Do Not Work 227 • CPU Frequency Does Not Work 228 • Suspend and Standby Do Not Work 228 20.5 For More Information 228 21 Using Tablet PCs 229 21.1 Installing Tablet
Recommended publications
  • MLNX OFED Documentation Rev 5.0-2.1.8.0

    MLNX OFED Documentation Rev 5.0-2.1.8.0

    MLNX_OFED Documentation Rev 5.0-2.1.8.0 Exported on May/21/2020 06:13 AM https://docs.mellanox.com/x/JLV-AQ Notice This document is provided for information purposes only and shall not be regarded as a warranty of a certain functionality, condition, or quality of a product. NVIDIA Corporation (“NVIDIA”) makes no representations or warranties, expressed or implied, as to the accuracy or completeness of the information contained in this document and assumes no responsibility for any errors contained herein. NVIDIA shall have no liability for the consequences or use of such information or for any infringement of patents or other rights of third parties that may result from its use. This document is not a commitment to develop, release, or deliver any Material (defined below), code, or functionality. NVIDIA reserves the right to make corrections, modifications, enhancements, improvements, and any other changes to this document, at any time without notice. Customer should obtain the latest relevant information before placing orders and should verify that such information is current and complete. NVIDIA products are sold subject to the NVIDIA standard terms and conditions of sale supplied at the time of order acknowledgement, unless otherwise agreed in an individual sales agreement signed by authorized representatives of NVIDIA and customer (“Terms of Sale”). NVIDIA hereby expressly objects to applying any customer general terms and conditions with regards to the purchase of the NVIDIA product referenced in this document. No contractual obligations are formed either directly or indirectly by this document. NVIDIA products are not designed, authorized, or warranted to be suitable for use in medical, military, aircraft, space, or life support equipment, nor in applications where failure or malfunction of the NVIDIA product can reasonably be expected to result in personal injury, death, or property or environmental damage.
  • Oracle Database Licensing Information, 11G Release 2 (11.2) E10594-26

    Oracle Database Licensing Information, 11G Release 2 (11.2) E10594-26

    Oracle® Database Licensing Information 11g Release 2 (11.2) E10594-26 July 2012 Oracle Database Licensing Information, 11g Release 2 (11.2) E10594-26 Copyright © 2004, 2012, Oracle and/or its affiliates. All rights reserved. Contributor: Manmeet Ahluwalia, Penny Avril, Charlie Berger, Michelle Bird, Carolyn Bruse, Rich Buchheim, Sandra Cheevers, Leo Cloutier, Bud Endress, Prabhaker Gongloor, Kevin Jernigan, Anil Khilani, Mughees Minhas, Trish McGonigle, Dennis MacNeil, Paul Narth, Anu Natarajan, Paul Needham, Martin Pena, Jill Robinson, Mark Townsend 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, 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.
  • IBM Power Systems Private Cloud Solution Is Enhanced to Support Selected SUSE Linux Enterprise Server Subscriptions As Shared Utility Capacity Resources

    IBM Power Systems Private Cloud Solution Is Enhanced to Support Selected SUSE Linux Enterprise Server Subscriptions As Shared Utility Capacity Resources

    IBM United States Hardware Announcement 121-045, dated April 20, 2021 IBM Power Systems Private Cloud Solution is enhanced to support selected SUSE Linux Enterprise Server subscriptions as Shared Utility Capacity resources Table of contents 1 Overview 1 Description 1 Key requirements 2 Order now 1 Effective date Overview The IBM(R) Power(R) Systems Private Cloud Solution with Shared Utility Capacity was initially launched with support to share Base processor and memory hardware resources, as well as AIX(R) and IBM i license entitlements, across a collection of similar Power servers in an enterprise. Now, selected SUSE Linux(R) Enterprise Server (SLES) subscription offerings will be supported as Base and Metered Capacity resources within an IBM Power Enterprise Pool (2.0) of IBM Power System E980 or E950 servers. Key requirements • For Linux metering, HMC 950 is required. Effective date April 30, 2021 Description SUSE Linux Enterprise Server subscription offerings will now be monitored, shared as Base Capacity, and made available as pay-per-use Metered Capacity resources when a Power Enterprise Pool (2.0) consisting of Power E980 or Power E950 systems is started: 5639-15S 5639-12S SUSE Linux Enterprise Server for Power with Base 1 - 2 Socket, Unlimited LPAR and Priority Subscription or Priority Subscription/Support features 5639-SAP SUSE Linux Enterprise Server for SAP Applications for Power with 1 - 2 Socket, Unlimited LPAR and Priority Subscription or Priority Subscription/Support features Base Capacity resources may be shared across systems within a pool. SLES Base subscription entitlement for each system will be set to the number of cores available in the quantity of sockets entitled by the current, valid subscription for that system IBM United States Hardware Announcement 121-045 IBM is a registered trademark of International Business Machines Corporation 1 (the number of cores per chip multiplied by the quantity of sockets acquired in the current subscription).

  • Intel® Vtune Amplifier Latest Featured Articles

    ARTICLES & REVIEWS NEWS ARCHIVE FORUMS PREMIUM CATEGORIES Search Latest Linux News Debian Linux Is Now Available For NVIDIA's Jetson TX1 AMDGPU-PRO 16.60 Released It Looks Like Civilization VI Could Be There's Now A KDE-Branded Laptop Running Neon With Shipping Soon For Linux Plasma 5 Shadow of Mordor Updated For Linux With Written by Michael Larabel in KDE on 26 January 2017 at 06:32 AM EST. 33 Comments Performance Improvements Intel Sends In Final Batch Of DRM Features For KDE fans not interested in setting up a KDE-based Linux distribution on For Linux 4.11: DP MST Audio, HuC your own laptop and worrying about potential graphics driver bugs with Firmware Plasma or other possible headaches, there is now a "KDE laptop" backed by the KDE community. Wine-Staging 2.0 Rolls Out For Experimental Users: Vulkan, D3D11, Etc KDE has teamed up with Spanish computer hardware retailer Slimbook to Chrome 56 Released With WebGL 2.0 By offer the KDE Slimbook. It's an Intel laptop preloaded with KDE Neon and thus running the Default, FLAC Support latest KDE Frameworks 5 + Plasma 5 experience. This isn't a laptop running Coreboot or the GNOME's Mutter Rolls Out New Monitor like or any other real innovations besides just being pre-loaded with KDE Neon and tested Configuration System by KDE Developers to ensure you don't run into any hardware troubles, etc. NetworkManager 1.6 Released 10-bit HEVC Decoding Support Being The KDE Slimbook currently comes in two varieties with either a Core i5 6200U or Core i7 Worked On For RadeonSI Gallium3D 6500U processor, 4 / 8 / 16GB RAM options, Intel Graphics HD 520, SSD storage, 13.3-inch 1080p screen, and a two-year warranty.
  • Current Status of OFED in SUSE Linux Enterprise Server

    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
  • Name Synopsis Description Arguments Options

    Name Synopsis Description Arguments Options

    W3M(1) General Commands Manual W3M(1) NAME w3m − a text based web browser and pager SYNOPSIS w3m [OPTION]... [ file | URL ]... DESCRIPTION w3m is a text based browser which can display local or remote web pages as well as other documents. It is able to process HTML tables and frames but it ignores JavaScript and Cascading Style Sheets. w3m can also serveasapager for text files named as arguments or passed on standard input, and as a general purpose directory browser. w3m organizes its content in buffers or tabs, allowing easy navigation between them. With the w3m-img extension installed, w3m can display inline graphics in web pages. And whenever w3m’s HTML rendering capabilities do not meet your needs, the target URL can be handed overtoagraphical browser with a single command. Forhelp with runtime options, press “H” while running w3m. ARGUMENTS When givenone or more command line arguments, w3m will handle targets according to content type. For web, w3m gets this information from HTTP headers; for relative orabsolute file system paths, it relies on filenames. With no argument, w3m expects data from standard input and assumes “text/plain” unless another MIME type is givenbythe user. If provided with no target and no fallback target (see for instance option −v below), w3m will exit with us- age information. OPTIONS Command line options are introduced with a single “−” character and may takeanargument. General options −B with no other target defined, use the bookmark page for startup −M monochrome display −no-mouse deactivate mouse support −num display each line’snumber −N distribute multiple command line arguments to tabs.
  • Linux Software User's Manual

    Linux Software User's Manual

    New Generation Systems (NGS) Linux Software User’s Manual Version 1.0, September 2019 www.moxa.com/product © 2019 Moxa Inc. All rights reserved. New Generation Systems (NGS) Linux Software User’s Manual The software described in this manual is furnished under a license agreement and may be used only in accordance with the terms of that agreement. Copyright Notice © 2019 Moxa Inc. All rights reserved. Trademarks The MOXA logo is a registered trademark of Moxa Inc. All other trademarks or registered marks in this manual belong to their respective manufacturers. Disclaimer Information in this document is subject to change without notice and does not represent a commitment on the part of Moxa. Moxa provides this document as is, without warranty of any kind, either expressed or implied, including, but not limited to, its particular purpose. Moxa reserves the right to make improvements and/or changes to this manual, or to the products and/or the programs described in this manual, at any time. Information provided in this manual is intended to be accurate and reliable. However, Moxa assumes no responsibility for its use, or for any infringements on the rights of third parties that may result from its use. This product might include unintentional technical or typographical errors. Changes are periodically made to the information herein to correct such errors, and these changes are incorporated into new editions of the publication. Technical Support Contact Information www.moxa.com/support Moxa Americas Moxa China (Shanghai office) Toll-free: 1-888-669-2872 Toll-free: 800-820-5036 Tel: +1-714-528-6777 Tel: +86-21-5258-9955 Fax: +1-714-528-6778 Fax: +86-21-5258-5505 Moxa Europe Moxa Asia-Pacific Tel: +49-89-3 70 03 99-0 Tel: +886-2-8919-1230 Fax: +49-89-3 70 03 99-99 Fax: +886-2-8919-1231 Moxa India Tel: +91-80-4172-9088 Fax: +91-80-4132-1045 Table of Contents 1.
  • The Elinks Manual the Elinks Manual Table of Contents Preface

    The Elinks Manual the Elinks Manual Table of Contents Preface

    The ELinks Manual The ELinks Manual Table of Contents Preface.......................................................................................................................................................ix 1. Getting ELinks up and running...........................................................................................................1 1.1. Building and Installing ELinks...................................................................................................1 1.2. Requirements..............................................................................................................................1 1.3. Recommended Libraries and Programs......................................................................................1 1.4. Further reading............................................................................................................................2 1.5. Tips to obtain a very small static elinks binary...........................................................................2 1.6. ECMAScript support?!...............................................................................................................4 1.6.1. Ok, so how to get the ECMAScript support working?...................................................4 1.6.2. The ECMAScript support is buggy! Shall I blame Mozilla people?..............................6 1.6.3. Now, I would still like NJS or a new JS engine from scratch. .....................................6 1.7. Feature configuration file (features.conf).............................................................................7
  • Suse Linux Enterprise Server 12 - Administration Guide Pdf, Epub, Ebook

    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.
  • Auditing Overhead, Auditing Adaptation, and Benchmark Evaluation in Linux Lei Zeng1, Yang Xiao1* and Hui Chen2

    Auditing Overhead, Auditing Adaptation, and Benchmark Evaluation in Linux Lei Zeng1, Yang Xiao1* and Hui Chen2

    SECURITY AND COMMUNICATION NETWORKS Security Comm. Networks 2015; 8:3523–3534 Published online 4 June 2015 in Wiley Online Library (wileyonlinelibrary.com). DOI: 10.1002/sec.1277 RESEARCH ARTICLE Auditing overhead, auditing adaptation, and benchmark evaluation in Linux Lei Zeng1, Yang Xiao1* and Hui Chen2 1 Department of Computer Science, The University of Alabama, Tuscaloosa 35487-0290, AL, U.S.A. 2 Department of Mathematics and Computer Science, Virginia State University, Petersburg 23806, VA, U.S.A. ABSTRACT Logging is a critical component of Linux auditing. However, our experiments indicate that the logging overhead can be significant. The paper aims to leverage the performance overhead introduced by Linux audit framework under various us- age patterns. The study on the problem leads to an adaptive audit-logging mechanism. Many security incidents or other im- portant events are often accompanied with precursory events. We identify important precursory events – the vital signs of system activity and the audit events that must be recorded. We then design an adaptive auditing mechanism that increases or reduces the type of events collected and the frequency of events collected based upon the online analysis of the vital-sign events. The adaptive auditing mechanism reduces the overall system overhead and achieves a similar level of protection on the system and network security. We further adopt LMbench to evaluate the performance of key operations in Linux with compliance to four security standards. Copyright © 2015 John Wiley & Sons, Ltd. KEYWORDS logging; overhead; Linux; auditing *Correspondence Yang Xiao, Department of Computer Science, The University of Alabama, 101 Houser Hall, PO Box 870290, Tuscaloosa 35487-0290, AL, U.S.A.
  • SUSE® Linux Enterprise Server ("SLES ™")11 SP1 Novell® Software License Agreement

    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.
  • A U T O M at E D I N S Ta L L At

    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.