DOCSLIB.ORG

Kernel Module Packages Manual for SUSE Linux Enterprise 12 SP2 Or Later and SUSE Linux Enterprise 15

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Kernel Module Packages Manual for SUSE Linux Enterprise 12 SP2 Or Later and SUSE Linux Enterprise 15 SUSE Best Practices Kernel Module Packages Manual for SUSE Linux Enterprise 12 SP2 or later and SUSE Linux Enterprise 15 SUSE Linux Enterprise 12 SP2+, 15 Document Owner: Ann Davis, Senior Software Engineer, SUSE Kernel Module Packages Manual for SUSE Linux Enterprise 12 SP2 or later and SUSE Linux 1 Enterprise 15 SUSE-based distributions use the RPM Package Manager for software management. As such, any external kernel modules (these are kernel modules not included in SUSE kernel packages) should be packaged in RPM packages. These RPMs should be built in accordance with specic guidelines to ensure that the resulting Kernel Module Packages (KMPs) can be installed and updated appropriately, in synchronization with kernel updates. This document species the requirements for RPM packages that contain kernel modules, and describes the processes surrounding those packages including building, signing, installing and upgrading. A complete example is given and explained. This version of the Kernel Module Packages Manual applies to SUSE Linux Enterprise Server 12 (Service Pack 2 and later), and SUSE Linux Enterprise Server 15, and all products based on these versions. Publication Date: July 31, 2019 Contents 1 Scope 4 2 Background 4 3 Kernel Packages 6 4 Kernel Modules 7 5 Kernel Module Packages 8 6 RPM Provides and Requires 12 7 Building Kernel Module Packages 12 8 Signing 14 9 Deploying Kernel Module Packages 18 10 System Installation and Kernel Module Packages 18 Kernel Module Packages Manual for SUSE Linux Enterprise 12 SP2 or later and SUSE Linux 2 Enterprise 15 11 Kernel Updates and Kernel Module Packages 19 12 Appendix A: Sample Source for suse-hello Kernel Module Package 20 13 Appendix B: Changes and References 22 14 Legal Notice 23 15 GNU Free Documentation License 24 Kernel Module Packages Manual for SUSE Linux Enterprise 12 SP2 or later and SUSE Linux 3 Enterprise 15 1 Scope This version of the Kernel Module Packages Manual applies to: SUSE Linux Enterprise Server 12 Service Pack 2 and later or SUSE Linux Enterprise Desktop 12 Service Pack 2 and later, and all products based on these versions SUSE Linux Enterprise Server 15 and SUSE Linux Enterprise Desktop 15 (along with service packs) All products and extensions based on SUSE Linux Enterprise Server 12 SP2 or later and SUSE Linux Enterprise Server 15 Developers who want to build for SUSE Linux Enterprise Server versions before SUSE Linux Enterprise Server 12 SP2 should use previous versions of this document SUSE SolidDriver Documentation: Kernel Module Packages Manual for Code 11 (https://documentation.suse.com/ sbp/all/html/SBP-KMP-Manual/index.html) . Appendix B provides a list of changes that have been made to this document to accommodate new features. 2 Background The Linux kernel supports adding functionality at runtime through kernel-loadable modules. It includes more than 1500 modules, about 75 percent of which are hardware drivers. These modules are shipped as part of the kernel packages. In some cases it is desirable to add additional modules or replace existing ones. For example, a driver for a particular storage controller that was not available at the time of product release might be added later to support new hardware. Kernel modules interact with the kernel by the means of exported symbols, in a way similar to how user space binaries use shared libraries. The /proc/kallsyms le lists all symbols currently known to the kernel. To ensure that the kernel and modules refer to the same symbols, a version checksum ( modversion ) is added to each symbol. The checksum is computed from the symbol's type: in the case of function symbols, the checksum is determined by the function's parameters and return type. Kernel Module Packages Manual for SUSE Linux Enterprise 12 SP2 or later and SUSE Linux 4 Enterprise 15 When any of a function's parameters or the return type changes, the checksum changes as well. This includes all the data types involved recursively: If a function takes a struct task_struct as parameter and struct task_struct includes a eld of type struct dentry, then a change to struct dentry will cause the symbol's version checksum to change as well. Symbol version checksums for dierent kernel avors (for example kernel- default versus kernel-xen) will not match, and symbol versions of the same kernel package on dierent architectures will not match either. This mechanism ensures that the kernel and kernel modules agree on the types of data structures that they use to communicate. Unless symbol version checking is disabled, modules will load only if the checksums of the symbols they use match the checksums of the symbols that the kernel exports. The exported symbols and their version checksums comprise the kernel Application Binary Interface (kABI). When an updated kernel includes kABI changes, kernel modules that use any modied symbols must be updated as well. During their multi-year lifecycle, products like SUSE Linux Enterprise Server undergo continuous changes. Dierent kinds of updates like service packs (SPs), maintenance/security updates, and customer-specic updates (Program Temporary Fixes) are released. The Application Binary Interface (ABI) between the kernel and kernel modules is volatile. Some kernel updates will change the kernel ABI (kABI) by adding or removing exported symbols, or existing symbol checksums can change in a kernel update because of changes in data structures they reference. SUSE strives to keep the kernel ABI stable in maintenance and security and customer-specic updates, but sometimes changes cannot be avoided. In service packs, SUSE reserves the right to introduce more intrusive changes, which increases the likelihood of ABI changes. SUSE believes that the added exibility outweighs the disadvantages of breaking older modules. For full discussion of this topic, see the documentation SUSE SolidDriver Documentation: SUSE Kernel ABI Stability (https://drivers.suse.com/doc/SolidDriver/SUSE_Kernel_ABI_Stability.html) and The Linux Kernel Driver Interface (http://www.kroah.com/log/linux/stable_api_nonsense.html) from Greg Kroah-Hartman (also provided as stable_api_nonsense.txt in the upstream kernel source tree). SUSE Linux Enterprise-based operating systems include technology to ensure that kernel modules can be reused or updated in synchronization with kernel updates. To use this technology, kernel modules must be packaged into Kernel Module Packages (KMPs) as dened in this document. Kernel Module Packages Manual for SUSE Linux Enterprise 12 SP2 or later and SUSE Linux 5 Enterprise 15 3 Kernel Packages Each product based on SUSE Linux Enterprise 12 SP2 or SUSE Linux Enterprise 15 contains a set of kernel packages that share the same version and release number; they are built from the same kernel sources. These packages are: kernel-FLAVOR , kernel-FLAVOR-base The binary kernel packages. Each architecture has its own set of kernel avors (for example kernel-default , kernel-debug , etc.). These are the packages that the kernel modules will be used with. The kernel-FLAVOR-base packages are subsets of the kernel-FLAVOR packages, intended for use with minimal installs. They are not installed by default. kernel-source The kernel source tree, generated by unpacking the vanilla kernel sources and applying all necessary patches. Although the kernel-FLAVOR packages technically are not built from the kernel-source package, they are built from the same source tree. This tree should be used for module building. kernel-devel , kernel-macros Kernel-level headers, makeles, and RPM macros and templates required for development of external kernel modules. kernel-syms , kernel-FLAVOR-devel Kernel symbol version information for compiling external modules. The kernel-FLAVOR-devel package is required for building external modules. If this package is not used, the resulting modules will be missing symbol version information, which will cause them to break during kernel updates. The kernel-syms package is a placeholder package which depends on the kernel-FLAVOR-devel packages for all kernel avors. Kernel Module Packages Manual for SUSE Linux Enterprise 12 SP2 or later and SUSE Linux 6 Enterprise 15 For more information, refer to the document “Working With The SUSE 2.6.x and 3.x Kernel Sources” from Andreas Gruenbacher and Michal Marek. This document is provided as README.SUSE in the SUSE kernel-source package. 4 Kernel Modules Documentation on general kernel module building can be found in abundance on the Internet. Two good lectures are: Peter Jay Salzman, Michael Burian, Ori Pomerantz: The Linux Kernel Module Programming Guide, http://www.tldp.org/LDP/lkmpg/2.6/html/index.html Jonathan Corbet, Alessandro Rubini, Greg Kroah-Hartman: Linux Device Drivers, Third Edition, February 2005, http://www.oreilly.com/catalog/linuxdrive3/ (also available online at http://lwn.net/Kernel/LDD3/ ) SUSE-specic information is found in the above-mentioned README.SUSE in the kernel- source package. When built, kernel module binaries are installed below /lib/modules/VERSION-RELEASE- FLAVOR on the le system (example: /lib/modules/4.4.73-5-default for the SUSE Linux Enterprise Server 12 SP3 kernel-default-4.4.73-5 package). Dierent kernels have dierent module directories, and will usually not see each other's modules. Update modules are modules intended to replace or augment the modules that are provided in the kernel packages. Update modules must be stored below the /lib/modules/VERSION- RELEASE-FLAVOR/updates/ directory. Modules in the updates/ directory have precedence over other modules with the same name. Never replace modules from the kernel package by overwriting les: this would lead to inconsistencies between the le system and the RPM database. Note: Where to Store Modules Modules intended to take precedence over in-kernel modules of the same name should be stored below /lib/modules/VERSION-RELEASE-FLAVOR/updates/ . Other add-on modules can be stored below /lib/modules/VERSION-RELEASE-FLAVOR/extra/ .
Load more

Recommended publications
  • Creating Rpms Guide
    CREATING RPMS (Student version) v1.0 Featuring 36 pages of lecture and a 48 page lab exercise This docu m e n t serves two purpose s: 1. Representative sample to allow evaluation of our courseware manuals 2. Make available high quality RPM documentation to Linux administrators A bout this m aterial : The blue background you see simulates the custom paper that all Guru Labs course w are is printed on. This student version does not contain the instructor notes and teaching tips present in the instructor version. For more information on all the features of our unique layout, see: http://ww w . g urulabs.co m /courseware/course w are_layout.php For more freely available Guru Labs content (and the latest version of this file), see: http://www.gurulabs.co m/goodies/ This sample validated on: Red Hat Enterprise Linux 4 & Fedora Core v3 SUSE Linux Enterprise Server 9 & SUSE Linux Professional 9.2 About Guru Labs: Guru Labs is a Linux training company started in 199 9 by Linux experts to produce the best Linux training and course w are available. For a complete list, visit our website at: http://www.gurulabs.co m/ This work is copyrighted Guru Labs, L.C. 2005 and is licensed under the Creative Common s Attribution- NonCom mer cial- NoDerivs License. To view a copy of this license, visit http://creativecom m o n s.org/licenses/by- nc- nd/2.0/ or send a letter to Creative Commons, 559 Nathan Abbott Way, Stanford, California 943 0 5, USA. Guru Labs 801 N 500 W Ste 202 Bountiful, UT 84010 Ph: 801-298-5227 WWW.GURULABS.COM Objectives: • Understand
    [Show full text]
  • Current Status of OFED in SUSE Linux Enterprise Server
    Current Status of OFED in SUSE Linux Enterprise Server John Jolly Senior Software Engineer SUSE Agenda 2 λAbout SUSE λAbout SUSE Linux Enterprise Server λOFED Integration into SLES λFuture Direction of OFED in SLES SUSE and the Attachmate Group λSUSE , headquartered in Nürnberg / Germany, λis an independently operating business unit of λThe Attachmate Group, Inc. λThe Attachmate Group is a privately held λ1 billion+ $ revenue software company λwith four brands: •Cloud Infrastructure •Enterprise Computing •Integrated Systems SUSE® Linux Enterprise How We Build It Online Repository Source Package Image OBS OBS user submits source to OBS and gets a product SUSE® Linux Enterprise Server 12 Lifecyle Model •13-year lifecycle (10 years general support, 3 years extended support) •5-year lifecycle per Service Pack (2 years general + 3 years extended support) •Long Term Service Pack Support (LTSS) available for all versions, including GA http://www.suse.com/lifecycle/ Unique Tools Included λAppArmor Security Framework -Application confinement λFree High Availability Extension -Cluster Framework, Cluster FS, DRBD, GEO-cluster* λYaST2 systems management -Install, deploy, and configure every aspect of the server λSubscription Management Tool -Subscription and patch management, proxy/mirroring/staging λStarter System for System z -A pre-built installation server, deployable with z/VM tools Features of SLES 12 λLinux Kernel 3.12 λOnly 64-bit kernel -Support of 32-bit application through execution environment λYaST modules written in Ruby λOFED 3.12 -Significant
    [Show full text]
  • SUSE® Linux Enterprise Server ("SLES ™")11 SP1 Novell® Software License Agreement
    SUSE® Linux Enterprise Server ("SLES ™")11 SP1 Novell® Software License Agreement PLEASE READ THIS AGREEMENT CAREFULLY. BY INSTALLING OR OTHERWISE USING THE SOFTWARE (INCLUDING ITS COMPONENTS), YOU AGREE TO THE TERMS OF THIS AGREEMENT. IF YOU DO NOT AGREE WITH THESE TERMS, DO NOT DOWNLOAD, INSTALL OR USE THE SOFTWARE. RIGHTS AND LICENSES This Novell Software License Agreement (“Agreement”) is a legal agreement between You (an entity or a person) and Novell, Inc. (“Novell”). The software product identified in the title of this Agreement, any media and accompanying documentation (collectively the “Software”) is protected by the copyright laws and treaties of the United States (“U.S.”) and other countries and is subject to the terms of this Agreement. Any update or support release to the Software that You may download or receive that is not accompanied by a license agreement expressly superseding this Agreement is Software and governed by this Agreement. If the Software is an update or support release, then You must have validly licensed the version and quantity of the Software being updated or supported in order to install or use the update or support release. The Software is a modular operating system comprised of numerous components that may be accompanied by separate license terms. The Software is a collective work of Novell; although Novell does not own the copyright to every component of the Software, Novell owns the collective work copyright for the Software. Most of the components are open source packages, developed independently, and accompanied by separate license terms. Your license rights with respect to individual components accompanied by separate license terms are defined by those terms; nothing in this agreement shall restrict, limit, or otherwise affect any rights or obligations You may have, or conditions to which You may be subject, under such license terms; however, if You distribute copies of any component independent of the Software, You must remove all Novell trademarks, trade dress, and logos from each copy.
    [Show full text]
  • SUSE Linux Enterprise Server 11 SP4 System Analysis and Tuning Guide System Analysis and Tuning Guide SUSE Linux Enterprise Server 11 SP4
    SUSE Linux Enterprise Server 11 SP4 System Analysis and Tuning Guide System Analysis and Tuning Guide SUSE Linux Enterprise Server 11 SP4 Publication Date: September 24, 2021 SUSE LLC 1800 South Novell Place Provo, UT 84606 USA https://documentation.suse.com Copyright © 2006– 2021 SUSE LLC and contributors. All rights reserved. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or (at your option) version 1.3; with the Invariant Section being this copyright notice and license. A copy of the license version 1.2 is included in the section entitled “GNU Free Documentation License”. For SUSE trademarks, see http://www.suse.com/company/legal/ . All other third party trademarks are the property of their respective owners. A trademark symbol (®, ™ etc.) denotes a SUSE or Novell trademark; an asterisk (*) denotes a third party trademark. All information found in this book has been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. Neither SUSE LLC, its aliates, the authors nor the translators shall be held liable for possible errors or the consequences thereof. Contents About This Guide xi 1 Available Documentation xii 2 Feedback xiv 3 Documentation Conventions xv I BASICS 1 1 General Notes on System Tuning 2 1.1 Be Sure What Problem to Solve 2 1.2 Rule Out Common Problems 3 1.3 Finding the Bottleneck 3 1.4 Step-by-step Tuning 4 II SYSTEM MONITORING 5 2 System Monitoring Utilities 6 2.1 Multi-Purpose Tools 6 vmstat 7
    [Show full text]
  • CIT 470: Advanced Network and System Administration Slide #1 CIT 470: Advanced Network and System Administration Slide #2
    Topics 1. The Problem of Software Installation 2. Package Management Systems CIT 470: Advanced Network and 3. Using RPM System Administration 4. Finding RPMs Package Management 5. Building RPMs CIT 470: Advanced Network and System Administration Slide #1 CIT 470: Advanced Network and System Administration Slide #2 Software Installation What’s the problem? 1. Customization What prerequisites does your software have? Select options like language. What prereqs do your prereq packages have? Select file set. How do you handle conflicts? What if two programs install/modify same file? 2. Install new files in appropriate locations. Does your install work on every type of computer? 3. Modify existing configuration files. How do you handle upgrades? 4. Make software available to user. What if user has customized configuration? Shell configuration (PATH, etc.) What if ownerships/permissions have changed? GUI configuration (menu, icons, etc.) What if user needs old and new versions? How do you uninstall software? CIT 470: Advanced Network and System Administration Slide #3 CIT 470: Advanced Network and System Administration Slide #4 Package Manager Features UNIX Package Management Systems • Build management. deb: Debian system uses dpkg and APT. • Dependency tracking. pkgadd: Solaris packaging system. • Querying. portage: Gentoo uses with emerge. • Reversibility. ports: BSD ports system. • Verification. RPM: Redhat packaging system. • Version control. tgz: Tarballs used by Slackware. CIT 470: Advanced Network and System Administration Slide #5 CIT 470: Advanced Network and System Administration Slide #6 1 RPM RPM Package Names RPM Package Manager <name>-<version>-<release>.<arch>.rpm – Originally stood for Red Hat Package Manager – Came with Red Hat Linux 2.0 in 1995.
    [Show full text]
  • SUSE Openstack Cloud
    Product Flyer SUSE OpenStack Cloud SUSE OpenStack Cloud The digital economy is driving the need for fast IT transformation. Is your business able to keep up? The pace of change can be painful to manage, but it also creates new opportunities. SUSE® OpenStack Cloud provides a Software-Defined Infrastructure-as- a-Service (IaaS) for your data center, with access to pools of IT resources to quickly deploy and run applications. This gives you the flexibility to respond quickly and easily to new demands, providing the ideal platform for increased innovation, while helping you to control and reduce costs. SUSE OpenStack Cloud Product Overview most vibrant open source community at a Glance: SUSE OpenStack Cloud is the open source support, OpenStack is ideal for Open source cloud solution of choice for cloud solution of choice for enterprise developing new, innovative business enterprise businesses. business, helping you respond quickly to workloads and DevOps environments today’s ever-changing business-critical as well as for transforming traditional + Flexibility to respond quickly demands. data centers. SUSE OpenStack Cloud + Increase innovation leveraging the latest enables you to take full advantage technologies + Control and reduce costs SUSE OpenStack Cloud enables you to: of new business opportunities and rapidly evolving technology by Deliver improved agility, innovation enabling you to quickly deploy and and faster time to value to conquer easily manage an OpenStack private today’s competitive, market and cloud infrastructure. With a
    [Show full text]
  • SUSE Linux Enterprise Server 12 SP4 System Analysis and Tuning Guide System Analysis and Tuning Guide SUSE Linux Enterprise Server 12 SP4
    SUSE Linux Enterprise Server 12 SP4 System Analysis and Tuning Guide System Analysis and Tuning Guide SUSE Linux Enterprise Server 12 SP4 An administrator's guide for problem detection, resolution and optimization. Find how to inspect and optimize your system by means of monitoring tools and how to eciently manage resources. Also contains an overview of common problems and solutions and of additional help and documentation resources. 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 xii 1 Available Documentation xiii
    [Show full text]
  • Opensuse Leap to SLES: More Than the Sum of Its Parts
    openSUSE Leap to SLES: More Than The Sum Of Its Parts... Session TUT-1418 Udo Seidel Jeff Lindholm Tech-Writer and Enterprise Architect Sales Engineering Manager Amadeus SUSE [email protected] [email protected] 1 • Udo Seidel • Jeff Lindholm – SUSE • Teacher for Math and Physics • Detroit, MI USA • Linux and Open Source since 1996 • SUSE Evangelist since 2004 • Linux • Sales Engineering Manager • Software Defined Storage • OpenSUSE Community supporter • Openstack • Technology Focus • Container • Cloud Native Infrastructure • Raspberry Pi and Co • Application Transformation • … • Enterprise Linux • Enterprise Architect and Tech-Writer 2 Agenda 1. DevOPS Experience – Developer Use Case 2. OpenSUSE Community – Flexible Developer Platform 1. OpenSUSE Tumbleweed – Rolling Release 2. OpenSUSE Leap 15 – Stable Release 3. SUSE Linux Enterprise Server 15 4. LEAP SLE Interoperability and Supported Migration Use Cases 5. Demonstration – Leap Migration 6. Questions and Answers 3 4 SUSE Solutions For DevOps A suite of flexible, modular open source solutions CODE PLAN DEPLOY OBS, PackageHub, SUSE SUSE Linux Enterprise SUSE Application Delivery, Manager, Portus, GitHub openSUSE SUSE Public Cloud, SUSE Manager, Salt, Kubernetes BUILD OBS, SUSE Studio, SUSE Manager, KIWI, Docker open source project OPERATE & MONITOR SUSE Manager, SUSE Enterprise Storage, SUSE Application Delivery, TEST & RELEASE Kubernetes openQA, Jenkins 5 SUSE & openSUSE – Working Together Stable code and contributions Mutual collaboration Upstream innovations 6 These common elements are core to all openSUSE and SUSE distributions • YaST • openSUSE Build Service • Stability and testing - openQA 7 The openSUSE Distributions 8 openSUSE Tumbleweed • The Tumbleweed distribution is a pure rolling release version of openSUSE containing the latest stable versions of all software instead of relying on rigid periodic release cycles.
    [Show full text]
  • UNIX History Page 1 Tuesday, December 10, 2002 7:02 PM
    UNIX History Page 1 Tuesday, December 10, 2002 7:02 PM CHAPTER 1 UNIX Evolution and Standardization This chapter introduces UNIX from a historical perspective, showing how the various UNIX versions have evolved over the years since the very first implementation in 1969 to the present day. The chapter also traces the history of the different attempts at standardization that have produced widely adopted standards such as POSIX and the Single UNIX Specification. The material presented here is not intended to document all of the UNIX variants, but rather describes the early UNIX implementations along with those companies and bodies that have had a major impact on the direction and evolution of UNIX. A Brief Walk through Time There are numerous events in the computer industry that have occurred since UNIX started life as a small project in Bell Labs in 1969. UNIX history has been largely influenced by Bell Labs’ Research Editions of UNIX, AT&T’s System V UNIX, Berkeley’s Software Distribution (BSD), and Sun Microsystems’ SunOS and Solaris operating systems. The following list shows the major events that have happened throughout the history of UNIX. Later sections describe some of these events in more detail. 1 UNIX History Page 2 Tuesday, December 10, 2002 7:02 PM 2 UNIX Filesystems—Evolution, Design, and Implementation 1969. Development on UNIX starts in AT&T’s Bell Labs. 1971. 1st Edition UNIX is released. 1973. 4th Edition UNIX is released. This is the first version of UNIX that had the kernel written in C. 1974. Ken Thompson and Dennis Ritchie publish their classic paper, “The UNIX Timesharing System” [RITC74].
    [Show full text]
  • What's up with SUSE?
    March 11, 2021 What’s up with SUSE? Picture Welcome to TriLug! 1.History of SUSE 2.SUSE Linux Distros 3.Other Products 4.Tease about Rancher Copyright © SUSE 2021 2 Who is this guy? • Joined SUSE in March 2018 • Formerly with Western Digital, SanDisk, Fusion-io, SteelEye Tech.,Sun Microsystems, Lockheed • MS Computer Science, West Virginia • Attending TriLug since 2007 • Takes care of his wife's chickens.... Dwain Sims Sales Engineer [email protected] [email protected] +1 919-480-1774 Copyright © SUSE 2021 3 What means SUSE? Copyright © SUSE 2021 4 S.u.S.E. Roland Dyroff, Thomas Fehr, Burchard Steinbild and Hubert Mantel found S.u.S.E., 1992. SUSE is a German acronym for "Software und System-Entwicklung" (software and systems development). Softlanding Linux System (SLS) was one of the earliest Liunx disros. (Slackware was initially based on SLS) First true S.u.S.E. Liunx distro was 4.2, in 1996. Copyright © SUSE 2021 5 How is SUSE pronounced? Copyright © SUSE 2021 6 Brief History of SUSE Copyright © SUSE 2021 7 A BOUT S US E 28 Years of Leadership in True Open Source 1992 to 2000 2001 to 2010 2011 to Present 2017 to Present Becoming strategic partner of From Linux Pioneer to The Pioneering Enabling an Always Open SAP and building a strong Software-Defined Years Data Center ecosystem Infrastructure and Edge Important Milestones 1992 2010 2020 SUSE brings Linux to the Linux-based solution Acquires enterprise with AWS Rancher Labs 2020 2008 2019 Partnership with SUSE celebrates first year of Joint innovation with SAP EQT independence 8 Copyright © SUSE 2020.
    [Show full text]
  • Forcepoint DLP Supported File Formats and Size Limits
    Forcepoint DLP Supported File Formats and Size Limits Supported File Formats and Size Limits | Forcepoint DLP | v8.8.1 This article provides a list of the file formats that can be analyzed by Forcepoint DLP, file formats from which content and meta data can be extracted, and the file size limits for network, endpoint, and discovery functions. See: ● Supported File Formats ● File Size Limits © 2021 Forcepoint LLC Supported File Formats Supported File Formats and Size Limits | Forcepoint DLP | v8.8.1 The following tables lists the file formats supported by Forcepoint DLP. File formats are in alphabetical order by format group. ● Archive For mats, page 3 ● Backup Formats, page 7 ● Business Intelligence (BI) and Analysis Formats, page 8 ● Computer-Aided Design Formats, page 9 ● Cryptography Formats, page 12 ● Database Formats, page 14 ● Desktop publishing formats, page 16 ● eBook/Audio book formats, page 17 ● Executable formats, page 18 ● Font formats, page 20 ● Graphics formats - general, page 21 ● Graphics formats - vector graphics, page 26 ● Library formats, page 29 ● Log formats, page 30 ● Mail formats, page 31 ● Multimedia formats, page 32 ● Object formats, page 37 ● Presentation formats, page 38 ● Project management formats, page 40 ● Spreadsheet formats, page 41 ● Text and markup formats, page 43 ● Word processing formats, page 45 ● Miscellaneous formats, page 53 Supported file formats are added and updated frequently. Key to support tables Symbol Description Y The format is supported N The format is not supported P Partial metadata
    [Show full text]
  • Installation Quick Start Installation Quick Start SUSE Linux Enterprise Server for SAP Applications 15 SP1
    SUSE Linux Enterprise Server for SAP Applications 15 SP1 Installation Quick Start Installation Quick Start SUSE Linux Enterprise Server for SAP Applications 15 SP1 Publication Date: September 24, 2021 SUSE LLC 1800 South Novell Place Provo, UT 84606 USA https://documentation.suse.com Copyright © 2010–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 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 v 1 What Is SUSE Linux Enterprise Server for SAP Applications? 1 1.1 Software Components 2 2 Planning the Installation 4 2.1 Hardware Requirements 4 2.2 Installation Image 5 2.3 Offline Migration 5 2.4 Overview of the Installation Workflow 6 2.5 Required Data for Installing 6 2.6 Partitioning 8 Partitioning for the
    [Show full text]