DOCSLIB.ORG

Administration Guide Administration Guide SUSE Linux Enterprise Server 15 SP2

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Administration Guide Administration Guide SUSE Linux Enterprise Server 15 SP2 SUSE Linux Enterprise Server 15 SP2 Administration Guide Administration Guide SUSE Linux Enterprise Server 15 SP2 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 2 sudo Basics 17 2.1 Basic sudo Usage 17 Running a Single Command 17 • Starting a Shell 18 iii Administration Guide 2.2 Configuring sudo 19 Editing the Configuration Files 19 • Basic sudoers Configuration Syntax 20 • Basic sudoers Rules 21 2.3 sudo Use Cases 23 Using sudo without root Password 23 • Using sudo with X.Org Applications 24 2.4 Further Information 25 3 YaST 26 3.1 YaST Topics 26 3.2 YaST Interface Overview 27 3.3 Useful Key Combinations 27 4 YaST in Text Mode 29 4.1 Navigation in Modules 30 4.2 Advanced Key Combinations 31 4.3 Restriction of Key Combinations 32 4.4 YaST Command Line Options 32 Installing Packages from the Command Line 33 • Working with Individual Modules 33 • Command Line Parameters of YaST Modules 33 5 YaST Online Update 58 5.1 The Online Update Dialog 59 5.2 Installing Patches 60 5.3 Automatic Online Update 61 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 iv Administration Guide Services Using Deleted Files 75 • Managing Repositories with Zypper 76 • Querying Repositories and Packages with Zypper 78 • Showing Life Cycle Information 80 • Configuring Zypper 81 • Troubleshooting 82 • 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 84 • Delta RPM Packages 85 • RPM Queries 86 • 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 Default Settings 94 • Types of Snapshots 94 • Directories That Are Excluded from Snapshots 95 • Customizing the Setup 96 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 7.6 Manually Creating and Managing Snapshots 119 Snapshot Metadata 119 • Creating Snapshots 121 • Modifying Snapshot Metadata 122 • Deleting Snapshots 122 v Administration Guide 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 8.6 Troubleshooting Kernel Live Patching issues 138 Manual patch downgrade 138 9 Transactional Updates 139 9.1 Limitations of Technology Preview 139 9.2 Enabling transactional-update 141 9.3 Managing Automatic Updates 141 9.4 The transactional-update Command 142 9.5 Troubleshooting 144 10 Remote Graphical Sessions with VNC 145 10.1 The vncviewer Client 145 Connecting Using the vncviewer CLI 145 • Connecting Using the vncviewer GUI 146 • Notification of Unencrypted Connections 146 vi Administration Guide 10.2 Remmina: the Remote Desktop Client 146 Installation 146 • Main Window 147 • Adding Remote Sessions 147 • Starting Remote Sessions 149 • Editing, Copying, and Deleting Saved Sessions 150 • Running Remote Sessions from the Command Line 150 10.3 Configuring One-time Sessions on the VNC Server 151 Available Configurations 152 • Initiating a One-time VNC Session 153 • Configuring One-time VNC Sessions 153 10.4 Configuring Persistent VNC Server Sessions 154 VNC Session Initiated Using vncserver 155 • VNC Session Initiated Using vncmanager 156 10.5 Configuring Encryption on the VNC Server 159 11 File Copying with RSync 162 11.1 Conceptual Overview 162 11.2 Basic Syntax 162 11.3 Copying Files and Directories Locally 163 11.4 Copying Files and Directories Remotely 164 11.5 Configuring and Using an Rsync Server 164 11.6 For More Information 167 II BOOTING A LINUX SYSTEM 168 12 Introduction to the Boot Process 169 12.1 Terminology 169 12.2 The Linux Boot Process 170 The Initialization and Boot Loader Phase 170 • The Kernel Phase 171 • The init on initramfs Phase 174 • The systemd Phase 176 vii Administration Guide 13 UEFI (Unified Extensible Firmware Interface) 177 13.1 Secure Boot 177 Implementation on SUSE Linux Enterprise Server 178 • MOK (Machine Owner Key) 180 • Booting a Custom Kernel 181 • Using Non-Inbox Drivers 183 • Features and Limitations 184 13.2 For More Information 185 14 The Boot Loader GRUB 2 186 14.1 Main Differences between GRUB Legacy and GRUB 2 186 14.2 Configuration File Structure 186 The File /boot/grub2/grub.cfg 187 • The File /etc/default/ grub 188 • Scripts in /etc/grub.d 191 • Mapping between BIOS Drives and Linux Devices 192 • Editing Menu Entries during the Boot Procedure 193 • Setting a Boot Password 194 14.3 Configuring the Boot Loader with YaST 195 Boot Loader Location and Boot Code Options 197 • Adjusting the Disk Order 198 • Configuring Advanced Options 199 14.4 Differences in Terminal Usage on IBM Z 202 Limitations 202 • Key Combinations 203 14.5 Helpful GRUB 2 Commands 205 14.6 More Information 206 15 The systemd Daemon 207 15.1 The systemd concept 207 Unit File 208 15.2 Basic Usage 209 Managing Services in a Running System 209 • Permanently Enabling/ Disabling Services 211 15.3 System Start and Target Management 213 Targets Compared to Runlevels 213 • Debugging System Start- Up 216 • System V Compatibility 219 viii Administration Guide 15.4 Managing Services with YaST 220 15.5 Customizing systemd 221 Customizing Unit Files 221 • Creating drop-in files 222 • Converting xinetd services to systemd 223 • Creating Custom Targets 224 15.6 Advanced Usage 225 Cleaning Temporary Directories 225 • System Log 226 • Snapshots 226 • Loading Kernel Modules 226 • Performing Actions before Loading a Service 227 • Kernel Control Groups (cgroups) 228 • Terminating Services (Sending Signals) 229 • Important Notes on the D-Bus Service 229 • Debugging Services 230 15.7 systemd timer units 231 systemd timer types 232 • systemd timers and service units 232 • Practical example 232 • Managing systemd timers 234 15.8 More Information 234 III SYSTEM 235 16 32-Bit and 64-Bit Applications in a 64-Bit System Environment 236 16.1 Runtime Support 236 16.2 Kernel Specifications 237 17 journalctl: Query the systemd Journal 238 17.1 Making the Journal Persistent 238 17.2 journalctl Useful Switches 239 17.3 Filtering the Journal Output 240 Filtering Based on a Boot Number 240 • Filtering Based on Time Interval 240 • Filtering Based on Fields 241 17.4 Investigating systemd Errors 242 ix Administration Guide 17.5 Journald Configuration 243 Changing the Journal Size Limit 243 • Forwarding the Journal to /dev/ ttyX 243 • Forwarding the Journal to Syslog Facility 244 17.6 Using YaST to Filter the systemd Journal 244 17.7 Viewing Logs
Load more

Recommended publications
  • RACF Tips Volume 3, Issue 1, January 2009
    Volume 3 Issue 1 IPS RSH RACF T January For Administrators, Auditors, and Analysts 2009 Specifying a Replacement ID used to change a file's attributes for Program Control, APF Authorized, and Shared Library. with IRRRID00 . To generate commands to delete an ID and all references to it, use RACF's IRRRID00 utility. You simply enter the ID in the SYSIN DD Temporary Access with statement of the IRRRID00 job like so: CONNECT REVOKE(date) //SYSIN DD * USERX You may occasionally need to permit a user temporary access to a resource. One way to do If USERX is the owner of a profile or connect, so is to grant a group access to the resource IRRRID00 generates commands like: and connect the user to that group with a revoke date. The command to set the connect revoke CONNECT RDSADM GROUP(RACFSTC) OWNER(?USERX) date would look something like this: In these cases, you need to change ?USERX to CONNECT USERA GROUP(TEMPACC) REVOKE(1/20/09) a valid replacement ID. This can be done manually or with ISPF EDIT CHANGE. On the date specified with the revoke, RACF will no longer allow the user to have the access Alternatively, you can tell IRRRID00 which permitted to the group. If you want to remove the replacement ID to use when it builds the revoke date but leave the connect intact, enter: commands. If, for instance, you want to replace every occurrence of USERX with USERJ, enter CONNECT USERA GROUP(TEMPACC) NOREVOKE the following in the SYSIN DD: A banking client of ours used this capability to //SYSIN DD * govern access to APF-authorized libraries.
    [Show full text]
  • LS-09EN. OS Permissions. SUID/SGID/Sticky. Extended Attributes
    Operating Systems LS-09. OS Permissions. SUID/SGID/Sticky. Extended Attributes. Operating System Concepts 1.1 ys©2019 Linux/UNIX Security Basics Agenda ! UID ! GID ! Superuser ! File Permissions ! Umask ! RUID/EUID, RGID/EGID ! SUID, SGID, Sticky bits ! File Extended Attributes ! Mount/umount ! Windows Permissions ! File Systems Restriction Operating System Concepts 1.2 ys©2019 Domain Implementation in Linux/UNIX ! Two types domain (subjects) groups ! User Domains = User ID (UID>0) or User Group ID (GID>0) ! Superuser Domains = Root ID (UID=0) or Root Group ID (root can do everything, GID=0) ! Domain switch accomplished via file system. ! Each file has associated with it a domain bit (SetUID bit = SUID bit). ! When file is executed and SUID=on, then Effective UID is set to Owner of the file being executed. When execution completes Efective UID is reset to Real UID. ! Each subject (process) and object (file, socket,etc) has a 16-bit UID. ! Each object also has a 16-bit GID and each subject has one or more GIDs. ! Objects have access control lists that specify read, write, and execute permissions for user, group, and world. Operating System Concepts 1.3 ys©2019 Subjects and Objects Subjects = processes Objects = files (regular, directory, (Effective UID, EGID) devices /dev, ram /proc) RUID (EUID) Owner permissions (UID) RGID-main (EGID) Group Owner permissions (GID) +RGID-list Others RUID, RGID Others ID permissions Operating System Concepts 1.4 ys©2019 The Superuser (root) • Almost every Unix system comes with a special user in the /etc/passwd file with a UID=0. This user is known as the superuser and is normally given the username root.
    [Show full text]
  • 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.
    [Show full text]
  • 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
    [Show full text]
  • 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).
    [Show full text]
  • The Unicode Cookbook for Linguists: Managing Writing Systems Using Orthography Profiles
    Zurich Open Repository and Archive University of Zurich Main Library Strickhofstrasse 39 CH-8057 Zurich www.zora.uzh.ch Year: 2017 The Unicode Cookbook for Linguists: Managing writing systems using orthography profiles Moran, Steven ; Cysouw, Michael DOI: https://doi.org/10.5281/zenodo.290662 Posted at the Zurich Open Repository and Archive, University of Zurich ZORA URL: https://doi.org/10.5167/uzh-135400 Monograph The following work is licensed under a Creative Commons: Attribution 4.0 International (CC BY 4.0) License. Originally published at: Moran, Steven; Cysouw, Michael (2017). The Unicode Cookbook for Linguists: Managing writing systems using orthography profiles. CERN Data Centre: Zenodo. DOI: https://doi.org/10.5281/zenodo.290662 The Unicode Cookbook for Linguists Managing writing systems using orthography profiles Steven Moran & Michael Cysouw Change dedication in localmetadata.tex Preface This text is meant as a practical guide for linguists, and programmers, whowork with data in multilingual computational environments. We introduce the basic concepts needed to understand how writing systems and character encodings function, and how they work together. The intersection of the Unicode Standard and the International Phonetic Al- phabet is often not met without frustration by users. Nevertheless, thetwo standards have provided language researchers with a consistent computational architecture needed to process, publish and analyze data from many different languages. We bring to light common, but not always transparent, pitfalls that researchers face when working with Unicode and IPA. Our research uses quantitative methods to compare languages and uncover and clarify their phylogenetic relations. However, the majority of lexical data available from the world’s languages is in author- or document-specific orthogra- phies.
    [Show full text]
  • Version 7.8-Systemd
    Linux From Scratch Version 7.8-systemd Created by Gerard Beekmans Edited by Douglas R. Reno Linux From Scratch: Version 7.8-systemd by Created by Gerard Beekmans and Edited by Douglas R. Reno Copyright © 1999-2015 Gerard Beekmans Copyright © 1999-2015, Gerard Beekmans All rights reserved. This book is licensed under a Creative Commons License. Computer instructions may be extracted from the book under the MIT License. Linux® is a registered trademark of Linus Torvalds. Linux From Scratch - Version 7.8-systemd Table of Contents Preface .......................................................................................................................................................................... vii i. Foreword ............................................................................................................................................................. vii ii. Audience ............................................................................................................................................................ vii iii. LFS Target Architectures ................................................................................................................................ viii iv. LFS and Standards ............................................................................................................................................ ix v. Rationale for Packages in the Book .................................................................................................................... x vi. Prerequisites
    [Show full text]
  • Estudio De Producción Multimedia Con GNU/Linux”
    No. 03 Vol. 02 ABRIL / 2008 /etc/init.d/uxi start Y Cuba qué con el: “¿Por qué escoger Symfony?” MaryanLinux Noticias Migración .::página 8::. “Estudio de Producción Multimedia con GNU/Linux” Soluciones de esta edición “Instalar GRUB no en el Master Boot Record” Programación “Replicación Master-Master con MySQL 5.0 en Debian Etch”(Parte I) Entrevista ¿X? “Al Software Libre ¿por qué migrar?”(Parte II) 22000088 Humor Libre .::página 22::. Eventos “Cuba en el FLISoL 2008” Informática 2007 “Revisión de la legislación cubana para el uso y desarrollo del Software Libre Estudio de Producción en Cuba” Multimedia con GNU/Linux “Syslog Centralizado con detección de eventos” “Firewall de alta disponibilidad” .::página 9::. “Publicar nuestro software: único camino hacia la libertad plena” Jefe Consejo Editorial: Arte y Diseño: Abel García Vitier Angel Alberto Bello Caballero [email protected] [email protected] Editores: David Padrón Álvarez [email protected] Jorge Luis Betancourt González [email protected] Ezequiel Manresa Santana [email protected] Gustavo Javier Blanco Díaz [email protected] Karla Reyes Olivera [email protected] Félix Daniel Batista Diñeiro [email protected] Yosbel Brooks Chávez [email protected] Redacción: Yailin Simón Mir [email protected] Elisandra Corrales Estrada [email protected] Marisniulkis Lescaille Cos [email protected] Revisión y Corrección: MSc. Clara Gisela Scot Bigñot [email protected] Dunia Virgen Cruz Góngora [email protected] MSc. Graciela González Pérez Coordinadores: [email protected] Ing. Abel Meneses Abad [email protected] Rislaidy Pérez Ramos [email protected] Eiger Mora Moredo [email protected] Victor Frank Molina López [email protected] Patrocinadores: Proyecto de Software Libre Grupo de Producción FEU MaryanLinux: Distro de Facultad X Linux basada en Ubuntu Estimado Lector: Llega a usted otro número de UXi cargado de información referente al Software Libre.
    [Show full text]
  • Optical Character Recognition - a Combined ANN/HMM Approach
    Optical Character Recognition - A Combined ANN/HMM Approach Dissertation submitted to the Department of Computer Science Technical University of Kaiserslautern for the fulfillment of the requirements for the doctoral degree Doctor of Engineering (Dr.-Ing.) by Sheikh Faisal Rashid Dean: Prof. Dr. Klaus Schneider Thesis supervisors: Prof. Dr. Thomas Breuel, TU Kaiserslautern Prof. Dr. Andreas Dengel, TU Kaiserslautern Chair of supervisory committee: Prof. Dr. Karsten Berns, TU Kaiserslautern Kaiserslautern, 11 July, 2014 D 386 Abstract Optical character recognition (OCR) of machine printed text is ubiquitously considered as a solved problem. However, error free OCR of degraded (broken and merged) and noisy text is still challenging for modern OCR systems. OCR of degraded text with high accuracy is very important due to many applications in business, industry and large scale document digitization projects. This thesis presents a new OCR method for degraded text recognition by introducing a combined ANN/HMM OCR approach. The approach provides significantly better performance in comparison with state-of-the-art HMM based OCR methods and existing open source OCR systems. In addition, the thesis introduces novel applications of ANNs and HMMs for document image preprocessing and recognition of low resolution text. Furthermore, the thesis provides psychophysical experiments to determine the effect of letter permutation in visual word recognition of Latin and Cursive script languages. HMMs and ANNs are widely employed pattern recognition paradigms and have been used in numerous pattern classification problems. This work presents a simple and novel method for combining the HMMs and ANNs in application to segmentation free OCR of degraded text. HMMs and ANNs are powerful pattern recognition strategies and their combination is interesting to improve current state-of-the-art research in OCR.
    [Show full text]
  • The GNOME Desktop Environment
    The GNOME desktop environment Miguel de Icaza ([email protected]) Instituto de Ciencias Nucleares, UNAM Elliot Lee ([email protected]) Federico Mena ([email protected]) Instituto de Ciencias Nucleares, UNAM Tom Tromey ([email protected]) April 27, 1998 Abstract We present an overview of the free GNU Network Object Model Environment (GNOME). GNOME is a suite of X11 GUI applications that provides joy to users and hackers alike. It has been designed for extensibility and automation by using CORBA and scripting languages throughout the code. GNOME is licensed under the terms of the GNU GPL and the GNU LGPL and has been developed on the Internet by a loosely-coupled team of programmers. 1 Motivation Free operating systems1 are excellent at providing server-class services, and so are often the ideal choice for a server machine. However, the lack of a consistent user interface and of consumer-targeted applications has prevented free operating systems from reaching the vast majority of users — the desktop users. As such, the benefits of free software have only been enjoyed by the technically savvy computer user community. Most users are still locked into proprietary solutions for their desktop environments. By using GNOME, free operating systems will have a complete, user-friendly desktop which will provide users with powerful and easy-to-use graphical applications. Many people have suggested that the cause for the lack of free user-oriented appli- cations is that these do not provide enough excitement to hackers, as opposed to system- level programming. Since most of the GNOME code had to be written by hackers, we kept them happy: the magic recipe here is to design GNOME around an adrenaline response by trying to use exciting models and ideas in the applications.
    [Show full text]
  • TEE Internal Core API Specification V1.1.2.50
    GlobalPlatform Technology TEE Internal Core API Specification Version 1.1.2.50 (Target v1.2) Public Review June 2018 Document Reference: GPD_SPE_010 Copyright 2011-2018 GlobalPlatform, Inc. All Rights Reserved. Recipients of this document are invited to submit, with their comments, notification of any relevant patents or other intellectual property rights (collectively, “IPR”) of which they may be aware which might be necessarily infringed by the implementation of the specification or other work product set forth in this document, and to provide supporting documentation. The technology provided or described herein is subject to updates, revisions, and extensions by GlobalPlatform. This documentation is currently in draft form and is being reviewed and enhanced by the Committees and Working Groups of GlobalPlatform. Use of this information is governed by the GlobalPlatform license agreement and any use inconsistent with that agreement is strictly prohibited. TEE Internal Core API Specification – Public Review v1.1.2.50 (Target v1.2) THIS SPECIFICATION OR OTHER WORK PRODUCT IS BEING OFFERED WITHOUT ANY WARRANTY WHATSOEVER, AND IN PARTICULAR, ANY WARRANTY OF NON-INFRINGEMENT IS EXPRESSLY DISCLAIMED. ANY IMPLEMENTATION OF THIS SPECIFICATION OR OTHER WORK PRODUCT SHALL BE MADE ENTIRELY AT THE IMPLEMENTER’S OWN RISK, AND NEITHER THE COMPANY, NOR ANY OF ITS MEMBERS OR SUBMITTERS, SHALL HAVE ANY LIABILITY WHATSOEVER TO ANY IMPLEMENTER OR THIRD PARTY FOR ANY DAMAGES OF ANY NATURE WHATSOEVER DIRECTLY OR INDIRECTLY ARISING FROM THE IMPLEMENTATION OF THIS SPECIFICATION OR OTHER WORK PRODUCT. Copyright 2011-2018 GlobalPlatform, Inc. All Rights Reserved. The technology provided or described herein is subject to updates, revisions, and extensions by GlobalPlatform.
    [Show full text]
  • Powerview Command Reference
    PowerView Command Reference TRACE32 Online Help TRACE32 Directory TRACE32 Index TRACE32 Documents ...................................................................................................................... PowerView User Interface ............................................................................................................ PowerView Command Reference .............................................................................................1 History ...................................................................................................................................... 12 ABORT ...................................................................................................................................... 13 ABORT Abort driver program 13 AREA ........................................................................................................................................ 14 AREA Message windows 14 AREA.CLEAR Clear area 15 AREA.CLOSE Close output file 15 AREA.Create Create or modify message area 16 AREA.Delete Delete message area 17 AREA.List Display a detailed list off all message areas 18 AREA.OPEN Open output file 20 AREA.PIPE Redirect area to stdout 21 AREA.RESet Reset areas 21 AREA.SAVE Save AREA window contents to file 21 AREA.Select Select area 22 AREA.STDERR Redirect area to stderr 23 AREA.STDOUT Redirect area to stdout 23 AREA.view Display message area in AREA window 24 AutoSTOre ..............................................................................................................................
    [Show full text]