Table of Contents CHAPTER 1 INTRODUCTION 1.1 WHAT IS AN OPERATING SYSTEM? 1.2 HISTORY OF OPERATING SYSTEMS 1.3 OPERATING SYSTEM CONCEPTS 1.4 SYSTEM CALLS 1.5 OPERATING SYSTEM STRUCTURE 1.6 OUTLINE OF THE REST OF THIS BOOK 1.7 SUMMARY CHAPTER 2 PROCESSES 2.1 INTRODUCTION TO PROCESSES 2.2 INTERPROCESS COMMUNICATION 2.3 CLASSICAL IPC PROBLEMS 2.4 SCHEDULING 2.5 OVERVIEW OF PROCESSES IN MINIX 3 2.6 IMPLEMENTATION OF PROCESSES IN MINIX 3 2.7 THE SYSTEM TASK IN MINIX 3 2.8 THE CLOCK TASK IN MINIX 3 2.9 SUMMARY CHAPTER 3 INPUT/OUTPUT 3.1 PRINCIPLES OF I/O HARDWARE 3.2 PRINCIPLES OF I/O SOFTWARE 3.3 DEADLOCKS 3.4 OVERVIEW OF I/O IN MINIX 3 3.5 BLOCK DEVICES IN MINIX 3 3.6 RAM DISKS 3.7 DISKS 3.8 TERMINALS 3.9 SUMMARY CHAPTER 4 MEMORY MANAGEMENT 4.1 BASIC MEMORY MANAGEMENT 4.2 SWAPPING 4.3 VIRTUAL MEMORY 4.4 PAGE REPLACEMENT ALGORITHMS 4.5 DESIGN ISSUES FOR PAGING SYSTEMS 4.6 SEGMENTATION 4.7 OVERVIEW OF THE MINIX 3 PROCESS MANAGER 4.8 IMPLEMENTATION OF THE MINIX 3 PROCESS MANAGER 4.9 SUMMARY CHAPTER 5 FILE SYSTEMS 5.1 FILES 5.2 DIRECTORIES 5.3 FILE SYSTEM IMPLEMENTATION 5.4 SECURITY 5.5 PROTECTION MECHANISMS 5.6 OVERVIEW OF THE MINIX 3 FILE SYSTEM 5.7 IMPLEMENTATION OF THE MINIX 3 FILE SYSTEM 5.8 SUMMARY CHAPTER 6 READING LIST AND BIBLIOGRAPHY 6.1 SUGGESTIONS FOR FURTHER READING 6.2 ALPHABETICAL BIBLIOGRAPHY APPENDIX A - INSTALLING MINIX 3 APPENDIX B - MINIX 3 SOURCE CODE LISTING APPENDIX C - INDEX TO FILES INDEX

Operating Systems: Design and Implementation

Anyone who teaches a course in Computer Organization is faced with the problem of supplementing lectures and readings with hands-on experience for the students in microprogramming, both as laboratory exercises and homework. Many are using simulators to fill this role, as witnessed by frequent papers in this and other forums. (The “no fewer than three... since 1987,” in [Fu] is a considerable underestimate.) Rarely in these papers is discussed the educational goals behind the design and application of these simulators; instead, the specific capabilities and architectures are generally described, frequently accompanied by sample output and screen dumps. Related papers discuss actual microprogrammable hardware, generally interfaced with a microcomputer monitor. A selection of these papers appears in the bibliography; space precludes a complete list. The present paper describes the goals upon which one such simulator was based. This program, Micro, was originally written by the author in the Summer of 1989 and has been enhanced considerably during the following years. It is based on the data path used as the primary example in the Computer Organization book by Hamacher, et. al. [HVZ], particukwly in Chapter 5. It has been used for over four years in an undergraduate hardware-oriented Computer Organization course, and once in a Master’s level graduate Organization course.

Simulation in computer organization: a goals based study

A modern computer system provides its support via system software that consists of applications such as an assembler, a linker, a loader and virtual machines. It is of prime importance to give students that are learning system-software concepts a solid base of knowledge without any unnecessary details. To make the subject easy to understand we designed a simulator for a hypothetical computer that is already used in several courses on system software. In the paper, we describe the simulator's behavior as well as its design and implementation. Additionally, we present three case studies of using a simulator in teaching and describe our experience of its use in a course on system software. From the experience of using the simulator in a pedagogical process we conclude that it decreases the time invested by the students to comprehend the topic, and at the same time it enables in depth understanding. © 2013 Wiley Periodicals, Inc. Comput Appl Eng Educ 23:137–146, 2015; View this article online at wileyonlinelibrary.com/journal/cae; DOI 10.1002/cae.21585

SicSim: A simulator of the educational SIC/XE computer for a system-software course

There is no doubt that the most difficult topic to teach in a Computer Architecture and Organization course is microprogramming. In this paper the author describes a Pascal programming project in which the students write a simulator for a microprogram. The project has been assigned several times with very satisfying results for both the instructor and the students.

Microcode simulation in the computer architecture course

xSICSIH is an X-based graphical interface for the SICSIM computer simulation tool. Its graphical portrayal of register-level components tmwforms the ‘black box” SICSIM machine into a ‘visual computer”, helping students understand how computers work. Single step, fast-ezecution, and breakpoints are among the control features helpful for debugging assembly language programs. Automatic disassembly and format conversions and displays for comparing expected to actual execution reduce fiwstmtion in debugging loader, macro processor, and assembler projects.

/pdf/a-graphical-computer-simulator-for-systems-programming-4yo859chje.pdf

A graphical computer simulator for systems programming courses

Microprogramming is no generally available to programmers because it may involve modification of a machine's native language. A hypothetical computer can provide a simulator for microprogramming projects and add considerably to one's understanding of the subject of microprogramming and the concept of a multilevel machine. The classical text, Structured Computer Organization by Andrew S. Tanenbaum, contains a design for such a hypothetical computer. This paper presents an implementation of this machine with a user interface to permit development of microprograms as well as development of programs at the conventional machine language programming level. The user interface is similar to that of MS-DOS's DEBUG program. In addition to providing the basis for projects in Computer Architecture and Computer Organization classes, the simulator is being used as a simplified hypothetical machine in a Systems Programming class for the development of assembler, linker, and loader projects.

A hypothetical computer to simulate microprogramming and conventional machine language

Microprogramming is not generally available to programmers because it may involve modification of a machine's native language. A hypothetical computer can provide a simulator for microprogramming projects and add considerably to one's understanding of the subject of microprogramming and the concept of a multilevel machine. The classical text, Structured Computer Organization by Andrew S. Tanenbaum, contains a design for such a hypothetical computer. This paper presents an implementation of this machine with a user interface to permit development of microprograms as well as development of programs at the conventional machine language programming level. The user interface is similar to that of MS-DOS's DEBUG program. In addition to providing the basis for projects in Computer Architecture and Computer Organization classes, the simulator is being used as a simplified hypothetical machine in a Systems Programming class for the development of assembler, linker, and loader projects.

A multitasking operating system for an IBM PC or compatible has been developed to provide students with an educational opportunity for hands-on experience with concurrent programming concepts. The operating system includes features which permit users to observe performance as a function of the I/O versus compute bound processes. Although other such educational operating systems exist, this operating system is limited primarily to process management. The small size of the operating system makes it easy to comprehend in a single term course. It is, however, a powerful real time executive for applications such as small, embedded systems.

A small operating system

A system generation utility has been developed to assist students in producing IBM PC-based multitasking applications targeted for the small operating system (SOS) developed by Jerry E. Sayers. Our aim is to augment SOS by enabling a student to interactively tailor the characteristics of the operating system to meet the requirements of a particular application. The system allows the user to adjust factors such as: initial state, priority, and scheduling method of concurrently executed tasks, and, also, use of system resources. A custom operating system is produced by invoking a MAKE utility to bind SOS with application-specific code, in addition to intermediate source code created during the system generation process.Testing of the system included implementing an application that adds column vectors in a 5 × 5000 matrix concurrently. Further testing involves using the system generation utility along with SOS as part of an undergraduate operating systems class at East Tennessee State University.

Jerry E. Sayers

Papers

A hypothetical computer to simulate microprogramming and conventional machine language

A hypothetical computer to simulate microprogramming and conventional machine language

A small operating system

A system generation for a small operating system