DOCSLIB.ORG

A Source Book from the Open Group

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

ASource Book from The Open Group The Single UNIX® Specification: Authoriz ed Guide to Version 4 The Open Group Copyr ight ©March 2010, The Open Group All rights reserved. No partofthis publication maybereproduced, stored in a retrievalsystem, or transmitted, in anyfor m or by any means,electronic,mechanical, photocopying, recording or otherwise,without the prior permission of the copyr ight owners. ASource Book from The Open Group The Single UNIX® Specification: Author ized Guide to Version 4 ISBN: 1-931624-84-4 Document Number:G101 Published byThe Open Group,March 2010. Anycomments relating to the material contained in this document maybesubmitted byemail to: [email protected] ii ASource Book from The Open Group (2010) Contents Chapter 1 The Single UNIX Environment.............................................. 1 1.1 Introduction..................................................................................... 1 1.2 Interface Counts ............................................................................. 2 1.3 For mal Standards Alignment .......................................................... 2 1.4 Por tability Codes ............................................................................ 2 1.5 Option Groups ................................................................................ 6 1.6 Common Director ies and Devices .................................................. 7 1.7 Environment Var iables .................................................................... 7 1.8 YACCGrammars as Specifications ................................................ 8 1.9 Regular Expressions ...................................................................... 9 1.10 File Access ..................................................................................... 9 1.11 Programming Environment ............................................................. 9 1.11.1 C-Language Suppor t ................................................................... 9 1.11.2 Feature Test Macros and Name Space Issues............................ 10 1.11.3 Error Numbers ............................................................................. 10 1.11.4 Signal Concepts .......................................................................... 10 1.11.5 Standard I/O Streams.................................................................. 11 1.11.6 STREAMS ................................................................................... 11 1.11.7 XSI Inter process Communication ................................................ 11 1.11.8 Realtime ...................................................................................... 11 1.11.9 Threads ....................................................................................... 12 1.11.10 Sockets ........................................................................................ 12 1.11.11 General Ter minal Interface .......................................................... 12 1.11.12 HowtoRead an XSH Reference Page ........................................ 12 1.12 Commands and Utilities Environment ............................................ 13 1.12.1 Shell Command Language .......................................................... 13 1.12.2 Symbolic Links ............................................................................. 13 1.12.3 File Format Notation .................................................................... 13 1.12.4 HowtoRead an XCU Reference Page ....................................... 14 1.13 Ter minal Interfaces Environment .................................................... 14 1.14 Internationalization ......................................................................... 15 Chapter 2 The Single UNIX Specification, Version 4........................ 17 2.1 Base Definitions (XBD)................................................................... 17 2.2 System Interfaces (XSH) ................................................................ 18 2.3 Shell and Utilities (XCU) ................................................................. 18 2.4 Rationale (XRAT) ............................................................................ 19 2.5 X/Open Curses (XCURSES) .......................................................... 19 The Single UNIX® Specification: Author ized Guide to Version 4 iii Contents Chapter 3 System Interfaces...................................................................... 21 3.1 Base Documents ............................................................................ 21 3.2 Over viewofChanges ..................................................................... 21 3.3 System Interfaces byCategor y ...................................................... 25 3.4 XSH Option Groups........................................................................ 32 3.5 Options Policy ................................................................................. 34 Chapter 4 Shell and Utilities....................................................................... 37 4.1 Options in XCU............................................................................... 37 4.2 Functional Over view....................................................................... 37 4.3 Base Documents ............................................................................ 39 4.4 Over viewofChanges ..................................................................... 39 4.5 Exclusion of Utilities........................................................................ 40 Chapter 5 Headers.......................................................................................... 45 5.1 Header and Name Space Rules..................................................... 45 5.1.1 ISO CHeaders ............................................................................ 45 5.1.2 POSIX.1-2008 Base Headers...................................................... 46 5.1.3 XSI Headers ................................................................................ 47 5.2 Names SafetoUse ........................................................................ 48 5.3 Base Documents ............................................................................ 48 5.4 Over viewofChanges ..................................................................... 48 Chapter 6 Terminal Interfaces ................................................................... 51 6.1 Functional Over view....................................................................... 51 6.1.1 Curses Interfaces ........................................................................ 51 6.1.2 Curses Utilities ............................................................................. 53 6.2 Over viewofChanges ..................................................................... 53 Chapter 7 System Interface Table............................................................ 55 7.1 Introduction..................................................................................... 55 7.2 System Interface Table ................................................................... 56 Chapter 8 Utility Interface Table ............................................................... 81 8.1 Introduction..................................................................................... 81 8.2 Utility Interface Table ...................................................................... 82 Chapter 9 Header Interface Table............................................................. 87 9.1 Introduction..................................................................................... 87 9.2 Header Interface Table ................................................................... 88 Chapter 10 XCURSES Interface Table ...................................................... 91 10.1 Introduction..................................................................................... 91 10.2 XCURSES Interface Table .............................................................. 91 Chapter 11 System Interfaces Migration ................................................. 101 11.1 Introduction..................................................................................... 101 11.2 System Interfaces ........................................................................... 101 Chapter 12 Utilities Migration ...................................................................... 299 12.1 Introduction..................................................................................... 299 12.2 Utilities ............................................................................................ 299 iv ASource Book from The Open Group (2010) Contents Chapter 13 HeadersMigration ..................................................................... 341 13.1 Introduction..................................................................................... 341 13.2 Headers .......................................................................................... 341 Chapter 14 ISO C Migration .......................................................................... 363 14.1 Introduction..................................................................................... 363 14.2 Language Changes ........................................................................ 363 14.2.1 NewKeywords ............................................................................. 363 14.2.2 NewTypes ................................................................................... 364 14.2.3 Type Qualifiers............................................................................
Recommended publications
  • IEEE Std 1003.1-2008

    IEEE Std 1003.1-2008

    This preview is downloaded from www.sis.se. Buy the entire standard via https://www.sis.se/std-911530 INTERNATIONAL ISO/IEC/ STANDARD IEEE 9945 First edition 2009-09-15 Information technology — Portable Operating System Interface (POSIX®) Base Specifications, Issue 7 Technologies de l'information — Spécifications de base de l'interface pour la portabilité des systèmes (POSIX ®), Issue 7 Reference number ISO/IEC/IEEE 9945:2009(E) Copyright © 2001-2008, IEEE and The Open Group. All rights reserved This preview is downloaded from www.sis.se. Buy the entire standard via https://www.sis.se/std-911530 ISO/IEC/IEEE 9945:2009(E) PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. Neither the ISO Central Secretariat nor IEEE accepts any liability in this area. Adobe is a trademark of Adobe Systems Incorporated. Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies and IEEE members. In the unlikely event that a problem relating to it is found, please inform the ISO Central Secretariat or IEEE at the address given below.
  • Wait, I Don't Want to Be the Linux Administrator for SAS VA

    Wait, I Don't Want to Be the Linux Administrator for SAS VA

    SESUG Paper 88-2017 Wait, I don’t want to be the Linux Administrator for SAS VA Jonathan Boase; Zencos Consulting ABSTRACT Whether you are a new SAS administrator or switching to a Linux environment, you have a complex mission. This job becomes even more formidable when you are working with a system like SAS Visual Analytics that requires multiple users loading data daily. Eventually a user will have data issues or create a disruption that causes the system to malfunction. When that happens, what do you do next? In this paper, we will go through the basics of a SAS Visual Analytics Linux environment and how to troubleshoot the system when issues arise. INTRODUCTION Many companies choose to implement SAS Visual Analytics in a Linux environment. With a distributed deployment, it’s the only choice but many chose this operating system because it reduces operating costs. If you are the newly chosen SAS platform administrator, you might be more versed in a Windows environment and feel intimidated by Linux. This paper introduces using basic Linux commands and methods for troubleshooting a SAS Visual Analytics environment. The paper assumes that SAS Visual Analytics is installed on a SAS 9.4 platform for Linux and that the reader has some familiarity with other operating systems, such as Windows. PLATFORM ADMINISTRATION 101 SAS platform administrators work with three main product areas. Each area provides a different functionality based on the task the administrator needs to perform. The following figure defines each area and provides a general overview of its purpose. Figure 1 Platform Administrator Tools Operating System SAS Management SAS Environment •Contains installed Console Manager software •Access and manage the •Monitor the •Contains logs used for metadata environment troubleshooting •Control database •Configure custom alerts •Administer host system connections users •Manage user accounts •Manage the LASR server With any operating system, there is always a lot to learn.
  • UNIX Shell Programming (15CS35) Solution Internal Assessment

    UNIX Shell Programming (15CS35) Solution Internal Assessment

    UNIX Shell Programming (15CS35) Solution Internal Assessment- II November - 2016 1. Explain significance of following commands (2x5=10 M) i. cp ?????? progs Wild card ? matches any single character, hence the above command (cp) copies files whose names are six in length to progs directory ii. ls *.[xyz]* Wild card * matches any number of characters, hence the above command (ls) lists all the files having extension as either x, or y or z. iii. ls jones[0-9][0- 9][0-9] In the above command the character class[0-9] matches any digit between 0 to 9. Hence the above command lists all the files beginning with jones and having last three characters as any digit between 0 to 9. iv. echo * The above command lists all the file in the current directory. v. cp foo foo* The above command copies the file foo to file called foo*. Here the wild card * loses its meaning. 1. Write UNIX commands for the following (2 X 5= 10 M) i. Find and replace all the occurrences of unix with UNIX in the file after confirming the user. : 1,$s/unix/UNIX/gc ii. List all the files in the current directory which names are having exactly 5 characters and any number of characters in their extension. ls ?????.* iii. Copy all files stored in /home/vtu with .c, .cpp and .java extensions to progs sub- directory in current directory cp /home/vtu/*.{c,cpp,java} ./progs iv. Delete all files containing agra or agar in their file names. rm *ag[ra][ar]* v.
  • Process Text Streams Using Filters

    Process Text Streams Using Filters

    Process Text Streams Using Filters OBJECTIVE: Candidates should should be able to apply filters to text streams. 1 Process Text Streams Using Filters KeyKEY knowledge KNOWLEDGE area(s): AREAS: Send text files and output streams through text utility filters to modify the output using standard UNIX commands found in the GNU textutils package. 2 Process Text Streams Using Filters KEY FILES,TERMS, UTILITIES cat nl tail cut paste tr expand pr unexpand fmt sed uniq head sort wc hexdump split join tac 3 cat cat the editor - used as a rudimentary text editor. cat > short-message we are curious to meet penguins in Prague Crtl+D *Ctrl+D - command is used for ending interactive input. 4 cat cat the reader More commonly used to flush text to stdout. Options: -n number each line of output -b number only non-blank output lines -A show carriage return Example cat /etc/resolv.conf ▶ search mydomain.org nameserver 127.0.0.1 5 tac tac reads back-to-front This command is the same as cat except that the text is read from the last line to the first. tac short-message ▶ penguins in Prague to meet we are curious 6 head or tail using head or tail - often used to analyze logfiles. - by default, output 10 lines of text. List 20 first lines of /var/log/messages: head -n 20 /var/log/messages head -20 /var/log/messages List 20 last lines of /etc/aliases: tail -20 /etc/aliases 7 head or tail The tail utility has an added option that allows one to list the end of a text starting at a given line.
  • Modern Programming Languages CS508 Virtual University of Pakistan

    Modern Programming Languages CS508 Virtual University of Pakistan

    Modern Programming Languages (CS508) VU Modern Programming Languages CS508 Virtual University of Pakistan Leaders in Education Technology 1 © Copyright Virtual University of Pakistan Modern Programming Languages (CS508) VU TABLE of CONTENTS Course Objectives...........................................................................................................................4 Introduction and Historical Background (Lecture 1-8)..............................................................5 Language Evaluation Criterion.....................................................................................................6 Language Evaluation Criterion...................................................................................................15 An Introduction to SNOBOL (Lecture 9-12).............................................................................32 Ada Programming Language: An Introduction (Lecture 13-17).............................................45 LISP Programming Language: An Introduction (Lecture 18-21)...........................................63 PROLOG - Programming in Logic (Lecture 22-26) .................................................................77 Java Programming Language (Lecture 27-30)..........................................................................92 C# Programming Language (Lecture 31-34) ...........................................................................111 PHP – Personal Home Page PHP: Hypertext Preprocessor (Lecture 35-37)........................129 Modern Programming Languages-JavaScript
  • About ILE C/C++ Compiler Reference

    About ILE C/C++ Compiler Reference

    IBM i 7.3 Programming IBM Rational Development Studio for i ILE C/C++ Compiler Reference IBM SC09-4816-07 Note Before using this information and the product it supports, read the information in “Notices” on page 121. This edition applies to IBM® Rational® Development Studio for i (product number 5770-WDS) and to all subsequent releases and modifications until otherwise indicated in new editions. This version does not run on all reduced instruction set computer (RISC) models nor does it run on CISC models. This document may contain references to Licensed Internal Code. Licensed Internal Code is Machine Code and is licensed to you under the terms of the IBM License Agreement for Machine Code. © Copyright International Business Machines Corporation 1993, 2015. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents ILE C/C++ Compiler Reference............................................................................... 1 What is new for IBM i 7.3.............................................................................................................................3 PDF file for ILE C/C++ Compiler Reference.................................................................................................5 About ILE C/C++ Compiler Reference......................................................................................................... 7 Prerequisite and Related Information..................................................................................................
  • Drilling Network Stacks with Packetdrill

    Drilling Network Stacks with Packetdrill

    Drilling Network Stacks with packetdrill NEAL CARDWELL AND BARATH RAGHAVAN Neal Cardwell received an M.S. esting and troubleshooting network protocols and stacks can be in Computer Science from the painstaking. To ease this process, our team built packetdrill, a tool University of Washington, with that lets you write precise scripts to test entire network stacks, from research focused on TCP and T the system call layer down to the NIC hardware. packetdrill scripts use a Web performance. He joined familiar syntax and run in seconds, making them easy to use during develop- Google in 2002. Since then he has worked on networking software for google.com, the ment, debugging, and regression testing, and for learning and investigation. Googlebot web crawler, the network stack in Have you ever had the experience of staring at a long network trace, trying to figure out what the Linux kernel, and TCP performance and on earth went wrong? When a network protocol is not working right, how might you find the testing. [email protected] problem and fix it? Although tools like tcpdump allow us to peek under the hood, and tools like netperf help measure networks end-to-end, reproducing behavior is still hard, and know- Barath Raghavan received a ing when an issue has been fixed is even harder. Ph.D. in Computer Science from UC San Diego and a B.S. from These are the exact problems that our team used to encounter on a regular basis during UC Berkeley. He joined Google kernel network stack development. Here we describe packetdrill, which we built to enable in 2012 and was previously a scriptable network stack testing.
  • Technical Study Desktop Internationalization

    Technical Study Desktop Internationalization

    Technical Study Desktop Internationalization NIC CH A E L T S T U D Y [This page intentionally left blank] X/Open Technical Study Desktop Internationalisation X/Open Company Ltd. December 1995, X/Open Company Limited All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior permission of the copyright owners. X/Open Technical Study Desktop Internationalisation X/Open Document Number: E501 Published by X/Open Company Ltd., U.K. Any comments relating to the material contained in this document may be submitted to X/Open at: X/Open Company Limited Apex Plaza Forbury Road Reading Berkshire, RG1 1AX United Kingdom or by Electronic Mail to: [email protected] ii X/Open Technical Study (1995) Contents Chapter 1 Internationalisation.............................................................................. 1 1.1 Introduction ................................................................................................. 1 1.2 Character Sets and Encodings.................................................................. 2 1.3 The C Programming Language................................................................ 5 1.4 Internationalisation Support in POSIX .................................................. 6 1.5 Internationalisation Support in the X/Open CAE............................... 7 1.5.1 XPG4 Facilities.........................................................................................
  • Unix Standardization and Implementation

    Unix Standardization and Implementation

    Contents 1. Preface/Introduction 2. Standardization and Implementation 3. File I/O 4. Standard I/O Library 5. Files and Directories 6. System Data Files and Information 7. Environment of a Unix Process 8. Process Control 9. Signals 10.Inter-process Communication * All rights reserved, Tei-Wei Kuo, National Taiwan University, 2003. Standardization and Implementation Why Standardization? Proliferation of UNIX versions What should be done? The specifications of limits that each implementation must define! * All rights reserved, Tei-Wei Kuo, National Taiwan University, 2003. 1 UNIX Standardization ANSI C American National Standards Institute ISO/IEC 9899:1990 International Organization for Standardization (ISO) Syntax/Semantics of C, a standard library Purpose: Provide portability of conforming C programs to a wide variety of OS’s. 15 areas: Fig 2.1 – Page 27 * All rights reserved, Tei-Wei Kuo, National Taiwan University, 2003. UNIX Standardization ANSIC C <assert.h> - verify program assertion <ctype.h> - char types <errno.h> - error codes <float.h> - float point constants <limits.h> - implementation constants <locale.h> - locale catalogs <math.h> - mathematical constants <setjmp.h> - nonlocal goto <signal.h> - signals <stdarg.h> - variable argument lists <stddef.h> - standard definitions <stdio.h> - standard library <stdlib.h> - utilities functions <string.h> - string operations <time.h> - time and date * All rights reserved, Tei-Wei Kuo, National Taiwan University, 2003. 2 UNIX Standardization POSIX.1 (Portable Operating System Interface) developed by IEEE Not restricted for Unix-like systems and no distinction for system calls and library functions Originally IEEE Standard 1003.1-1988 1003.2: shells and utilities, 1003.7: system administrator, > 15 other communities Published as IEEE std 1003.1-1990, ISO/IEC9945-1:1990 New: the inclusion of symbolic links No superuser notion * All rights reserved, Tei-Wei Kuo, National Taiwan University, 2003.
  • The Linux Command Line

    The Linux Command Line

    The Linux Command Line Fifth Internet Edition William Shotts A LinuxCommand.org Book Copyright ©2008-2019, William E. Shotts, Jr. This work is licensed under the Creative Commons Attribution-Noncommercial-No De- rivative Works 3.0 United States License. To view a copy of this license, visit the link above or send a letter to Creative Commons, PO Box 1866, Mountain View, CA 94042. A version of this book is also available in printed form, published by No Starch Press. Copies may be purchased wherever fine books are sold. No Starch Press also offers elec- tronic formats for popular e-readers. They can be reached at: https://www.nostarch.com. Linux® is the registered trademark of Linus Torvalds. All other trademarks belong to their respective owners. This book is part of the LinuxCommand.org project, a site for Linux education and advo- cacy devoted to helping users of legacy operating systems migrate into the future. You may contact the LinuxCommand.org project at http://linuxcommand.org. Release History Version Date Description 19.01A January 28, 2019 Fifth Internet Edition (Corrected TOC) 19.01 January 17, 2019 Fifth Internet Edition. 17.10 October 19, 2017 Fourth Internet Edition. 16.07 July 28, 2016 Third Internet Edition. 13.07 July 6, 2013 Second Internet Edition. 09.12 December 14, 2009 First Internet Edition. Table of Contents Introduction....................................................................................................xvi Why Use the Command Line?......................................................................................xvi
  • Operating Systems Processes

    Operating Systems Processes

    Operating Systems Processes Eno Thereska [email protected] http://www.imperial.ac.uk/computing/current-students/courses/211/ Partly based on slides from Julie McCann and Cristian Cadar Administrativia • Lecturer: Dr Eno Thereska § Email: [email protected] § Office: Huxley 450 • Class website http://www.imperial.ac.uk/computing/current- students/courses/211/ 2 Tutorials • No separate tutorial slots § Tutorials embedded in lectures • Tutorial exercises, with solutions, distributed on the course website § You are responsible for studying on your own the ones that we don’t cover during the lectures § Let me know if you have any questions or would like to discuss any others in class 3 Tutorial question & warmup • List the most important resources that must be managed by an operating system in the following settings: § Supercomputer § Smartphone § ”Her” A lonely writer develops an unlikely relationship with an operating system designed to meet his every need. Copyright IMDB.com 4 Introduction to Processes •One of the oldest abstractions in computing § An instance of a program being executed, a running program •Allows a single processor to run multiple programs “simultaneously” § Processes turn a single CPU into multiple virtual CPUs § Each process runs on a virtual CPU 5 Why Have Processes? •Provide (the illusion of) concurrency § Real vs. apparent concurrency •Provide isolation § Each process has its own address space •Simplicity of programming § Firefox doesn’t need to worry about gcc •Allow better utilisation of machine resources § Different processes require different resources at a certain time 6 Concurrency Apparent Concurrency (pseudo-concurrency): A single hardware processor which is switched between processes by interleaving.
  • Moxa Nport Real TTY Driver for Arm-Based Platform Porting Guide

    Moxa Nport Real TTY Driver for Arm-Based Platform Porting Guide

    Moxa NPort Real TTY Driver for Arm-based Platform Porting Guide Moxa Technical Support Team [email protected] Contents 1 Introduction ...................................................................................2 2 Porting to the Moxa UC-Series—Arm-based Computer ....................2 2.1 Build binaries on a general Arm platform ...................................................... 2 2.2 Cross-compiler and the Real TTY driver ........................................................ 3 2.3 Moxa cross-compiling interactive script......................................................... 4 2.4 Manually build the Real TTY driver with a cross-compiler ................................ 5 2.5 Deploy cross-compiled binary to target......................................................... 8 3 Porting to Raspberry Pi OS .............................................................9 4 Porting to the Yocto Project on Raspberry Pi ................................ 10 4.1 Prerequisite............................................................................................... 10 4.2 Create a Moxa layer for the Yocto Project..................................................... 11 4.3 Install a Moxa layer into the Yocto Project.................................................... 17 4.4 Deploy the Yocto image in Raspberry Pi ....................................................... 17 4.5 Start the Real TTY driver in Raspberry Pi ..................................................... 18 4.6 Set the default tty mapping to the Real TTY configuration ............................