DOCSLIB.ORG

Administration Guide Administration Guide SUSE Linux Enterprise Server 15 SP1

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

SUSE Linux Enterprise Server 15 SP1 Administration Guide Administration Guide SUSE Linux Enterprise Server 15 SP1 Covers system administration tasks like maintaining, monitoring and customizing an initially installed system. 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 xxii 1 Available Documentation xxiii 2 Giving Feedback xxv 3 Documentation Conventions xxv 4 Product Life Cycle and Support xxvii Support Statement for SUSE Linux Enterprise Server xxviii • Technology Previews xxix I COMMON TASKS 1 1 Bash and Bash Scripts 2 1.1 What is “The Shell”? 2 Bash Configuration Files 2 • The Directory Structure 5 1.2 Writing Shell Scripts 9 1.3 Redirecting Command Events 10 1.4 Using Aliases 11 1.5 Using Variables in Bash 11 Using Argument Variables 13 • Using Variable Substitution 13 1.6 Grouping and Combining Commands 14 1.7 Working with Common Flow Constructs 15 The if Control Command 15 • Creating Loops with the for Command 16 1.8 For More Information 16 iii Administration Guide 2 sudo 17 2.1 Basic sudo Usage 17 Running a Single Command 17 • Starting a Shell 18 • Environment Variables 19 2.2 Configuring sudo 19 Editing the Configuration Files 20 • Basic sudoers Configuration Syntax 20 • Rules in sudoers 22 2.3 Common Use Cases 24 Using sudo without root Password 24 • Using sudo with X.Org Applications 25 2.4 More Information 26 3 YaST Online Update 27 3.1 The Online Update Dialog 28 3.2 Installing Patches 29 3.3 Automatic Online Update 30 4 YaST 33 4.1 Advanced Key Combinations 33 5 YaST in Text Mode 35 5.1 Navigation in Modules 36 5.2 Advanced Key Combinations 38 5.3 Restriction of Key Combinations 38 5.4 YaST Command Line Options 39 Installing Packages from the Command Line 39 • Starting Individual Modules 39 • Command Line Parameters of YaST Modules 40 iv Administration Guide 6 Managing Software with Command Line Tools 64 6.1 Using Zypper 64 General Usage 64 • Using Zypper Subcommands 66 • Installing and Removing Software with Zypper 66 • Updating Software with Zypper 71 • Identifying Processes and Services Using Deleted Files 74 • Managing Repositories with Zypper 76 • Querying Repositories and Packages with Zypper 78 • Showing Life Cycle Information 80 • Configuring Zypper 81 • Troubleshooting 81 • Zypper Rollback Feature on Btrfs File System 82 • For More Information 82 6.2 RPM—the Package Manager 82 Verifying Package Authenticity 83 • Managing Packages: Install, Update, and Uninstall 83 • Delta RPM Packages 85 • RPM Queries 85 • Installing and Compiling Source Packages 88 • Compiling RPM Packages with build 90 • Tools for RPM Archives and the RPM Database 91 7 System Recovery and Snapshot Management with Snapper 92 7.1 Default Setup 93 Types of Snapshots 94 • Directories That Are Excluded from Snapshots 94 • Customizing the Setup 95 7.2 Using Snapper to Undo Changes 99 Undoing YaST and Zypper Changes 100 • Using Snapper to Restore Files 105 7.3 System Rollback by Booting from Snapshots 107 Snapshots after Rollback 109 • Accessing and Identifying Snapshot Boot Entries 109 • Limitations 111 7.4 Enabling Snapper in User Home Directories 112 Installing pam_snapper and Creating Users 113 • Removing Users 113 • Manually Enabling Snapshots in Home Directories 114 7.5 Creating and Modifying Snapper Configurations 114 Managing Existing Configurations 116 v Administration Guide 7.6 Manually Creating and Managing Snapshots 119 Snapshot Metadata 119 • Creating Snapshots 121 • Modifying Snapshot Metadata 122 • Deleting Snapshots 122 7.7 Automatic Snapshot Clean-Up 124 Cleaning Up Numbered Snapshots 124 • Cleaning Up Timeline Snapshots 126 • Cleaning Up Snapshot Pairs That Do Not Differ 127 • Cleaning Up Manually Created Snapshots 128 • Adding Disk Quota Support 128 7.8 Showing Exclusive Disk Space Used by Snapshots 129 7.9 Frequently Asked Questions 131 8 Live kernel patching with KLP 133 8.1 Advantages of Kernel Live Patching 133 8.2 Kernel Live Patching overview 133 Kernel Live Patching scope 135 • Kernel Live Patching limitations 135 8.3 Activating Kernel Live Patching using YaST 135 8.4 Activating Kernel Live Patching from the command line 136 8.5 Performing Kernel Live Patching 137 Checking expiration date of the live patch 137 9 Transactional Updates 138 9.1 Limitations of Technical Preview 138 9.2 Enabling transactional-update 140 9.3 Managing Automatic Updates 140 9.4 The transactional-update Command 141 9.5 Troubleshooting 143 vi Administration Guide 10 Remote Graphical Sessions with VNC 144 10.1 The vncviewer Client 144 Connecting Using the vncviewer CLI 144 • Connecting Using the vncviewer GUI 145 • Notification of Unencrypted Connections 145 10.2 Remmina: the Remote Desktop Client 145 Installation 145 • Main Window 146 • Adding Remote Sessions 146 • Starting Remote Sessions 148 • Editing, Copying, and Deleting Saved Sessions 149 • Running Remote Sessions from the Command Line 149 10.3 Configuring One-time Sessions on the VNC Server 150 Available Configurations 151 • Initiating a One-time VNC Session 152 • Configuring One-time VNC Sessions 152 10.4 Configuring Persistent VNC Server Sessions 153 VNC Session Initiated Using vncserver 154 • VNC Session Initiated Using vncmanager 155 10.5 Configuring Encryption on the VNC Server 158 11 File Copying with RSync 161 11.1 Conceptual Overview 161 11.2 Basic Syntax 161 11.3 Copying Files and Directories Locally 162 11.4 Copying Files and Directories Remotely 163 11.5 Configuring and Using an Rsync Server 163 11.6 For More Information 166 II BOOTING A LINUX SYSTEM 167 12 Introduction to the Boot Process 168 12.1 Terminology 168 vii Administration Guide 12.2 The Linux Boot Process 169 The Initialization and Boot Loader Phase 169 • The Kernel Phase 170 • The init on initramfs Phase 173 • The systemd Phase 175 13 UEFI (Unified Extensible Firmware Interface) 176 13.1 Secure Boot 176 Implementation on SUSE Linux Enterprise Server 177 • MOK (Machine Owner Key) 179 • Booting a Custom Kernel 180 • Using Non-Inbox Drivers 182 • Features and Limitations 183 13.2 For More Information 184 14 The Boot Loader GRUB 2 185 14.1 Main Differences between GRUB Legacy and GRUB 2 185 14.2 Configuration File Structure 185 The File /boot/grub2/grub.cfg 186 • The File /etc/default/ grub 187 • Scripts in /etc/grub.d 190 • Mapping between BIOS Drives and Linux Devices 191 • Editing Menu Entries during the Boot Procedure 192 • Setting a Boot Password 193 14.3 Configuring the Boot Loader with YaST 194 Boot Loader Location and Boot Code Options 196 • Adjusting the Disk Order 197 • Configuring Advanced Options 198 14.4 Differences in Terminal Usage on IBM Z 201 Limitations 201 • Key Combinations 202 14.5 Helpful GRUB 2 Commands 204 14.6 More Information 205 15 The systemd Daemon 206 15.1 The systemd Concept 206 What Is systemd 206 • Unit File 207 15.2 Basic Usage 208 Managing Services in a Running System 208 • Permanently Enabling/ Disabling Services 210 viii Administration Guide 15.3 System Start and Target Management 212 Targets Compared to Runlevels 212 • Debugging System Start- Up 215 • System V Compatibility 218 15.4 Managing Services with YaST 219 15.5 Customization of systemd 220 Customizing Unit Files 220 • Creating “Drop-in” Files 222 • Creating Custom Targets 222 15.6 Advanced Usage 223 Cleaning Temporary Directories 223 • System Log 224 • Snapshots 224 • Loading Kernel Modules 224 • Performing Actions before Loading a Service 225 • Kernel Control Groups (cgroups) 226 • Terminating Services (Sending Signals) 227 • Important Notes on the D-Bus Service 227 • Debugging Services 228 15.7 More Information 229 III SYSTEM 230 16 32-Bit and 64-Bit Applications in a 64-Bit System Environment 231 16.1 Runtime Support 231 16.2 Kernel Specifications 232 17 journalctl: Query the systemd Journal 233 17.1 Making the Journal Persistent 233 17.2 journalctl Useful Switches 234 17.3 Filtering the Journal Output 235 Filtering Based on a Boot Number 235 • Filtering Based on Time Interval 235 • Filtering Based on Fields 236 17.4 Investigating systemd Errors 237 ix Administration Guide 17.5 Journald Configuration 238 Changing the Journal Size Limit 238 • Forwarding the Journal to /dev/ ttyX 238 • Forwarding the Journal to Syslog Facility 239 17.6 Using YaST to Filter the systemd Journal 239 17.7 Viewing Logs in GNOME 240 18 update-alternatives: Managing Multiple Versions of Commands and Files 241 18.1 Overview 241 18.2 Use Cases 243 18.3 Getting an Overview of Alternatives 243 18.4 Viewing Details on Specific Alternatives 243 18.5 Setting the Default Version of Alternatives 244 18.6 Installing Custom
Recommended publications
  • Performance Analysis of Text-Oriented Printing Using Postscript

    Performance Analysis of Text-Oriented Printing Using Postscript

    Rochester Institute of Technology RIT Scholar Works Theses 1988 Performance analysis of text-oriented printing using PostScript Thomas Kowalczyk Follow this and additional works at: https://scholarworks.rit.edu/theses Recommended Citation Kowalczyk, Thomas, "Performance analysis of text-oriented printing using PostScript" (1988). Thesis. Rochester Institute of Technology. Accessed from This Thesis is brought to you for free and open access by RIT Scholar Works. It has been accepted for inclusion in Theses by an authorized administrator of RIT Scholar Works. For more information, please contact [email protected]. Rochester Institute ofTechnology School ofComputer Science and Technology Perfonnance Analysis of Text-Oriented Printing Using POSTSCRIPT® by Thomas L. Kowalczyk A thesis, submitted to The Faculty ofthe School ofComputer Science and Technology, in partial fulfillment ofthe requirements for the degree of Master ofScience in Computer Science Approved by: Guy Johnson Professor and Chairman of Applied Computer Studies Dr. Vishwas G. Abhyankar instructor Frank R.Hubbell instructor October 10, 1988 Thesis Title: Performance Analysis of Text-Oriented Printing Using POSTSCRIPT® I, Thomas L. Kowalczyk, hereby grant permission to the Wallace Memorial Libra.ry, of R.I.T., to reproduce my thesis in whole or in part under the following conditions: 1. I am contacted each time a reproduction is made. I can be reached at the fol1mving address: 82 Brush Hollow Road Rochester, New York 14626 Phone # (716) 225-8569 2. Any reproduction will not be for commercial use orprofit. Date: October 10,1988 i Pennission Statement Apple, Appletalk, LaserWriter, and Macintosh are registered trademarks of Apple Computer, Inc. Fluent Laser Fonts and Galileo Roman are trademarks of CasadyWare Inc.
  • Improving Route Scalability: Nexthops As Separate Objects

    Improving Route Scalability: Nexthops As Separate Objects

    Improving Route Scalability: Nexthops as Separate Objects September 2019 David Ahern | Cumulus Networks !1 Agenda Executive Summary ▪ If you remember nothing else about this talk … Driving use case Review legacy route API Dive into Nexthop API Benefits of the new API Cumulus Networks !2 Performance with the Legacy Route API route route route prefix/lenroute prefix/lendev prefix/lendev gatewayprefix/len gatewaydev gatewaydev gateway Cumulus Networks !3 Splitting Next Hops from Routes Routes with separate Nexthop objects Legacy Route API route route prefix/len nexthop route nexthop id dev route gateway prefix/lenroute prefix/lendev prefix/lendev gatewayprefix/len gatewaydev gatewaydev gateway route prefix/len nexthop nexthop nexthop id group nexthopdev nexthop[N] gatewaydev gateway Cumulus Networks !4 Dramatically Improves Route Scalability … Cumulus Networks !5 … with the Potential for Constant Insert Times Cumulus Networks !6 Networking Operating System Using Linux APIs Routing daemon or utility manages switchd ip FRR entries in kernel FIBs via rtnetlink APIs SDK userspace ▪ Enables other control plane software to use Linux networking APIs rtnetlink Data path connections, stats, troubleshooting, … FIB notifications FIB Management of hardware offload is separate kernel upper devices tunnels ▪ Keeps hardware in sync with kernel ... eth0 swp1 swp2 swpN Userspace driver with SDK leveraging driver driver driver kernel notifications NIC switch ASIC H / W Cumulus Networks !7 NOS with switchdev Driver In-kernel switchdev driver ip FRR Leverages
  • Desktop Migration and Administration Guide

    Desktop Migration and Administration Guide

    Red Hat Enterprise Linux 7 Desktop Migration and Administration Guide GNOME 3 desktop migration planning, deployment, configuration, and administration in RHEL 7 Last Updated: 2021-05-05 Red Hat Enterprise Linux 7 Desktop Migration and Administration Guide GNOME 3 desktop migration planning, deployment, configuration, and administration in RHEL 7 Marie Doleželová Red Hat Customer Content Services [email protected] Petr Kovář Red Hat Customer Content Services [email protected] Jana Heves Red Hat Customer Content Services Legal Notice Copyright © 2018 Red Hat, Inc. This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed. 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.
  • Institutionen För Datavetenskap Department of Computer and Information Science

    Institutionen För Datavetenskap Department of Computer and Information Science

    Institutionen för datavetenskap Department of Computer and Information Science Final thesis GPU accelerated rendering of vector based maps on iOS by Jonas Bromö and Alexander Qvick Faxå LIU-IDA/LITH-EX-A--14/023--SE 2014-05-30 Linköpings universitet Linköpings universitet SE-581 83 Linköping, Sweden 581 83 Linköping Linköpings universitet Institutionen för datavetenskap Final thesis GPU accelerated rendering of vector based maps on iOS by Jonas Bromö and Alexander Qvick Faxå LIU-IDA/LITH-EX-A--14/023--SE 2014-05-30 Supervisor: Anders Fröberg (IDA), Thibault Durand (IT-Bolaget Per & Per AB) Examiner: Erik Berglund Abstract Digital maps can be represented as either raster (bitmap images) or vector data. Vector maps are often preferable as they can be stored more efficiently and rendered irrespective of screen resolution. Vector map rendering on demand can be a computationally intensive task and has to be implemented in an efficient manner to ensure good performance and a satisfied end-user, especially on mobile devices with limited computational resources. This thesis discusses different ways of utilizing the on-chip GPU to improve the vector map rendering performance of an existing iOS app. It describes an implementation that uses OpenGL ES 2.0 to achieve the same end-result as the old CPU-based implementation using the same underlying map infras- tructure. By using the OpenGL based map renderer as well as implementing other performance optimizations, the authors were able to achieve an almost fivefold increase in rendering performance on an iPad Air. i Glossary AGG Anti-Grain Geometry. Open source graphics library with a software renderer that supports Anti-Aliasing and Subpixel Accuracy.
  • Storage Administration Guide Storage Administration Guide SUSE Linux Enterprise Server 12 SP4

    Storage Administration Guide Storage Administration Guide SUSE Linux Enterprise Server 12 SP4

    SUSE Linux Enterprise Server 12 SP4 Storage Administration Guide Storage Administration Guide SUSE Linux Enterprise Server 12 SP4 Provides information about how to manage storage devices on a SUSE Linux Enterprise Server. 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 xii 2 Giving Feedback xiv 3 Documentation Conventions xiv 4 Product Life Cycle and Support xvi Support Statement for SUSE Linux Enterprise Server xvii • Technology Previews xviii I FILE SYSTEMS AND MOUNTING 1 1 Overview
  • Reverse Engineering Power Management on NVIDIA Gpus - Anatomy of an Autonomic-Ready System Martin Peres

    Reverse Engineering Power Management on NVIDIA Gpus - Anatomy of an Autonomic-Ready System Martin Peres

    Reverse Engineering Power Management on NVIDIA GPUs - Anatomy of an Autonomic-ready System Martin Peres To cite this version: Martin Peres. Reverse Engineering Power Management on NVIDIA GPUs - Anatomy of an Autonomic-ready System. ECRTS, Operating Systems Platforms for Embedded Real-Time appli- cations 2013, Jul 2013, Paris, France. hal-00853849 HAL Id: hal-00853849 https://hal.archives-ouvertes.fr/hal-00853849 Submitted on 23 Aug 2013 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. Reverse engineering power management on NVIDIA GPUs - Anatomy of an autonomic-ready system Martin Peres Ph.D. student at LaBRI University of Bordeaux Hobbyist Linux/Nouveau Developer Email: [email protected] Abstract—Research in power management is currently limited supported nor documented by NVIDIA. As GPUs are leading by the fact that companies do not release enough documentation the market in terms of performance-per-Watt [3], they are or interfaces to fully exploit the potential found in modern a good candidate for a reverse engineering effort of their processors. This problem is even more present in GPUs despite power management features. The choice of reverse engineering having the highest performance-per-Watt ratio found in today’s NVIDIA’s power management features makes sense as they processors.
  • Security Assurance Requirements for Linux Application Container Deployments

    Security Assurance Requirements for Linux Application Container Deployments

    NISTIR 8176 Security Assurance Requirements for Linux Application Container Deployments Ramaswamy Chandramouli This publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8176 NISTIR 8176 Security Assurance Requirements for Linux Application Container Deployments Ramaswamy Chandramouli Computer Security Division Information Technology Laboratory This publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8176 October 2017 U.S. Department of Commerce Wilbur L. Ross, Jr., Secretary National Institute of Standards and Technology Walter Copan, NIST Director and Under Secretary of Commerce for Standards and Technology NISTIR 8176 SECURITY ASSURANCE FOR LINUX CONTAINERS National Institute of Standards and Technology Internal Report 8176 37 pages (October 2017) This publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8176 Certain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. This p There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each ublication is available free of charge from: http publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.
  • Practice Test Version 1.8 LPI 117-101: Practice Exam QUESTION NO: 1 CORRECT TEXT

    Practice Test Version 1.8 LPI 117-101: Practice Exam QUESTION NO: 1 CORRECT TEXT

    LPI 117-101 117-101 LPI 101 General Linux, Part I Practice Test Version 1.8 LPI 117-101: Practice Exam QUESTION NO: 1 CORRECT TEXT You suspect that a new ethernet card might be conflicting with another device. Which file should you check within the /proc tree to learn which IRQs are being used by which kernel drives? Answer: interrupts QUESTION NO: 2 How many SCSI ids for peripherals can SCSI-1 support? A. 5 B. 6 C. 7 D. 8 Answer: C Explanation: SCSI-1 support total 7 peripherals. There are several different types of SCSI devices. The original SCSI specification is commonly referred to as SCSI-1. The newer specification, SCSI-2, offers increased speed and performance, as well as new commands. Fast SCSI increases throughput to more than 10MB per second. Fast-Wide SCSI provides a wider data path and throughput of up to 40MB per second and up to 15 devices. There there are Ultra-SCSI and Ultra-Wide-SCSI QUESTION NO: 3 You need to install a fax server. Which type of fax/modem should you install to insure Linux compatibility? Test-King.com A. External Serial Fax/modem B. External USB Fax/modem C. Internal ISA Fax/modem D. Internal PCI Fax/modem Answer: A QUESTION NO: 4 You are running Linux 2.0.36 and you need to add a USB mouse to your system. Which of the following statements is true? "Welcome to Certification's Main Event" - www.test-king.com 2 LPI 117-101: Practice Exam A. You need to rebuild the kernel.
  • High Speed Visualization in the Jetos Aviation Operating System Using Hardware Acceleration*

    High Speed Visualization in the Jetos Aviation Operating System Using Hardware Acceleration*

    High Speed Visualization in the JetOS Aviation Operating System Using Hardware Acceleration* Boris Barladian[0000-0002-2391-2067], Nikolay Deryabin[0000-0003-1248-6047], Alexey Voloboy[0000-0003-1252-8294], Vladimir Galaktionov[0000-0001-6460-7539], and Lev Shapiro[0000-0002-6350-851X] The Keldysh Institute of the Applied Mathematics of RAS, Moscow, Russia [email protected],{voloboy, vlgal, pls}@gin.keldysh.ru Abstract. The paper discusses details of the pilot display visualization that uses the hardware acceleration capabilities of the Vivante graphics processor in the JetOS aviation operating system. Previously the OpenGL Safety Critical library was implemented without hardware acceleration. This was done in such a way because software library is easier to certify in accordance with the avionics re- quirements. But usage of the software OpenGL does not provide acceptable visualization speed for modern Flight Display and 3D relief applications. So more complex visualization approach utilized the GPU acceleration capabilities was elaborated. Although the OpenGL library was implemented for a specific GPU and took into account its specificity, the described approach to adapt the MESA open source library can be used for other GPUs. An effective algorithm for multi-window visualization using the implemented library with hardware acceleration is present. The described approach allows you to achieve the visu- alization speed acceptable for the pilot display of the aircraft. Keywords: Pilot Display, Embedded Systems, Real-time Operating System, OpenGL Safety Critical, Multi-windowing. 1 Introduction In [1] requirements were formulated for a real-time operating system (RTOS) de- signed to work with integrated modular avionics. In particular, the RTOS should comply with the ARINC 653 standard [2].
  • Lightdm Lightdm

    Lightdm Lightdm

    02/10/2021 20:51 1/8 LightDM LightDM Objet : installation et configuration du gestionnaire de connexion Lightdm. Niveau requis : débutant, avisé . Commentaires : LighDM est une alternative à GDM ou KDM. Débutant, à savoir : Utiliser GNU/Linux en ligne de commande, tout commence là ! Suivi : à-tester Création par black_sun_2012 le 18/07/2012. Mise-à-jour par paskal le 29/10/2013. Mise à jour par Freddec le 07/12/2015, rajout du paragraphe. Verrouiller le pavé numérique dés le lancement de LightDM. Testé par <…> le <…> Commentaires sur le forum : Lien vers le forum concernant ce tuto 1) Présentation LightDM est un gestionnaire d'affichage multi-desktop. Il a été conçu pour être une alternative relativement légère et très personnalisable à GDM. LightDM a été introduit depuis Wheezy, il est suffisamment stable pour être aussi utilisé dans Stretch et Sid. Installation Installer2) le paquet lightdm : apt-get update && apt-get install lightdm Depuis stretch on peut aussi utiliser la commande apt ainsi : apt update && apt install lightdm Configuration LightDM est configurable en éditant3) le fichier : /etc/lightdm/lightdm.conf Il est recommandé d'effectuer une sauvegarde du fichier de configuration avant d'essayer de le Documentation - Wiki - http://debian-facile.org/ Last update: 31/08/2021 11:24 doc:environnements:x11:lightdm http://debian-facile.org/doc:environnements:x11:lightdm configurer. Pour changer le gestionnaire d'affichage par défaut courant, exécutez : dpkg-reconfigure lightdm puis sélectionnez : lightdm Si vous débutez avec LightDM, mieux vaut avoir GDM, SLiM ou un autre gestionnaire d'affichage installé en sauvegarde. Pour connaître les différentes clés je vous renvoie sur la doc : ubuntu Et aussi quelques explications sur différents paramètres et comment les modifier : aller plus loin Modifier le fond de l'écran d'accueil La configuration de l'écran d'accueil GTK de LightDM avec Debian se trouve dans le fichier /etc/lightdm/lightdm-gtk-greeter.conf.
  • Control of Protein Orientation on Gold Nanoparticles † ∥ † § † ∥ ⊥ Wayne Lin, Thomas Insley, Marcus D

    Control of Protein Orientation on Gold Nanoparticles † ∥ † § † ∥ ⊥ Wayne Lin, Thomas Insley, Marcus D

    Article pubs.acs.org/JPCC Control of Protein Orientation on Gold Nanoparticles † ∥ † § † ∥ ⊥ Wayne Lin, Thomas Insley, Marcus D. Tuttle, Lingyang Zhu, Deborah A. Berthold, Petr Kral,́, † ‡ # † Chad M. Rienstra,*, , , and Catherine J. Murphy*, † ‡ Department of Chemistry and Department of Biochemistry, University of Illinois at Urbana−Champaign, 600 South Matthews Avenue, Urbana, Illinois 61801, United States § School of Chemical Sciences, University of Illinois at Urbana−Champaign, 505 South Matthews Avenue, Urbana, Illinois 61801, United States ∥ ⊥ Department of Chemistry and Department of Physics, University of Illinois at Chicago, 845 West Taylor Street, Chicago, Illinois 60607, United States # Center for Biophysics and Computational Biology, University of Illinois at Urbana−Champaign, 607 South Matthews Avenue, Urbana, Illinois 61801, United States *S Supporting Information ABSTRACT: Gold nanoparticles (Au NPs) have attracted much attention due to their potential applications in nanomedicine. While numerous studies have quantified biomolecular adsorption to Au NPs in terms of equilibrium binding constants, far less is known about biomolecular orientation on nanoparticle surfaces. In this study, the binding of the protein α-synuclein to citrate and (16- mercaptohexadecyl)trimethylammonium bromide (MTAB)-coated 12 nm Au NPs is examined by heteronuclear single quantum coherence NMR spectroscopy to provide site-specific measurements of protein−nanoparticle binding. Molecular dynamics simulations support the orientation assignments, which
  • Implementation of an Orthogonally Persistent L4 -Kernel Based System

    Implementation of an Orthogonally Persistent L4 -Kernel Based System

    Implementation of an Orthogonally Persistent L4 -Kernel Based System Christian Ceelen ÐÒÖºÙ º Supervisor: Cand. Scient. Espen Skoglund Universitat¨ Karlsruhe 15th February 2002 2 3 Abstract Orthogonal persistent systems open up possibilities for a wide number of appli- cations. Even more, it is a very natural concept for the storage of information, since objects and information persists until the end of their lifetime. Most current commercial non-persistent systems have only an explicit storage model. Thus, an application has to care for the persistent storage of data itself. This has to be done by transforming the data structures into something that can be stored within a file. Furthermore the file has to be opened, written to and saved explicitly; a source of overhead for programmers. Moreover the programmer also has to estimate the life-time of all valuable data. Including the conversion and recovery of data, the amount of code needed to store data explicitly could easily take up a third or half of the actual programming work. In order to support a convenient system environment, persistent storage could be handled implicitly by the operating system. The operating system has to store for each task an image of the user memory and all kernel internal data like page- tables, mapping structures, file descriptors and so on. This approach is very de- manding and very error-prone for current monolithic systems. Therefore we pro- pose a -kernel based system instead. The proposed work should provide an implementation base for further persistent systems by supplying the necessary mechanisms to build persistent applications on top of the -kernel.