Academia.eduAcademia.edu

Outline

Title
Abstract
Introduction of Operating System
Finding Files
Summary for Useful Common Commands
Introduction of Pico Editor
Introduction of the Emacs Editor
Running Command in Foreground or in Background
Putting Process in Background
Unix Inodes and Data Structures for File System
Program Control Flow Statement (C): Case Statement
Processing Numeric Data
TCP/Ip Protocol Suite
Protocols in Application Layer
Protocols in Transport Layer
Protocols in Network Layer
Protocols in Link Layer
An Example for TCP/Ip Protocol Suite
Ip Protocol
TCP Protocol and Applications
Email Protocols and Programs
Email Protocols
Udp Protocol and Applications
Udp Protocol
Summary
References
All Topics
Computer Science

UNIX Operating System

Profile image of Yong YueYong Yue

2011

https://doi.org/10.1007/978-3-642-20432-6
visibility

…

description

382 pages

link

1 file

Abstract

This book presents UNIX as a practical case of operating systems for the reader to understand and master deeply and tangibly the theory and algorithms in operating systems. It gives discussions and studies on the hierarchical structure, principles, applications, shells, development, and management of the UNIX operation system multi-dimensionally, systematically and from the elementary to the profound. It brings readers to go into the inside of the UNIX operating system and lets them understand clearly what and how UNIX operating system functions. This book consists of 11 chapters. The first two chapters discuss the background of UNIX operating system (OS), and give a whole picture of what UNIX OS looks like and the evolution of UNIX. Chapter 3 focuses on the editors that will be used frequently by UNIX users, no matter who are regular users or seasoned programmers. Chapters 4, 5, 6, and 7 concentrate on the services of the UNIX kernel. Chapter 4 zooms in the process management, which is usually hidden from the final users. Chapter 5 is to discuss the UNIX memory management, which cooperates with the process management to accomplish the processes' concurrently running. Chapter 6 introduces the UNIX file management, which is involved almost in every service that the UNIX kernel provides to the users. Chapter 6, however, for UNIX users, is fundamentally useful to understand how UNIX works. Chapter 7 explores UNIX I/O, I/O redirection and piping. As UNIX treats its hardware devices as special files, this mechanism brings a whole different concept on UNIX input and output devices. I/O redirection and piping are two useful tools that can be used to deduce different commands to control the terminals through UNIX system calls. UNIX has almost as many shells as versions of the UNIX operating system. Chapter 8 introduces some types of shells, shell evolution, and some common concepts in UNIX shells. As there are so many kinds of shells, it vi Preface Preface vii mers and also confine their imagination and creativity. This tendency can also affect the ability of system development newcomers to develop an intact software system that can handle software as well as hardware by restricting the field of vision to some detached modules or applications so as to result in software maintenance costly and complicated. Further, just understanding the theory of operating systems, readers cannot image and understand well how the operating system works. With UNIX as a real case, readers can map the abstract algorithms, mechanisms and strategies of operating system theory into the real modules, functions and programs of UNIX implementation one-to-one. The abstract theory can be exemplified. In this way, as the promising programmers, readers can understand well and master these algorithms and mechanisms, practice them in their own development, and stimulate novel algorithms and mechanisms that may be more effective and efficient to their own context. It seems as if a repetition of the old tale when considering the discussion on UNIX, which, all in all, reached its heyday around 1980s. In the latest two decades, however, due to commercial purposes and activities, there are no other operating systems like UNIX, which is so thoroughly open for the academic community to learn and do research. In addition, there are plenty of references about UNIX that have been published, but most of them were originally published around 1980s. For the recent promising programmers, the published classics may be somewhat obscure because of the sparse context that might not be necessary for readers in those days but can be unfamiliar to nowadays readers. As the well-known rapid development of computer hardware in the latest decades, computer architecture and structure have made a big change. This change has also wielded a deep influence on the theories and concepts of computer, which makes the difficulty for recent readers to understand well descriptions and expressions in the published UNIX classics, and to map them properly into practical cases. It is possible to build an obstacle for readers to learn from them. Otherwise, for the operating system construction, which belongs to software developments but resides the one of the most exciting and integrated of software development, it would be a pity and defect if losing an operational means. Fortunately, this means can be gained by doing research on UNIX. It is taken that UNIX has its own philosophy and several items in the philosophy are written in different references. If having the right, we can say that the most important one should be the UNIX programmers' dedication and passion to their work. UNIX is also deemed to a programmer's OS. UNIX programmers have done a wonderful work just as for tackling a necessary affair, from which others else really benefit. It is critical for the academic community. UNIX benefited also from those days. If AT&T, at that time, could market computer products without a 1956 Consent Decree signed with the Federal Government, and if Bell Laboratories did not withdraw Ken Thompson and others from the MULTICS project, and if Professor Robert S. Fabry of the viii Preface University of California at Berkeley did not contact Ken Thompson at the Symposium on Operating Systems Principles at Purdue University in November 1973, we would have a totally different story about UNIX. It needs the open and free soil to breed an academic activity. The more relieved the outside environment is, the more natural the academic activity develops within the environment. UNIX was destined for being flourishing in its day. Even though being just observers on this period of history, the authors of this book are impressed by the passion and concentration that UNIX developers had in the day. During five years of teaching UNIX in their campuses, the authors realized that if this fantastic piece of history was not introduced to more readers, it would be a pity for authors as well as readers. In this high-technology and high-material-civilization age, UNIX development process can give readers some new inspiration-a glowing motivation from inside to accomplish a meaningful work. Preface ix of operating systems and the underlying hardware parts. For real developers and programmers, it may take a big risk to sit on a seemingly-transparent but unfamiliar system to do their developments-finally they may encounter some bugs that they cannot tackle. They have to experience something that can let them understand what really make the construction of an operating system, what the kernel of an operating system does for users, and how algorithms and mechanisms in the theory of operating systems are implemented. Even though the disassembled UNIX cannot tell all the story of a well-designed modern or future operating system, it can give the mapping or clues to different functions and services, which can be treated as an anatomy lecture of a promising surgeon. In other words, a well-designed operating system may be daunting for a promising developer, which is complicated and confused. The simplicity and clarity of UNIX can help readers walk out of the swamp and sort out the confusion, and lead them to face and tackle more sophisticated problems. Knowledge needs to renew and information needs to update. The updating includes the expression of a convincing, successful and classical process in a proper, timely and new way. Maybe the UNIX story is old, but it can give different inspirations to people in different ages, which is still developing. The authors hope the developing can be reflected in this book. One of the targets of this book is to let the UNIX philosophy propagate and carry on. Let more readers comprehend this philosophy's results-the fast development, maintainability and scalability of an operating system. The authors also want to present readers (especially, programmers) two aspects of a whole operating system and any one of its subsystems, in other words, to give not only the inside implementation process, which is viewed by the system or application programmers, but also the outside application performance, which is usually felt by the end users. In this way, readers cannot only keep the view of the system constructors but also be considerate of the end users when developing their systems. During development, a system can benefit from that its developers can consider more for its end users. For readers, it is easy to enter the learning from user interfaces of UNIX operating systems since they have usually had the experience of using one of operating systems in their daily works or lives. Thus, in this book, we take this strategy: when starting one topic, we present it from its user interface, and then go into the kernel with the system calls and lower-level algorithms if possible. In this way, readers can be brought from a familiar environment into elusive and deep techniques. To describe algorithms, we try to use common English language rather than some computer language, such as C or assembly language. The primary x Preface reason is: we try to make algorithms more readable and help readers save their time and effort. For a programmer, it is often time-consuming to read some code that is written by others. This book is written for the wide groups of readers who want to master the professional knowledge of operating systems through a real and opensource case. Its main readers include graduates, senior undergraduates and teachers of computer and software majors, and potential researchers on applicable computing and engineering modeling. The readers can also be ones who maybe have some or have not much knowledge related to Computer Science and Technology and Software Engineering, but have a strong interest in these fields and want to get into them quickly, acquire some useful and important knowledge and reach an advanced level in the relevant fields after learning. This book can help readers construct, not...

Related papers

OPERATING SYSTEMS THREE EASY PIECES
shiva eshwari

iii iv humorous style. Whether you find them useful, or humorous, well, that's another matter entirely.

View PDFchevron_right
Advanced administration GNU/Linux operating system, february 2010
Josep Jorba

2010

View PDFchevron_right
The Fragrance of Unix
Martin T Ranang

2003

Abstract: This compendium is meant to be a quick introduction to using Unix-similar operating systems. It is intended for people with some computer experience, but little or no experience with Unix systems. Hopefully, you will also find it useful as a reference matter where you can look things up. The author hopes that The Fragrance of Unix will give you a sufficient introduction to Unix systems that you will be able to continue using them on your own.

View PDFchevron_right
ROAD MAP FOR PART ONE Chapter 1 Computer System Overview Chapter 2 Operating System Overview
Ugur Agansoy

An operating system mediates among application programs, utilities, and users, on the one hand, and the computer system hardware on the other. To appreciate the functionality of the operating system and the design issues involved, one must have some appreciation for computer organization and architecture. Chapter 1 provides a brief survey of the processor, memory, and Input/Output (I/O) elements of a computer system. The topic of operating system (OS) design covers a huge territory, and it is easy to get lost in the details and lose the context of a discussion of a particular issue. Chapter 2 provides an overview to which the reader can return at any point in the book for context. We begin with a statement of the objectives and functions of an operating system. Then some historically important systems and OS functions are described. This discussion allows us to present some fundamental OS design principles in a simple environment so that the relationship among various OS functions is clear. The chapter next highlights important characteristics of modern operating systems. Throughout the book, as various topics are discussed, it is necessary to talk about both fundamental, well-established principles as well as more recent innovations in OS design. The discussion in this chapter alerts the reader to this blend of established and recent design approaches that must be addressed. Finally, we present an overview of Windows, UNIX, and Linux; this discussion establishes the general architecture of these systems, providing context for the detailed discussions to follow.

View PDFchevron_right
Operating systems: design and implementation
Arti Kumari

1997

View PDFchevron_right
An operating systems vade mecum
Raphael Finkel

1986

Which page should be swapped out? 114 Startup-phase conflicts. 115 Perspective 116 Further reading 118 Exercises 118 Chapter 4 RESOURCE DEADLOCK 121 Nuts and bolts 122 Deadlock and starvation 124 Dining philosophers 128 One-shot allocation 131 Hierarchical allocation 132 Advance-claim algorithm 133 Deadlock detection 138 Deadlock recovery 141 Starvation 141 Perspective 142 Further reading 144 Exercises 144 Chapter 5 TRANSPUT 147 Device hardware 148 1.1 Disks 148 Contents vii 2.2 Virtual interrupts 297 2.3 Pipes 298 2.4 Ports 301 Data. Access. 302 Naming and transfer. 303 2.5 Semantics of Read and Write 307 3 Distributed operating systems 308 3.1 Multiprocessors 308 3.2 Local-area networks 309 3.3 Long-haul networks 311 3.4 Multicomputers 312 4 The communication-kernel approach 313 4.1 Processes and threads 314 4.2 Communication 315 4.3 Space management 316 4.4 Other services 316 5 Perspective 317 6 Further reading 318 7 Exercises 319 REFERENCES 322 GLOSSARY 328 INDEX 352 viii Contents Balance is a registered trademark of Sequent Computer Systems, Inc. CMS is a registered trademark of IBM. CP/M is a registered trademark of Digital Research. Cray-1 is a registered trademark of Cray Research. Cray-2 is a registered trademark of Cray Research. Cyber is a registered trademark of Control Data Corporation. DEC is a registered trademark of Digital Equipment Corporation. DECnet is a registered trademark of Digital Equipment Corporation. Dynix is a registered trademark of Sequent Computer Systems, Inc. Exec-8 is a registered trademark of Sperry Rand. IBM is a registered trademark of International Business Machines Corporation. Locus is a registered trademark of Locus Computing Corporation. MS-DOS is a registered trademark of Microsoft Corporation. MVS is a registered trademark of IBM. NonStop is a registered trademark of Tandem Computers. OS/360 is a registered trademark of IBM. PDP-10 is a registered trademark of Digital Equipment Corporation. PDP-11 is a registered trademark of Digital Equipment Corporation. RT-11 is a registered trademark of Digital Equipment Corporation. Tenex is a registered trademark of BBN. Tops-10 is a registered trademark of Digital Equipment Corporation. Tops-20 is a registered trademark of Digital Equipment Corporation. Univac is a registered trademark of Sperry Rand. Unix is a registered trademark of Bell Laboratories. VAX is a registered trademark of Digital Equipment Corporation. VM/370 is a registered trademark of IBM. VMS is a registered trademark of Digital Equipment Corporation. Contents ix PREFACE Traditionally, a vade mecum (pronounced ''VAHdee MAYkem'') is a laboratory manual that guides the student step by step through complex procedures. Operating systems are complex mixtures of policy and mechanism, of algorithm and heuristic, and of theoretical goals and practical experience. This vade mecum tries to unify these diverse points of view and guide the novice step by step through the complexities of the subject. As a text, this book is intended for a first course in operating systems at the undergraduate level. The subject has so many individual parts that its practitioners and teachers often concentrate on subareas and ignore the larger concepts that govern the entire subject. I have tried to rectify that situation in this book by structuring the presentation about the dual ideas of resource management and beautification. To unify disparate threads of discussion, I have taken the liberty introducing names for recurrent themes and glorifying them with the title ''principles.'' I hope that this organization and nomenclature will help the reader to understand the subject better and to integrate new ideas into the same framework. Each technical term that is introduced in the text is printed in boldface the first time it appears. All boldface entries are collected and defined in the glossary. I have striven to use a consistent nomenclature throughout the book. At times this nomenclature is at odds with accepted American practice. For example, I prefer to call computer memory ''store.'' This name allows me to unify the various levels of the storage hierarchy, including registers, main store, swap space, files on disk, and files on magnetic tape. I also prefer the single word ''transput'' to the clumsier but more common term ''input/output.'' Although I found this term jarring at first, I have grown to like it. Each chapter closes with a section on perspective, suggestions for further reading, and exercises. The perspective section steps back from the details of the subject and summarizes the choices that actual operating systems have made and rules of thumb for distinguishing alternatives. It also fits the subject of the chapter into the larger picture. The suggestions for further reading have two purposes. First, they show the reader where more information on the subject discussed in the chapter may be found. Second, they point to research articles related to the subject that describe actual implementations and xi areas of current activity. The exercises also serve two purposes. First, they allow the student to test his or her understanding of the subject presented in the text by working exercises directly related to the material. More importantly, they push the student beyond the confines of the material presented to consider new situations and to evaluate new policies. Subjects that are only hinted at in the text are developed more thoroughly in this latter type of exercise. A course in operating systems is not complete without computer projects. Unfortunately, such exercises require a substantial investment in software. The most successful projects for a first course in operating systems involve implementing parts of an operating system. A complete operating system can be presented to the class, with welldefined modules and interfaces, and the class can be assigned the task of replacing modules with ones of their own design. A less ambitious project has the students first build a simple scheduler for a simulated machine. After it is completed, it can be enhanced by adding virtual memory, transput, and other features. If the necessary software is not available for these assignments, students can be asked to simulate particular policies or algorithms in isolation from a complete operating system. Several exercises in the book give guidelines for this sort of project. This second edition of the text differs from the first in several ways. Many figures have been added, both to clarify individual points and to unify the treatment of different subjects with similar diagrams. For example, the history of operating system styles is now adorned with consistent pictures. The nuts and bolts of process switching has been moved from Chapter 2 to Chapter 1, and a new section on virtual-machine operating systems has been added. The discussion of page-replacement policies in Chapter 2 has been enhanced with fault-rate graphs drawn from a simulation. Analysis and simulation are described near the end of Chapter 2. Chapter 9 on cooperating processes has been enlarged with a major new section on the communication-kernel approach. The Hysteresis Principle has been introduced. Minor errors and inconsistencies have been fixed throughout the text. I owe a debt of gratitude to the many people who helped me write this text. The students of Bart Miller's operating system class all wrote book reviews for an early draft. My parents Asher and Miriam and my brothers Joel and Barry devoted countless hours to a careful reading of the entire text, suggesting clarifications and rewording throughout. My colleagues Bart Miller, Mary Vernon, and Michael Carey read and criticized individual chapters. Michael Scott's careful reading of Chapter 8 and his keen insight into language issues in general were of great help. I am also grateful to

View PDFchevron_right
Introduction to Operating Systems
Dominic Tomking

Operating System, 2019

View PDFchevron_right
The architecture of UNIX united
Lindsay Marshall

Proceedings of the IEEE, 2000

UNIX United is an architecture for a distributed system based on UNIX. As it is compatible with UNIX at the system call level, any program written for a normal UNIX system can be transparently extended to exploit the richer environment of UNIX United. As it relies on having a UNIX system beneath it, the implementation of UNIX United, called the Newcastle Connection, provides an interesting example of the construction of a very powerful distributed system with only a modicum of effort. A description of the basic semantics of UNIX United is followed by that of the architecture implied by the protocol between components in a UNIX United system, and of a software structure appropriate to the architecture and the protocol.

View PDFchevron_right
Operating systems Q&A
Ayesha Naureen

This document contains Principles of Operating Systems Few questions and answers for professional grad students.

View PDFchevron_right
Operating Systems A Concept-Based Approach
Eidy Estupiñan Varona

Fundamental concepts are introduced in simple terms. • The associations between techniques and concepts are readily established. • Numerous examples are included to illustrate concepts and techniques. • Implementation details and case studies are organized as small capsules spread throughout the text. xvi Preface xvii • Optional sections are devoted to advanced topics such as deadlock characterization, kernel memory allocation, synchronization and scheduling in multiprocessor systems, file sharing semantics, and file system reliability. The key benefit of this approach is that concepts, techniques, and case studies are well integrated, so many design and implementation details look "obvious" by the time the reader encounters them. It emphasizes the most important message an operating systems text can give to students: A concept-based study of operating systems equips a computer professional to comprehend diverse operating system techniques readily. • Preview of the Book The last section of the first chapter is a brief preview of the book that motivates study of each chapter by describing its importance within the overall scheme of the operating system, the topics covered in the chapter, and its relationships with other chapters of the book. xviii Preface and Windows, respectively, except when features of a specific version such as Linux 2.6 or Windows Vista are being discussed. Tests of Concepts A set of objective and multiple-choice questions is provided at the end of each chapter so that the reader can test his grasp of concepts presented in the chapter. Exercises Exercises are included at the end of each chapter. These include numerical problems based on material covered in the text, as well as challenging conceptual questions that test understanding and also provide deeper insights.

View PDFchevron_right

References (169)

  1. Bach MJ (2006) The design of the UNIX operating system. China Machine Press, Beijing
  2. Cooke D, Urvan J, Hailton S (1999) UNIX and beyond: An interview with Ken Thompson. Computer 32(5): 58 -64
  3. German DM, Penta MD, Davies J (2010) Understanding and auditing the licensing of open source software distributions. IEEE 18th International Conference on Program Comprehension, Braga, Minho Portugal, June 2010: pp 84 -93
  4. Jespersen H (1995) POSIX retrospective. ACM, StandardView 3(1): 2 -10
  5. Katzan H Jr (1970) Operating system architecture. AFIPS: Spring Joint Computer Conference, Atlantic City, New Jersey, 5 -7 May 1970: pp109 -118
  6. Kim T, Shin G, Hong E (1999) Experience with porting a UNIX version case tool to the corresponding Java version. APSEC'99: IEEE sixth Asia-Pacific software engineering conference, Takamatsu, December 1999: pp 622 -629
  7. Lawrence DC (1998) Internetnews server: Inside an open-source project. IEEE Internet Comput 2(5): 49 -52
  8. Mann D (1992) UNIX and the Am29000 microprocessor. IEEE Micro 12(1): 23 -31
  9. Martin VC (1995) There can be only one! A summary of the UNIX standardization movement. ACM, Crossroads 1(3): 9 -11
  10. McKusick MK (1999) Twenty years of Berkeley Unix: from AT&T-owned to freely redistributable. LINUXjunkies.org. http://www.linuxjunkies.org/articles/ kirkmck.pdf. Accessed 20 Aug 2010
  11. McKusick MK, Neville-Neil GV (2005) The design and implementation of FreeBSD operating system. Addison-Wesley, Boston References Bach MJ (2006) The design of the UNIX operating system. China Machine Press, Beijing
  12. Badger L, Sterne DF, Sherman DL et al (1995) Practical domain and type enforce- ment for UNIX. SP'95: The 1995 IEEE Symposium on Security and Privacy, Oakland, CA, 8 -10 May 1995, pp 66 -77
  13. Berkman J (1995) A user-friendly menu interface for UNIX. The 23rd Annual ACM SIGUCCS Conference on User Services: Winning the Networking Game, St. Louis, Missouri, US. ACM, 1995, pp 51 -54
  14. Braams J (1995) Batch class process scheduler for UNIX SVR4. SIGMETER- ICS'95/PERFORMANCE'95: The 1995 ACM SIGMETERICS Joint Interna- tional Conference on Measurement and Modeling of Computer Systems, Ottawa, Ontario, Canada. ACM, pp 301 -302
  15. Carson SD, Setia S (1992) Analysis of the periodic update write policy for disk cache. IEEE Software Eng 18(1): 44 -54
  16. Heindel LE, Kasten VA (1995) Real-time UNIX application filestores. RTAS'95: First IEEE Real-time Technology and Applications Symposium, Chicago, Illi- nois, 15 -17 May 1995, pp 44 -45
  17. Isaak J (1990) The history of POSIX: a study of the standards process. Computer 23(7): 89 -92
  18. Isaak J, Lohnson L (1998) POSIX/UNIX standards: Foundation for 21st century growth. IEEE Micro 18(4): 88, 87
  19. Jespersen H (1995) POSIX retrospective. ACM, StandardView 3(1): 2 -10
  20. McKusick MK (1999) Twenty years of Berkeley Unix: From AT&T-owned to freely redistributable. LINUXjunkies.org. http://www.linuxjunkies.org/articles/ kirkmck.pdf. Accessed 20 Aug 2010
  21. McKusick MK, Neville-Neil GV (2005) The design and implementation of FreeBSD operating system. Addison-Wesley, Boston
  22. Mohay G, Zellers J (1997) Kernel and shell based applications integrity assurance. ACSAC'97: The IEEE 13th Annual Computer Security Applications Confer- ence, San Diego, CA, 8 -12, December 1997, pp 34 -43
  23. Nelson BL, Keezer WS, Schuppe TF (1996) A hybrid simulation-queuing module for modeling UNIX I/O in performance analysis. WSC'96: The 1996 IEEE Winter Simulation Conference, 8 -11 December 1996, pp 1238 -1246
  24. Nguyen HQ, Bac C, Bernard G (1997) Integrating QoS management in a micro- kernel based UNIX operating system. The 23rd IEEE EUROMICRO Conference '97 new Frontiers of Information Technology, Budapest, Hungary, 1 -4 Septem- ber 1997, pp 371 -378
  25. Quarterman JS, Silberschatz A, Peterson JL (1985) Operating systems concepts, 2nd edn. Addison-Wesley, Reading, Massachusetts
  26. Rashid R, Tevanian A, Michael JR et al (1988) Machine-independent virtual mem- ory management for paged uniprocessor and multiprocessor architectures. IEEE Comput 37(8): 896 -908
  27. Ritchie DM, Thompson K (1974) The Unix time-sharing system. Commun ACM 17 (7): 365 -375
  28. References Bach MJ (2006) The design of the UNIX operating system. China Machine Press, Beijing
  29. Baecker R (1986) Design principles for the enhanced presentation of computer pro- gram source text. CHI'86: Conference on Human Factors in Computer Systems, Boston, Massachusetts, US, 13 -17 April 1986, ACM: 51 -58
  30. Douglas SA, Moran TP (1983) Learning text editor semantics by analogy. CHI'83: Conference on Human Factors in Computer Systems, Boston, Massachusetts, December 1983, ACM: 207 -211
  31. Makatani LH, Egan DE, Ruedisueli LW et al (1986) TNT: a talking tutor 'N' trainer for teaching the use of interactive computer systems. CHI'86: Conference on Human Factors in Computer Systems, Boston, Massachusetts, 13 -17 April 1986, ACM: 29 -34
  32. McKusick MK (1999) Twenty years of Berkeley Unix: from AT&T-owned to freely redistributable. LINUXjunkies.org. http://www.linuxjunkies.org/articles/ kirkmck.pdf. Accessed 20 Aug 2010
  33. Pelaprat E, Shapiro RB (2002) User activity histories. CHI'02: Conference on Hu- man Factors in Computer Systems, Minneapolis, Minnesota, April 2002, ACM: 876 -877
  34. Quarterman JS, Silberschatz A, Peterson JL (1985) Operating systems concepts, 2nd edn. Addison-Wesley, Reading, Massachusetts
  35. Ritchie DM, Thompson K (1974) The Unix time-sharing system. Commun ACM 17(7): 365 -375
  36. Rosson MB (1985) Effects of experience on learning, using, and evaluating a text editor. Human Factors 26: 463 -475
  37. Sarwar SM, Koretesky R, Sarwar SA (2006) UNIX: the textbook, 2nd edn. China Machine Press, Beijing
  38. Stallings W (1998) Operating systems: internals and design principles 3rd edn. Prentice Hall, Upper Saddle River, New Jersey
  39. Walker N, Olson JR (1988) Designing keybindings to be easy to learn and resistant to forgetting even when the set of commands is large. CHI'88: Conference on Human Factors in Computer Systems, Washington, D.C., US, May 1988, ACM: 201 -206
  40. Ward W (2003) Getting started with vi. Linux Journal 2003 (114): 5
  41. Wilder D (1997) At last, an X-based vi. Linux Journal 1997(34): Article No. 6 References
  42. Anderson TE, Bershad BN, Lazowska ED et al (1992) Scheduler activations: Ef- fective kernel support for the user-level management of parallelism. ACM T Comput Syst 10(1): 53 -79
  43. Andrews GR (1983) Concepts and notations for concurrent programming. ACM Comput Surv 15(1): 3 -43
  44. Bach MJ (2006) The design of the UNIX operating system. China Machine Press, Beijing
  45. Braams J (1995) Batch class process scheduler for UNIX SVR4. SIGMETER- ICS'95/PERFORMANCE'95: The 1995 ACM SIGMETERICS joint interna- tional conference on measurement and modeling of computer systems, Ottawa, Ontario. ACM, pp 301 -302
  46. Cmelik RF, Gehani NH, Roome WD (1989) Experience with multiple processor versions of concurrent C. IEEE T Software Eng 15(3): 335 -344
  47. DeBenedictis EP, Johnson SC (1993) Extending UNIX for scalable computing. Computer 26(11): 43 -53
  48. Denning PJ (1983) The working set model for program behavior. Commun ACM 26(1): 43 -48
  49. Devarakonda MV, Iyer PK (1989) Predictability of process resource usage: A measurement-based study on UNIX. IEEE T Software Eng 15(12): 1579 -1586
  50. Dijkstra EW (1968) Cooperating sequential processes, in programming languages. ACM, New York
  51. Dijkstra EW (1968) The structure of the "THE"-multiprogramming system. Com- mun ACM 11(5): 341 -346
  52. Forrest S, Hofmeyr SA, Somayaji A et al (1996) A sense of self for UNIX processes. SP'96: The 1996 IEEE Symposium on Security and Privacy, Oakland, CA, 6 -8 May 1996, pp 120 -128
  53. Kosaraju SR (1973) Limitations of Dijkstra's semaphore primitives and Petri nets. SOSP'73: The Fourth ACM Symposium on Operating System Principles, ACM, pp 122 -126
  54. Lauesen S (1975) A large semaphore based operating system. Commun ACM 18(7): 377 -389
  55. Leffler SJ, Fabry RS, Joy WN (1983) A 4.2BSD interprocess communication primer. UNIX Programmer's Manual, 4.2 Berkeley Software Distribution. Computer Systems Research Group, Depat. of Electrical Engineering and Computer Sci- ence, Univ. of California, Berkeley, Aug 1983
  56. McKusick MK (1999) Twenty years of Berkeley UNIX: From AT&T-owned to freely redistributable. LINUXjunkies.org. http://www.linuxjunkies.org/articles/ kirkmck.pdf. Accessed 20 Aug 2010
  57. McKusick MK, Neville-Neil GV (2005) The design and implementation of FreeBSD operating system. Addison-Wesley, Boston
  58. Mohay G, Zellers J (1997) Kernel and shell based applications integrity assurance. ACSAC'97: The IEEE 13th Annual Computer Security Applications Confer- ence, 1997, pp 34 -43
  59. Peachey DR, Bunt RB, Williamson CL et al (1984) An experimental investigation of scheduling strategies for UNIX. SIGMETRICS: 1984 ACM SIGMETRICS Conference on Measurement and Modeling of Computer Systems, pp 158 -166
  60. Quarterman JS, Silberschatz A, Peterson JL (1985) Operating systems concepts, 2nd edn. Addison-Wesley, Reading, Massachusetts
  61. Ritchie DM, Thompson K (1974) The Unix time-sharing system. Commun ACM 17 (7): 365 -375
  62. Sarwar SM, Koretesky R, Sarwar SA (2006) UNIX: the textbook, 2nd edn. China Machine Press, Beijing
  63. Sielski KL (1992) Implementing Ada tasking in a multiprocessing, multithreaded UNIX environment. The Conference on TRI-Ada'92, Orlando, Florida. ACM, 512 -517
  64. Stallings W (1998) Operating systems: internals and design principles, 3rd edn. Prentice Hall, Upper Saddle River, New Jersey
  65. Thompson K (1978) UNIX implementation. Bell Syst Tech J 57(6) Part 2: 1931 - 1946
  66. Zhou Y (2009) UNIX process, merging unified process and extreme programming to benefit software development practice. 2009 IEEE First International Workshop on Education Technology and Computer Science, Wuhan, Hubei, China, 7 -8 March 2009, pp 699 -702, doi 10.1109/ETCS.2009.690
  67. References Bach MJ (2006) The design of the UNIX operating system. China Machine Press, Beijing
  68. Bartels G, Karlin A, Anderson D et al (1999) Potentials and limitations of fault- based Markov prefetching for virtual memory pages. SIGMETRICS'99: The 1999 ACM SIGMETRICS International Conference on Measurement and Mod- eling of Computer Systems, Atlanta, Georgia, June 1999: 206 -207
  69. Bays C (1977) A comparison of next-fit, first-fit, and best-fit. Commun ACM 20(3): 191 -192
  70. Belay LA, Nelson RA, Shedler GS (1969) An anomaly in space-time characteristics of certain programs running in a paging machine. Commun ACM 12(6): 349 - 353
  71. Braams J (1995) Batch class process scheduler for UNIX SVR4. SIGMETER- ICS'95/PERFORMANCE'95: The 1995 ACM SIGMETERICS Joint Interna- tional Conference on Measurement and Modeling of Computer Systems, Ottawa, 1995, Canada. ACM, pp 301 -302
  72. Brawn BS, Gustavson FG, Mankin ES (1970) Sorting in a paging environment. Commun ACM 13(8): 483 -494
  73. Christensen C, Hause AD (1970) A multiprogramming, virtual memory system for a small computer. AFIPS'70 (spring): Spring Joint Computer Conference, Atlantic City, New Jersey, 5 -7 May 1970: pp 683 -690
  74. Cmelik RF, Gehani NH, Roome WD (1989) Experience with multiple processor versions of concurrent C. IEEE T Software Eng 15(3): 335 -344
  75. Denning PJ (1968) Thrashing: its causes and prevention. AFIPS'68 (Fall, part I): Fall Joint Computer Conference, part I, San Francisco, California, 9 -11 December 1968: pp 915 -922
  76. Denning PJ (1970) Virtual memory. ACM Compt Surv 2(3): 153 -189
  77. Denning PJ (1983) The working set model for program behavior. Commun ACM 26(1): 43 -48
  78. Iftode L, Blumrich M, Dubnicki C et al (1999) Shared virtual memory with au- tomatic update support. ICS'99: The 13th International Conference on Super- computing, Rhodes, Greece, May 1999, ACM: 175 -183
  79. McKusick MK, Neville-Neil GV (2005) The design and implementation of FreeBSD operating system. Addison-Wesley, Boston
  80. Midorikawa ET, Piantola RL, Cassettari HH (2008) On adaptive replacement based on LRU with working area restriction algorithm. ACM SIGOPS Operating Sys- tems Review 42(6): 81 -92
  81. Park Y, Scott R (1996) Virtual memory versus file interfaces for large, memory- intensive scientific applications. Supercomputing'96: The 1996 ACM/IEEE Con- ference on Supercomputing (CDROM), Pittsburgh, Pennsylvania, November 1996, IEEE computer society: Article No.: 53
  82. Peachey DR, Bunt RB, Williamson CL et al (1984) An experimental investiga- tion of scheduling strategies for UNIX. SIGMETRICS'84: ACM SIGMETRICS Conference on Measurement and Modeling of Computer Systems, August 1984, 12(3): pp 158 -166
  83. Quarterman JS, Silberschatz A, Peterson JL (1985) Operating systems concepts, 2nd edn. Addison-Wesley, Reading, Massachusetts
  84. Rashid R, Tevanian A, Michael JR et al (1988) Machine-independent virtual mem- ory management for paged uniprocessor and multiprocessor architectures. IEEE T Comput 37(8): 896 -908
  85. Ritchie DM, Thompson K (1974) The Unix time-sharing system. Commun ACM 17 (7): 365 -375
  86. Stallings W (1998) Operating systems: internals and design principles, 3rd edn. Prentice Hall, Upper Saddle River, New Jersey.
  87. Weizer N, Oppenheimer G (1969) Virtual memory management in a paging en- vironment. Spring Joint Computer Conference, ACM, Boston, Massachusetts, 14 -16 May 1969: pp 249 -256
  88. Ashley P, Vandenwauver M (1999) Using SESAME to implement role based access control in UNIX file systems. IEEE 8th International Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises, Palo Alto, Califor- nia, 16 -18 June 1999, pp 141 -146
  89. Bach MJ (2006) The design of the UNIX operating system. China Machine Press, Beijing
  90. Cai X, Gui Y, Johnson R (2009) Exploiting UNIX file-system races via algorith- mic complexity attacks. 2009 30th IEEE Symposium on Security and Privacy, Oakland, California, US, 17 -20 May 2009, pp 27 -41
  91. Floyd RA, Ellis CS (1989) Directory reference patterns in hierarchical file systems. IEEE T Knowl and Data En, 1(2): 238 -247
  92. Heindel LE, Kasten VA (1995) RTAS'95: Real-time UNIX application filestores. First IEEE real-time technology and applications symposium, Chicago, Illinois, 15 -17 May 1995, pp 44 -45
  93. Isaak J, Lohnson L (1998) POSIX/UNIX standards: foundation for 21st century growth. IEEE Micro 18(4): 88, 87
  94. Jonge W, Kaashoek MF, Hsieh WC (1993) The logical disk: a new approach to im- proving file systems. SOSP'93: The fourteenth ACM Symposium on Operating Systems Principles, Asheville, North Carolina, December 1993, pp 15 -28
  95. McKusick MK (1999) Twenty years of Berkeley Unix: from AT&T-owned to freely redistributable. LINUXjunkies.org. http://www.linuxjunkies.org/articles/ kirkmck.pdf. Accessed 20 Aug 2010
  96. McKusick MK, Neville-Neil GV (2005) The design and implementation of FreeBSD operating system. Addison-Wesley, Boston
  97. Mohay G, Zellers J (1997) Kernel and shell based applications integrity assurance. ACSAC'97: The IEEE 13th Annual Computer Security Applications Confer- ence, San Diego, 8 -12, December 1997, pp 34 -43
  98. Ousterhout JK, Costa HD, Harrison D et al (1985) A trace-driven analysis of the UNIX 4.2 BSD file system. SOSP'85: The Tenth ACM Symposium on Operating Systems Principles, Orcas Island, Washington, December 1985, pp 15 -24
  99. Quarterman JS, Silberschatz A, Peterson JL (1985) Operating systems concepts, 2nd edn. Addison-Wesley, Reading, Massachusetts
  100. Ritchie DM, Thompson K (1974) The UNIX time-sharing system. Commun ACM 17(7): 365 -375
  101. Sarwar SM, Koretesky R, Sarwar SA (2006) UNIX: The textbook, 2nd edn. China Machine Press, Beijing
  102. Stallings W (1998) Operating systems: internals and design principles 3rd edn. Prentice Hall, upper saddle River, New Jersey
  103. Thompson K (1978) UNIX implementation. Bell Sys Tech J 57(6) Part 2: 1931 - 1946 References
  104. Bach MJ (2006) The design of the UNIX operating system. China Machine Press, Beijing
  105. Carson SD, Setia S (1992) Analysis of the periodic update write policy for disk cache. IEEE T Software Eng 18(1): 44 -54
  106. Heindel LE, Kasten VA (1995) Real-time UNIX application filestores. RTAS'95: First IEEE Real-time Technology and Applications Symposium, Chicago, Illi- nois, 15 -17 May 1995, pp 44 -45
  107. Isaak J, Lohnson L (1998) POSIX/UNIX standards: Foundation for 21st century growth. IEEE Micro 18(4): 88, 87
  108. Jespersen H (1995) POSIX retrospective. ACM, StandardView 3 (1): 2 -10
  109. McKusick MK, Neville-Neil GV (2005) The design and implementation of FreeBSD operating system. Addison-Wesley, Boston
  110. Nelson BL, Keezer WS, Schuppe TF (1996) A hybrid simulation-queuing module for modeling UNIX I/O in performance analysis. WSC'96: The 1996 IEEE Winter Simulation Conference, 8 -11 December 1996, pp 1238 -1246
  111. Quarterman JS, Silberschatz A, Peterson JL (1985) Operating systems concepts, 2nd edn. Addison-Wesley, Reading
  112. Ritchie DM, Thompson K (1974) The Unix time-sharing system. Commun ACM 17 (7): 365 -375
  113. Ritchie DM (1984) A stream input output system. AT&T Bell Lab Tech J, 63(8) Part 2: 1897 -1910
  114. Sarwar SM, Koretesky R, Sarwar SA (2006) UNIX: the textbook, 2nd edn. China Machine Press, Beijing
  115. Stallings W (1998) Operating systems: internals and design principles, 3rd edn. Prentice Hall, Upper Saddle River, New Jersey References Bach MJ (2006) The design of the UNIX operating system. China Machine Press, Beijing
  116. Bourne SR (1978) The UNIX shell. T Bell Syst Tech J, 57(6) Part 2: pp 1971 -1990
  117. Bourne SR (1983) The UNIX system. Addison-Wesley, Reading, Massachusetts Joy WN (1980) An introduction to the C shell. UNIX Programmer's Manual, 4.2 Berkeley Software Distribution. Computer systems research group, Depat. of Electrical Engineering and Computer Science, Univ. of California, Berkeley, Aug 1980
  118. Korn D (1983) KSH -a shell programming language. USENIX Conference Proceed- ings, Toronto, Ontario, June 1983, pp 191 -202
  119. Miller RC, Myers BA (2000) Integrating a command shell into a web browser. 2000 USENIX Annual Technical Conference, San Diego, California, 18 -23 June 2000. http://www.usenix.org/events/usenix2000/general/generaltechnical. html. Ac- cessed 24 Sep 2009
  120. Mohay G, Zellers J (1997) Kernel and shell based applications integrity assurance. ACSAC'97: The IEEE 13th Annual Computer Security Applications Confer- ence, 1997, pp 34 -43
  121. Quarterman JS, Silberschatz A, Peterson JL (1985) Operating systems concepts, 2nd edn. Addison-Wesley, Reading, Massachusetts
  122. Ritchie DM, Thompson K (1974) The Unix time-sharing system. Commun ACM 17 (7): 365 -375
  123. Rosenblatt B, Robbins A (2002) Learning the Korn shell, 2nd edn. O'Reilly & Associates, Sebastopol
  124. Sarwar SM, Koretesky R, Sarwar SA (2006) UNIX: the textbook, 2nd edn. China Machine Press, Beijing References Bach MJ (2006) The design of the UNIX operating system. China Machine Press, Beijing
  125. Bourne SR (1978) The UNIX shell. Bell Syst Techn J, 57(6) Part 2: pp 1971 -1990
  126. Bourne SR (1983) The UNIX system. Addison-Wesley, Reading, Massachusetts Joy WN (1980) An introduction to the C shell. UNIX Programmer's Manual, 4.2 Berkeley Software Distribution. Computer Systems Research Group, Depat. of Electrical Engineering and Computer Science, Univ. of California, Berkeley, Aug 1980
  127. Korn D (1983) KSH -a shell programming language. USENIX Conference Proceed- ings, Toronto, Ontario, June 1983, pp 191 -202
  128. Miller RC, Myers BA (2000) Integrating a command shell into a web browser. 2000 USENIX Annual Technical Conference, San Diego, California, USA, 18 -23 June 2000. http://www.usenix.org/events/usenix2000/general/generaltechnical. html. Accessed 24 Sep 2009
  129. Mohay G, Zellers J (1997) Kernel and shell based applications integrity assurance. ACSAC'97: The IEEE 13th Annual Computer Security Applications Confer- ence, 1997, pp 34 -43
  130. Quarterman JS, Silberschatz A, Peterson JL (1985) Operating systems concepts, 2nd edn. Addison-Wesley, Reading, Massachusetts
  131. Ritchie DM, Thompson K (1974) The Unix time-sharing system. Commun ACM 17 (7): 365 -375
  132. Rosenblatt B, Robbins A (2002) Learning the Korn shell, 2nd edn. O'Reilly & Associates, Sebastopol
  133. Sarwar SM, Koretesky R, Sarwar SA (2006) UNIX: the textbook, 2nd edn. China Machine Press, Beijing
  134. Stallings W (1998) Operating systems: internals and design principles, 3rd edn. Prentice Hall, Upper Saddle River, New Jersey References
  135. Bourne SR (1978) The UNIX shell. Bell Syst Tech J 57(6) Part 2, pp 1971 -1990
  136. Bourne SR (1983) The UNIX system. Addison-Wesley, Reading, Massachusetts Joy WN (1980) An introduction to the C shell. UNIX Programmer's Manual, 4.2 Berkeley Software Distribution. Computer Systems Research Group, Depat. of Electrical Engineering and Computer Science, Univ. of California, Berkeley, Aug, 1980
  137. Korn D (1983) KSH -a shell programming language. USENIX Conference Proceed- ings, Toronto, Ontario, June 1983, pp 191 -202
  138. Rosenblatt B, Robbins A (2002) Learning the Korn shell, 2nd edn. O'Reilly & Associates, Sebastopol.
  139. Sarwar SM, Koretesky R, Sarwar SA (2006) UNIX: the textbook, 2nd edn. China Machine Press, Beijig References
  140. Borenstein N, Freed N (1993) MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for specifying and describing the format of Internet message bodies. RFC 1521.http://tools.ietf.org/html/rfc1521. Accessed 10 Oct 2010
  141. Cain B, Deering S, Kouvelas I et al (2002) Internet Group Management Protocol, Version 3. RFC 3376. http://tools.ietf.org/html/rfc3376. Accessed 10 Oct 2010
  142. Cerf V, Dalal Y (1974) Specification of Internet Transmission Control Program. RFC 675. http://tools.ietf.org/html/rfc675. Accessed 10 Oct 2010
  143. Comer DE (1998) Computer networks and Internets. Prentice Hall, Upper Saddle River, New Jersey
  144. Comer DE, Stevens DL (1998) Internetworking with TCP/IP vol III: Client-server programming and applications, windows sockets version. Prentice Hall, Upper Saddle River, New Jersey
  145. Conta A, Deering S, Gupta M (ed) (2006) Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification. RFC 4443. http://tools.ietf.org/html/rfc4443. Accessed 10 Oct 2010
  146. Crispin M (1988) Interactive mail access protocol, 2nd edn. RFC 1064. http://tools.ietf.org/html/rfc1064. Accessed 13 Oct 2010
  147. Crocker DH (1982) Standard for the format of ARPA Internet text messages. RFC 822. http://tools.ietf.org/html/rfc822. Accessed 13 Oct 2010
  148. Deering S (1989) Host Extensions for IP Multicasting. RFC 1112. http://tools. ietf.org/html/rfc1112. Accessed 10 Oct 2010
  149. Deering S, Hinden R (1998) Internet Protocol, Version 6 (IPv6) Specification. RFC 2460. http://tools.ietf.org/html/rfc2460. Accessed 10 Oct 2010
  150. Fenner W (1997) Internet Group Management Protocol, 2nd edn. RFC 2236. http://tools.ietf.org/html/rfc2236. Accessed 10 Oct 2010
  151. Finlayson R, Mann T, Mogul JC at el (1984) A Reverse Address Resolution Pro- tocol. RFC 903. http://tools.ietf.org/html/rfc903. Accessed 10 Oct 2010
  152. Holmgren S (1975) Network UNIX. RFC 681. http://tools.ietf.org/html/ rfc681. Accessed 10 Oct 2010
  153. Kantor B (1991) BSD rlogin. RFC 1282. http://tools.ietf.org/html/rfc1282. Ac- cessed 13 Oct 2010
  154. Kohler E, Handley M, Floyd S (2006) Datagram congestion control protocol (DCCP). RFC 4340. http://tools.ietf.org/html/rfc4340. Accessed 10 Oct 2010
  155. Ong L, Yoakum J (2002) An introduction to the stream control transmission pro- tocol (SCTP). RFC 3286. http://tools.ietf.org/html/rfc3286. Accessed 10 Oct 2010
  156. Plummer DC (1982) An Ethernet Address Resolution Protocol, or converting net- work protocol address to 48 bit Ethernet address for transmission on Ethernet hardware. RFC 826. http://tools.ietf.org/html/rfc826. Accessed 10 Oct 2010
  157. Postel JB (1980) User datagram protocol. RFC 768. http://tools.ietf.org/html /rfc768. Accessed 10 Oct 2010
  158. Postel JB (ed) (1981) Internet Protocol. RFC 791. http://tools.ietf.org/html /rfc791. Accessed 10 Oct 2010
  159. Postel JB (1981) Internet Control Message Protocol. RFC 792. http://tools. ietf.org/html/rfc792. Accessed 10 Oct 2010
  160. Postel JB (1981) Transmission Control Protocol. RFC 793. http://tools.ietf. org/html/rfc793. Accessed 10 Oct 2010
  161. Postel JB (1982) Simple Mail Transfer Protocol. RFC 821. http://tools.ietf. org/html/rfc821. Accessed 13 Oct 2010
  162. Postel JB, Peynolds JK (1983) Telnet Protocol specification. RFC 854. http: //tools.ietf.org/html/rfc854. Accessed 13 Oct 2010
  163. Postel JB, Reynolds JK (1985) File Transfer Protocol (FTP). RFC 959. http://tools. ietf.org/html/rfc959. Accessed 13 Oct 2010
  164. Reynolds JK (1984) Post Office Protocol. RFC 918. http://tools.ietf.org/html /rfc918. Accessed 13 Oct 2010
  165. Stevens WR (2002) TCP/IP illustrated, volume 1: The protocols. China Machine Press, Beijing
  166. Stevens WR (2002) TCP/IP illustrated, volume 3: TCP for transactions, HTTP, NNTP and UNIX domain protocols. China Machine Press, Beijing
  167. Stewart R (ed) (2007) Stream control transmission protocol. RFC 4960. http: //tools.ietf.org/html/rfc4960. Accessed 10 Oct 2010
  168. Wright GR, Stevens WR (2002) TCP/IP illustrated, volume 2: The implementa- tion. China Machine Press, Beijing
  169. Zimmerman D (1991) The finger user information protocol. RFC 1288. http: //tools.ietf.org/html/rfc1288. Accessed 13 Oct 2010

Related papers

UNIX Operating System: The Development Tutorial via UNIX Kernel Services
Yong Yue

2011

This book presents UNIX as a practical case of operating systems for the reader to understand and master deeply and tangibly the theory and algorithms in operating systems. It gives discussions and studies on the hierarchical structure, principles, applications, shells, development, and management of the UNIX operation system multi-dimensionally, systematically and from the elementary to the profound. It brings readers to go into the inside of the UNIX operating system and lets them understand clearly what and how UNIX operating system functions. This book consists of 11 chapters. The first two chapters discuss the background of UNIX operating system (OS), and give a whole picture of what UNIX OS looks like and the evolution of UNIX. Chapter 3 focuses on the editors that will be used frequently by UNIX users, no matter who are regular users or seasoned programmers. Chapters 4, 5, 6, and 7 concentrate on the services of the UNIX kernel. Chapter 4 zooms in the process management, which is usually hidden from the final users. Chapter 5 is to discuss the UNIX memory management, which cooperates with the process management to accomplish the processes' concurrently running. Chapter 6 introduces the UNIX file management, which is involved almost in every service that the UNIX kernel provides to the users. Chapter 6, however, for UNIX users, is fundamentally useful to understand how UNIX works. Chapter 7 explores UNIX I/O, I/O redirection and piping. As UNIX treats its hardware devices as special files, this mechanism brings a whole different concept on UNIX input and output devices. I/O redirection and piping are two useful tools that can be used to deduce different commands to control the terminals through UNIX system calls. UNIX has almost as many shells as versions of the UNIX operating system. Chapter 8 introduces some types of shells, shell evolution, and some common concepts in UNIX shells. As there are so many kinds of shells, it vi Preface

View PDFchevron_right
The unix programming environment
Mujahid Gamta

This is a revised version of the UNIX compendium which is available in printed form and online via the WWW and info hypertext readers. It forms the basis for a one or two semester course in UNIX. The most up-to-date version of this manual can be found at

View PDFchevron_right
Unix as an application program
Alessandro Forin

Proceedings of the Summer …, 1990

1. Abstract Since March of 1989 we have had running at CMU a computing environment in which the functions of a traditional Unix system are cleanly divided into two parts: facilities which manage the hardware resources of a computer system (such as CPU, I/O and memory) and support for higher-level resource abstractions used in the building of application programs, e.g.

View PDFchevron_right
Operating Systems/Introduction to Operating System Lecture Notes Module 1: Introduction to Operating System
Priyanshu Sharma
View PDFchevron_right
PRINCIPLES OF Operating Systems
Yashnath Pandey

PRINCIPLES OF Operating Systems by Naresh Chauhan(OXFORD)

View PDFchevron_right

Related topics

  • Computer Science
    • 580 California St., Suite 400
    San Francisco, CA, 94104
    © 2025 Academia. All rights reserved