DOCSLIB.ORG

OS-9 Operating System User's Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
OS-9 Operating System User's Guide OS-9 Operating System User's Guide For Use with OS-9 Level One and OS-9 Level Two OS-9 Operating System User's Guide: For Use with OS-9 Level One and OS-9 Level Two Copyright © 1980, 1983 Microware Systems Corporation All Rights Reserved. Introduction .................................................................................................................. v 1. Getting Started... ....................................................................................................... 1 1.1. What You Need to Run OS-9 ........................................................................... 1 1.1.1. Starting the System ............................................................................... 1 1.1.2. In Case You Have Problems Starting OS-9 ............................................... 1 1.1.3. A Quick Introduction to the Use of the Keyboard and Disks ......................... 2 1.1.4. Initial Explorations ............................................................................... 2 1.2. Making a Backup of the System Disk ................................................................. 3 1.2.1. Formatting Blank Disks ......................................................................... 3 1.2.2. Running the Backup Program ................................................................. 4 2. Basic Interactive Functions .......................................................................................... 5 2.1. Running Commands and Basic Shell Operation .................................................... 5 2.1.1. Sending Output to the Printer ................................................................. 5 2.2. Shell Command Line Parameters ....................................................................... 6 2.3. Some Common Command Formats .................................................................... 7 2.4. Using the Keyboard and Video Display .............................................................. 7 2.4.1. Video Display Functions ........................................................................ 8 2.4.2. Keyboard Shift and Control Functions ...................................................... 8 2.4.3. Control Key Functions ........................................................................... 8 3. The OS-9 File System .............................................................................................. 11 3.1. Introduction to the Unified Input/Output System ................................................. 11 3.2. Pathlists: How Paths Are Named ...................................................................... 11 3.3. I/O Device Names ......................................................................................... 12 3.4. Multifile Devices And Directory Files ............................................................... 12 3.5. Creating and Using Directories ........................................................................ 13 3.6. Deleting Directory Files ................................................................................. 15 3.7. Additional Information About Directories .......................................................... 15 3.8. Using and Changing Working Directories .......................................................... 16 3.8.1. Automatic Selection of Working Directories ............................................ 16 3.8.2. Changing Current Working Directories ................................................... 17 3.8.3. Anonymous Directory Names ................................................................ 17 3.9. The File Security System ................................................................................ 18 3.9.1. Examining and Changing File Attributes ................................................. 18 3.10. Reading and Writing From Files ..................................................................... 19 3.10.1. File Usage in OS-9 ............................................................................ 19 3.10.2. Text Files ........................................................................................ 20 3.10.3. Random Access Data Files .................................................................. 20 3.10.4. Executable Program Module Files ........................................................ 20 3.10.5. Directory Files .................................................................................. 21 3.10.6. Miscellaneous File Usage ................................................................... 21 3.10.7. Record Lockout (Level Two Only) ....................................................... 21 3.11. Physical File Organization ............................................................................. 21 3.12. Physical Sector I/O ...................................................................................... 22 4. Advanced Features of the Shell .................................................................................. 25 4.1. A More Detailed Description Command Line Processing ...................................... 25 4.2. Execution Modifiers ....................................................................................... 26 4.2.1. Alternate Memory Size Modifier ........................................................... 26 4.2.2. I/O Redirection Modifiers ..................................................................... 26 4.3. Command Separators ..................................................................................... 27 4.3.1. Sequential Execution ........................................................................... 27 4.3.2. Concurrent Execution .......................................................................... 27 4.3.3. Pipes and Filters ................................................................................. 28 4.4. Command Grouping ....................................................................................... 28 4.5. Built-in Shell Commands and Options ............................................................... 29 4.6. Shell Procedure Files ..................................................................................... 30 4.7. Error Reporting ............................................................................................. 30 4.8. Running Compiled Intermediate Code Programs ................................................. 31 4.9. Setting Up Timesharing System Procedure Files ................................................. 31 iii OS-9 Operating System User's Guide 5. Multiprogramming and Memory Management ............................................................... 33 5.1. Processor Time Allocation and Timeslicing ........................................................ 33 5.2. Process States ............................................................................................... 34 5.3. Creation of New Processes .............................................................................. 34 5.4. Basic Memory Management Functions .............................................................. 35 5.4.1. Loading Program Modules Into Memory ................................................. 35 5.4.2. Loading Multiple Programs .................................................................. 37 5.4.3. Memory Fragmentation ........................................................................ 37 6. Use of the System Disk ............................................................................................ 39 6.1. The OS9Boot File ......................................................................................... 39 6.2. The SYS Directory ........................................................................................ 40 6.3. The Startup File ............................................................................................ 40 6.4. The CMDS Directory ..................................................................................... 40 6.5. The DEFS Directory ...................................................................................... 40 6.6. Changing System Disks .................................................................................. 40 6.7. Making New System Disks ............................................................................. 41 7. System Command Descriptions .................................................................................. 43 7.1. Formal Syntax Notation .................................................................................. 43 7.2. Commands ................................................................................................... 43 A. OS-9 Error Codes ................................................................................................... 89 A.1. Device Driver Errors ..................................................................................... 90 B. VDG Display System Functions ................................................................................. 91 B.1. The Video Display Generator .......................................................................... 91 B.2. Alpha Mode Display ..................................................................................... 91 B.3. Graphics Mode Display ................................................................................. 92 B.4. Get Status Commands ................................................................................... 94 C. Key Definitions With Hexadecimal Values .................................................................
Load more

Recommended publications
  • Freebsd-And-Git.Pdf
    FreeBSD and Git Ed Maste - FreeBSD Vendor Summit 2018 Purpose ● History and Context - ensure we’re starting from the same reference ● Identify next steps for more effective use / integration with Git / GitHub ● Understand what needs to be resolved for any future decision on Git as the primary repository Version control history ● CVS ○ 1993-2012 ● Subversion ○ src/ May 31 2008, r179447 ○ doc/www May 19, 2012 r38821 ○ ports July 14, 2012 r300894 ● Perforce ○ 2001-2018 ● Hg Mirror ● Git Mirror ○ 2011- Subversion Repositories svnsync repo svn Subversion & Git Repositories today svn2git git push svnsync git svn repo svn git github Repositories Today fork repo / Freebsd Downstream svn github github Repositories Today fork repo / Freebsd Downstream svn github github “Git is not a Version Control System” phk@ missive, reproduced at https://blog.feld.me/posts/2018/01/git-is-not-revision-control/ Subversion vs. Git: Myths and Facts https://svnvsgit.com/ “Git has a number of advantages in the popularity race, none of which are really to do with the technology” https://chapmanworld.com/2018/08/25/why-im-now-using-both-git-and-subversion-for-one-project/ 10 things I hate about Git https://stevebennett.me/2012/02/24/10-things-i-hate-about-git Git popularity Nobody uses Subversion anymore False. A myth. Despite all the marketing buzz related to Git, such notable open source projects as FreeBSD and LLVM continue to use Subversion as the main version control system. About 47% of other open source projects use Subversion too (while only 38% are on Git). (2016) https://svnvsgit.com/ Git popularity (2018) Git UI/UX Yes, it’s a mess.
    [Show full text]
  • Xilinx XAPP545 Statistical Profiler for Embedded IBM Powerpc, Application Note
    Product Not Recommended for New Designs Application Note: Virtex-II Pro R Statistical Profiler for Embedded IBM PowerPC XAPP545 (v1.0) September 15, 2004 Author: Njuguna Njoroge Summary This application note describes how to generate statistical profiling information from the IBM PowerPC 405D, which is embedded in some Virtex-II Pro™ FPGAs. Specifically, the application note details how to convert trace output files generated from the Agilent Technologies Trace Port Analyzer into a gprof (GNU profiler) readable format. The gprof tool is capable of generating a histogram of a program's functions and a call-graph table of those functions. Introduction Profiling allows a programmer to assess where a program is spending most of its time and how frequently functions are being called. With this information, a programmer can gain insight as to what optimizations to make. In some cases, a programmer can identify bugs that would be otherwise undetectable. Using the RISCWatch application is a first step in profiling a program. Nonetheless, manually mulling through approximately 350 MB (or 8 million cycles) of trace data to discern the run-time profile of the program is a fruitless endeavor. In fact, the designers of RISCWatch realized this, so they standardized the trace output format to enable post processing of the trace. The regular format of the trace files allows scripts to parse through the trace and convert it to the gprof format. By converting the trace files into the gprof format, the widespread use of gprof in the profiling community
    [Show full text]
  • Getting Started With... Berkeley Software for UNIX† on the VAX‡ (The Third Berkeley Software Distribution)
    Getting started with... Berkeley Software for UNIX† on the VAX‡ (The third Berkeley Software Distribution) A package of software for UNIX developed at the Computer Science Division of the University of California at Berkeley is installed on our system. This package includes a new version of the operating sys- tem kernel which supports a virtual memory, demand-paged environment. While the kernel change should be transparent to most programs, there are some things you should know if you plan to run large programs to optimize their performance in a virtual memory environment. There are also a number of other new pro- grams which are now installed on our machine; the more important of these are described below. Documentation The new software is described in two new volumes of documentation. The first is a new version of volume 1 of the UNIX programmers manual which has integrated manual pages for the distributed software and incorporates changes to the system made while introducing the virtual memory facility. The second volume of documentation is numbered volume 2c, of which this paper is a section. This volume contains papers about programs which are in the distribution package. Where are the programs? Most new programs from Berkeley reside in the directory /usr/ucb. A major exception is the C shell, csh, which lives in /bin. We will later describe how you can arrange for the programs in the distribution to be part of your normal working environment. Making use of the Virtual Memory With a virtual memory system, it is no longer necessary for running programs to be fully resident in memory.
    [Show full text]
  • Tanium™ Client Deployment Guide
    Tanium™ Client Deployment Guide Version 6.0.314.XXXX February 05, 2018 The information in this document is subject to change without notice. Further, the information provided in this document is provided “as is” and is believed to be accurate, but is presented without any warranty of any kind, express or implied, except as provided in Tanium’s customer sales terms and conditions. Unless so otherwise provided, Tanium assumes no liability whatsoever, and in no event shall Tanium or its suppliers be liable for any indirect, special, consequential, or incidental damages, including without limitation, lost profits or loss or damage to data arising out of the use or inability to use this document, even if Tanium Inc. has been advised of the possibility of such damages. Any IP addresses used in this document are not intended to be actual addresses. Any examples, command display output, network topology diagrams, and other figures included in this document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental. Please visit https://docs.tanium.com for the most current Tanium product documentation. Tanium is a trademark of Tanium, Inc. in the U.S. and other countries. Third-party trademarks mentioned are the property of their respective owners. © 2018 Tanium Inc. All rights reserved. © 2018 Tanium Inc. All Rights Reserved Page 2 Table of contents Overview 8 What is the Tanium Client? 8 Registration 9 Client peering 9 File distribution 11 Prerequisites 14 Host system requirements 14 Admin account 15 Network connectivity and firewall 16 Host system security exceptions 16 Deployment options summary 18 Using the Tanium Client Deployment Tool 21 Methods 21 Before you begin 21 Install the Client Deployment Tool 23 Deploy the Tanium Client 25 Check for Tanium Client updates 32 Troubleshooting 33 Logs 34 Advanced settings 34 Deploying the Tanium Client to Windows endpoints 36 Step 1: Create the installer 36 Step 2: Execute the installer 37 © 2018 Tanium Inc.
    [Show full text]
  • Microware OS-9 Release Notes Version 3.2
    Microware OS-9 Release Notes Version 4.1 RadiSys. 118th Street Des Moines, Iowa 50325 515-223-8000 www.radisys.com Revision A • May 2003 Copyright and publication information Reproduction notice This manual reflects version 4.1 of Microware OS-9. The software described in this document is intended to Reproduction of this document, in part or whole, by be used on a single computer system. RadiSys Corpo- any means, electrical, mechanical, magnetic, optical, ration expressly prohibits any reproduction of the soft- chemical, manual, or otherwise is prohibited, without written permission from RadiSys Corporation. ware on tape, disk, or any other medium except for backup purposes. Distribution of this software, in part Disclaimer or whole, to any other party or on any other system may constitute copyright infringements and misappropria- The information contained herein is believed to be accurate as of the date of publication. However, tion of trade secrets and confidential processes which RadiSys Corporation will not be liable for any damages are the property of RadiSys Corporation and/or other including indirect or consequential, from use of the parties. Unauthorized distribution of software may OS-9 operating system, Microware-provided software, cause damages far in excess of the value of the copies or reliance on the accuracy of this documentation. involved. The information contained herein is subject to change without notice. May 2003 Copyright ©2003 by RadiSys Corporation. All rights reserved. EPC and RadiSys are registered trademarks of RadiSys Corporation. ASM, Brahma, DAI, DAQ, MultiPro, SAIB, Spirit, and ValuePro are trademarks of RadiSys Corporation. DAVID, MAUI, OS-9, OS-9000, and SoftStax are registered trademarks of RadiSys Corporation.
    [Show full text]
  • VMS CRA Y Station Now Available It Is Now Possible to Submit Jobs Functions Closely
    VMS CRA Y Station Now Available It is now possible to submit jobs Functions closely. It is implemented as a to the CRAY-1 from UCC's VAX/VMS The VMS station provides these series of commands entered in system. functions: response to the system's $ A CRAY-1 running the cos oper­ prompt. The commands look like ating system requires another -It submits jobs to the CRAY-1, VMS commands: they have pa­ computer to act as a "front-end" and returns output as a file un­ rameters and /qualifiers; they fol­ system. You prepare jobs and der the user's VMS directory. low much the same syntax and data on the front-end system, us­ -It transfers files between the interpretation rules (for example, ing whatever tools that system machines using the cos AC­ wild cards are handled correctly); provides, then submit the files as QUIRE and DISPOSE commands. and they prompt for required a batch job to the CRAY for proc­ The source of an ACQUIREd file parameters not present on the essing. Output is returned to the can be disk or tape; the desti­ command line. You can always front-end system for viewing. nation of a DISPOSEd file can recognize a station command, The software that runs on the be disk, tape, printer, or the though, because it always begins front-end machine to provide this VMS batch input queue. with the letter C. For example, communication is called a -At your option, it sends bulle­ the station command to submit a "station." tins to the terminal chronicling job to the CRAY is CSUBMIT.
    [Show full text]
  • CS 350 Operating Systems Spring 2021
    CS 350 Operating Systems Spring 2021 4. Process II Discussion 1: Question? • Why do UNIX OSes use the combination of “fork() + exec()” to create a new process (from a program)? • Can we directly call exec() to create a new process? Or, do you have better ideas/designs for creating a new process? • Hints: To answer this question: think about the possible advantages of this solution. Fork Parent process Child process Exec New program image in execution 2 Discussion 1: Background • Motived by the UNIX shell • $ echo “Hello world!” • $ Hello world! • shell figures out where in the file system the executable “echo” resides, calls fork() to create a new child process, calls exec() to run the command, and then waits for the command to complete by calling wait(). • You can see that you can use fork(), exec() and wait() to implement a shell program – our project! • But what is the benefit of separating fork() and exec() in creating a new process? 3 Discussion 1: Case study • The following program implements the command: • $ wc p3.c > p4.output # wc counts the word number in p3.c • # the result is redirected to p4.output Close default standard output (to terminal) open file p4.output 4 Discussion 1: Case study • $ wc p3.c # wc outputs the result to the default standard output, specified by STDOUT_FILENO • By default, STDOUT_FILENO points to the terminal output. • However, we close this default standard output → close(STDOUT_FILENO ); • Then, when we open the file “p4.output” • A file descriptor will be assigned to this file • UNIX systems start looking for free file descriptors from the beginning of the file descriptor table (i.e., at zero).
    [Show full text]
  • An Efficient and Portable SIMD Algorithm for Charge/Current Deposition in Particle-In-Cell Codes✩
    Computer Physics Communications 210 (2017) 145–154 Contents lists available at ScienceDirect Computer Physics Communications journal homepage: www.elsevier.com/locate/cpc An efficient and portable SIMD algorithm for charge/current deposition in Particle-In-Cell codesI H. Vincenti a,b,∗, M. Lobet a, R. Lehe a, R. Sasanka c, J.-L. Vay a a Lawrence Berkeley National Laboratory, 1 Cyclotron Road, Berkeley, CA, USA b Lasers Interactions and Dynamics Laboratory (LIDyL), Commissariat À l'Energie Atomique, Gif-Sur-Yvette, France c Intel Corporation, OR, USA a r t i c l e i n f o a b s t r a c t Article history: In current computer architectures, data movement (from die to network) is by far the most energy Received 9 January 2016 consuming part of an algorithm (≈20 pJ=word on-die to ≈10,000 pJ/word on the network). To increase Received in revised form memory locality at the hardware level and reduce energy consumption related to data movement, 10 August 2016 future exascale computers tend to use many-core processors on each compute nodes that will have Accepted 19 August 2016 a reduced clock speed to allow for efficient cooling. To compensate for frequency decrease, machine Available online 19 September 2016 vendors are making use of long SIMD instruction registers that are able to process multiple data with one arithmetic operator in one clock cycle. SIMD register length is expected to double every four years. As Keywords: Particle-In-Cell method a consequence, Particle-In-Cell (PIC) codes will have to achieve good vectorization to fully take advantage OpenMP of these upcoming architectures.
    [Show full text]
  • The Dragonflybsd Operating System
    1 The DragonFlyBSD Operating System Jeffrey M. Hsu, Member, FreeBSD and DragonFlyBSD directories with slightly over 8 million lines of code, 2 million Abstract— The DragonFlyBSD operating system is a fork of of which are in the kernel. the highly successful FreeBSD operating system. Its goals are to The project has a number of resources available to the maintain the high quality and performance of the FreeBSD 4 public, including an on-line CVS repository with mirror sites, branch, while exploiting new concepts to further improve accessible through the web as well as the cvsup service, performance and stability. In this paper, we discuss the motivation for a new BSD operating system, new concepts being mailing list forums, and a bug submission system. explored in the BSD context, the software infrastructure put in place to explore these concepts, and their application to the III. MOTIVATION network subsystem in particular. A. Technical Goals Index Terms— Message passing, Multiprocessing, Network The DragonFlyBSD operating system has several long- operating systems, Protocols, System software. range technical goals that it hopes to accomplish within the next few years. The first goal is to add lightweight threads to the BSD kernel. These threads are lightweight in the sense I. INTRODUCTION that, while user processes have an associated thread and a HE DragonFlyBSD operating system is a fork of the process context, kernel processes are pure threads with no T highly successful FreeBSD operating system. Its goals are process context. The threading model makes several to maintain the high quality and performance of the FreeBSD guarantees with respect to scheduling to ensure high 4 branch, while exploring new concepts to further improve performance and simplify reasoning about concurrency.
    [Show full text]
  • ROM OS-9 Into Your Coco Boisy G
    ROM OS-9 Into Your CoCo Boisy G. Pitre Imagine turning on your CoCo and instead of being greeted with the all-to-familiar Microsoft BASIC copyright message and OK prompt, you see “OS9 BOOT”. In two seconds, the OS-9 copyright banner and an OS9: prompt appears, and you have an OS-9 shell at your fingertips without having anything plugged in the CoCo’s expansion port! It may sound far out, but it’s actually quite easy to set up a ROM-based OS-9 CoCo. It can be done simply by replacing the Microsoft BASIC ROM that comes in all CoCo systems with a ROM containing OS-9 with special modifications to certain modules to allow booting from ROM. OS-9 Sans Disk? It may sound strange that OS-9 could be run totally from ROM, but indeed, this is the way that OS-9 was designed to run: without any disk storage. In the embedded OS-9 world, a disk drive or other mass storage device is incidental, or in most cases, impractical. Yet in the CoCo world, we have become accustomed to thinking of OS-9 as a Disk Operating System (DOS) as opposed to an embedded operating system. This was reinforced by the fact that Tandy/Radio Shack catalogs stated that OS-9 required a disk drive, and indeed, for the particular boot strategy that Tandy and Microware employed, a disk drive was and still is necessary. So if it is possible to use OS-9 without a disk drive, then what’s the point? How useful can OS-9 be without a disk drive? The answer: extremely useful.
    [Show full text]
  • Ascii, Baudot, and the Radio Amateur
    ASCII, BAUDOT AND THE RADIO AMATEUR George W. Henry, Jr. K9GWT Copyright © 1980by Hal Communications Corp., Urbana, Illinois HAL COMMUNICATIONS CORP. BOX365 ASCII, BAUDOT, AND THE RADIO AMATEUR The 1970's have brought a revolution to amateur radio RTTY equipment separate wire to and from the terminal device. Such codes are found in com­ and techniques, the latest being the addition of the ASCII computer code. mon use with computer and line printer devices. Radio amateurs in the Effective March 17, 1980, radio amateurs in the United States have been United States are currently authorized to use either the Baudot or ASCII authorized by the FCC to use the American Standard Code for Information serial asynchronous TTY codes. Interchange(ASCII) as well as the older "Baudot" code for RTTY com­ munications. This paper discusses the differences between the two codes, The Baudot TTY Code provides some definitions for RTTY terms, and examines the various inter­ facing standards used with ASCII and Baudot terminals. One of the first data codes used with mechanical printing machines uses a total of five data pulses to represent the alphabet, numerals, and symbols. Constructio11 of RTTY Codes This code is commonly called the Baudot or Murray telegraph code after the work done by these two pioneers. Although commonly called the Baudot Mark Ull s,.ce: code in the United States, a similar code is usually called the Murray code in other parts of the world and is formally defined as the International Newcomers to amateur radio RTTY soon discover a whole new set of terms, Telegraphic Alphabet No.
    [Show full text]
  • Bapco® Eecomark V2 User Guide
    BAPCo® EEcoMark v2 User Guide BAPCo is a U.S. Registered Trademark of the Business Applications Performance Corporation. EEcoMark is a U.S. Registered Trademark of the Business Applications Performance Corporation. Copyright © 2012 Business Applications Performance Corporation. All other brand and product names are trademarks or registered trademarks of their respective holders Contents 1.0 General .................................................................................................................................................... 4 1.1 Terminology ........................................................................................................................................ 4 2.0 Setup ....................................................................................................................................................... 5 2.1 Minimum System Requirements ........................................................................................................ 5 2.2 Hardware Setup .................................................................................................................................. 5 2.3 Software Setup .................................................................................................................................... 6 3.0 Configuration .......................................................................................................................................... 7 3.1 Guidelines ..........................................................................................................................................
    [Show full text]