Modern Operating Systems, 2nd Edition (+Solutions)
(Pearson Education) A reference offering practical and example-based information on constructing and understanding modern operating systems. Includes chapters on computer security, multimedia operating systems, multiple processor systems, single processor computer systems, and a score of other topics. Also features a companion Web site. DLC: Operating systems.
For software development professionals and computer science students, Modern Operating Systems gives a solid conceptual overview of operating system design, including detailed case studies of Unix/Linux and Windows 2000.
What makes an operating system modern? According to author Andrew Tanenbaum, it is the awareness of high-demand computer applications–primarily in the areas of multimedia, parallel and distributed computing, and security. The development of faster and more advanced hardware has driven progress in software, including enhancements to the operating system. It is one thing to run an old operating system on current hardware, and another to effectively leverage current hardware to best serve modern software applications. If you don’t believe it, install Windows 3.0 on a modern PC and try surfing the Internet or burning a CD.
Readers familiar with Tanenbaum’s previous text, Operating Systems, know the author is a great proponent of simple design and hands-on experimentation. His earlier book came bundled with the source code for an operating system called Minux, a simple variant of Unix and the platform used by Linus Torvalds to develop Linux. Although this book does not come with any source code, he illustrates many of his points with code fragments (C, usually with Unix system calls).
The first half of Modern Operating Systems focuses on traditional operating systems concepts: processes, deadlocks, memory management, I/O, and file systems. There is nothing groundbreaking in these early chapters, but all topics are well covered, each including sections on current research and a set of student problems. It is enlightening to read Tanenbaum’s explanations of the design decisions made by past operating systems gurus, including his view that additional research on the problem of deadlocks is impractical except for «keeping otherwise unemployed graph theorists off the streets.»
It is the second half of the book that differentiates itself from older operating systems texts. Here, each chapter describes an element of what constitutes a modern operating system–awareness of multimedia applications, multiple processors, computer networks, and a high level of security. The chapter on multimedia functionality focuses on such features as handling massive files and providing video-on-demand. Included in the discussion on multiprocessor platforms are clustered computers and distributed computing. Finally, the importance of security is discussed–a lively enumeration of the scores of ways operating systems can be vulnerable to attack, from password security to computer viruses and Internet worms.
Included at the end of the book are case studies of two popular operating systems: Unix/Linux and Windows 2000. There is a bias toward the Unix/Linux approach, not surprising given the author’s experience and academic bent, but this bias does not detract from Tanenbaum’s analysis. Both operating systems are dissected, describing how each implements processes, file systems, memory management, and other operating system fundamentals.
Tanenbaum’s mantra is simple, accessible operating system design. Given that modern operating systems have extensive features, he is forced to reconcile physical size with simplicity. Toward this end, he makes frequent references to the Frederick Brooks classic The Mythical Man-Month for wisdom on managing large, complex software development projects. He finds both Windows 2000 and Unix/Linux guilty of being too complicated–with a particular skewering of Windows 2000 and its «mammoth Win32 API.» A primary culprit is the attempt to make operating systems more «user-friendly,» which Tanenbaum views as an excuse for bloated code. The solution is to have smart people, the smallest possible team, and well-defined interactions between various operating systems components. Future operating system design will benefit if the advice in this book is taken to heart. –Pete Ostenson