Rating: 
Summary: Excellent fundamentals of operating systems text.
Review: I read this text in an Operating Systems class at the University of Phoenix. I liked the "bad" examples which were faulted by another reviewer, just as much as I liked the "good" examples. The "bad" examples show different approaches to solving the same problem, while showing the difficulty one might encounter while attempting to solve the problem that way.My conclusion: if you are interested in the "bottom line" or "right answer," this book contains a lot of extraneous information. If you are interested in the hows and whys of current practice, this book is probably for you.
Rating:
Summary: Clear and Comprehensive
Review: I used it as a reference book of my OS course last semester. I read it more than the desired book of the porfessor. The reason is that the context is clear and detailed. It's mainly about the OS concepts. It doesn't only tell you what an OS should looks like, but also tells you why it looks like that. I especially loves the chapters about concurrency. Classical problems such as critical section, semaphore(sleeping barber), monitors, message passinb, readers/writers problem, dining philosophers etc are all discussed with a great detail. The texts explain the concepts step by step, the pseudocode allows you understand how to implement them, no matter which programming languages you use. It helps me a lot with I do the programming assignments.
Rating:
Summary: Truely a masterpiece
Review: It is truly amazing what PLAIN ENGLISH does for you. Truely maginificent
Rating: 
Summary: Very wordy
Review: There are better books than this on operating systems. This book is very wordy...great for those nights when you cannot fall asleep.
Rating:
Summary: Don't buy this book unless you must!
Review: This book contains all you need to know about OS at a beginner level. It fails badly to deliver it in a simple and clear way. The examples are not detailed enough and hard to understand.
There are lots of examples from outdated operating systems.
The practical utility of this book is almost zero.
You need to consult other documentation to solve the problems. Overall: it manages to complicate simple things and make you feel like an idiot.
Rating: 
Summary: Best book on operating systems I've ever read
Review: This book explains all aspects of operating system design with examples from NT and Unix. You don't start coding you own OS after reading this, but you get a better understanding of the problems in OS design and you probably become a better programmer.
Rating:
Summary: The most horrible book on networks I have ever read.
Review: This book is completely and utterly useless. If you want a good book on networks get Tanenbaum. If you like O'Reilly titles - concise and to the point, this book is a complete OPPOSITE. Wordy, and most of the time pointless! Even if you have to get this book for a course, don't!
Rating:
Summary: A good book
Review: This book is for beginners, and it is easy to read. It illustrate concurrency well. However, it doen't do so well about the Filesystem. The context on the FS is too lack. But I still consider it as a readable book .
Rating:
Summary: Pass on this one!
Review: This book is wordy and confusing. The questions at the end of each chapter could only be answered if you have experience with operaing systems and computers. This is not a beginners book. It is probably a fine graduate level book or a an adv. operating systems book in undergraduate. BUT NOT A FIRST COURSE IN OPERATING SYSTEMS.
Rating:
Summary: Good overview on operating systems
Review: This book on operating systems compares a few operating systems, and Windows NT is taken as model. It does not go too much in depth technically, so it is easy to read and understand. The topic of memory management, virtual memory, and scheduling is also covered in this book; topics not easily found elsewhere all in one book.
| 
