A Quarter Century of UNIX

Rating:
Summary: The birth of UNIX from an insider
Review: A lively and impeccably well informed history of the birth of UNIX. It's not perfect, but it's still the best source around.

Rating:
Summary: The coolest book on Unix History
Review: By far the coolest book on Unix!!

The little stories on Unix are amazing.

e.g. Bill Joy's start of BSD distribution or Steve Johnson's lex and yacc development. This book is full of zany characters that we just know names of. This book gives a picture of their personality. The best of the lot are of
Ken T, Dennis R, Robert Morris, Bill Joy, McKusick, and the rest of the looney unix toons. These guys are awesome. A must read for any Unix Lover.

Rating:
Summary: Overview of the Unix World
Review: In 1969 the Unix operating system was born. The main developers were Ken Thompson and Dennis Ritchie, two programmers at Bell Telephone Labs. Unix was born because of the cancellation of another operating system developed at BTL, Multics. Learning from the experience they gained from Multics, Thompson and Ritchie began working on Unix, which would later prove to be a good choice. At first they used the PDP-7 machine, assembler language, and the programming language B (by Dennis Ritchie). Only later did BTL upgrade to PDP-11. Because of the upgrade and because of the development of the C programming language, Unix could mature.

The book has six parts: Genesis, Birth of a System, What makes UNIX Unix?, Unix Spreads and Blossoms, The Unix Industry, and The Currents of Change. In the first part, Peter Salus introduces us to Thompson and Ritchie; there's also a chapter on computers in general. Part two, Birth of a System, tells the story about how Unix came to be with what today is seen as much outdated hardware. Later parts give information on the many companies and groups involved in the Unix history, most notably the development of the BSD systems.

Peter Salus has been involved in the Unix history himself, and therefore he writes about it with sympathetic understanding. That means that we don't get introduced properly to the persons. And it means that the pages are full of acronyms. The writing is very compact and full of quotes from interviews, magazines, books and other sources, and that makes the book difficult to read. The book also has some minor errors.

But if you can live with these flaws, "A Quarter Century of Unix" is a good read. It gives an overview of the Unix world, and shows that Linux is just a small part of the whole operating system landscape, and that there are alternatives.

Rating:
Summary: What you needed to know about Unix!
Review: One of the reason I like this book is, more than 50% of the text is interview with scores of UNIX developers and early enthusiasts. Unlike other books filled with authors' historical anaylsts and poetic comments, this book reads like an UNIX man page: give you the information you needed and not confuse you.END

Rating:
Summary: Directly told from people who made it happen
Review: One of the reason I like this book is, more than 50% of the text is interview with scores of UNIX developers and early enthusiasts. Unlike other books filled with authors' historical anaylsts and poetic comments, this book reads like an UNIX man page: give you the information you needed and not confuse you.END

Rating:
Summary: don't loose your money
Review: The really expensive little book lacks coherence and it is difficult to follow due to the full of citations and data piled up and left as row material page after page.

Rating:
Summary: You must own this book. Period.
Review: There are numerous reference books for Unix, the operating system of choice for the computer-aware. This book, though, brings Unix to life. The rich and storied history of Ken's and Dennis' baby is covered in detail along with pictures of the major players. (Apparently facial hair was a defacto standard. Maybe ZZ Top spent some time in Murray Hill, eh?) Even if you already know Unix, Salus does a wonderful job in helping you *appreciate* this elegant, robust, powerful and selectively-friendly operating system.

UNIX: Live free or die!

Rating:
Summary: What you needed to know about Unix!
Review: This book is an excellent overview of the history of Unix. It will help you to understand how Unix came to be, and how it came to be split up into so many different versions. A must for every Unix nerd.

Rating:
Summary: Excellent, but pricey
Review: This is a very good, very carefully researched, and a must-read for anyone who ever even wondered about the history of Unix.

However, I can't get over the price -- like US$30 for a pretty thin little book that's simply a for-fun read.

Rating:
Summary: Expensive short chronology; most material is availble online
Review: This is an expensive short book with mainly trivial chronological information, 90% of which are freely available on the Internet. As for the history of the first 25 year of Unix it is both incomplete and superficial. Salus is reasonably good as a facts collector (although for a person with his level of access to the Unix pioneers he looks extremely lazy and he essentially missed an opportunity to write a real history, setting for a glossy superficial chronology instead). He probably just felt the market need for such a book and decided to fill the niche.

In my humble opinion Salus lucks real understanding of the technical and social dynamics of Unix development, understanding that can be found, say, in chapter "Twenty Years of Berkeley Unix from AT&T-Owned to Freely Redistributable" in the book "Open Sources: Voices from the Open Source Revolution (O'Reilly, 1999)" (available online). The extended version of this chapter will be published in the second edition of "The Design and Implementation of the 4.4BSD Operating System (Unix and Open Systems Series)" which I highly recommend (I read a preprint at Usenix.)

In any case Kirk McKusick is a real insider, not a former Usenix bureaucrat like Salus. Salus was definitely close to the center of the events; but it is unclear to what extent he understood the events he was close to.

Unix history is a very interesting example how interests of military (DAPRA) shape modern technical projects (not always to the detriment of technical quality, quite opposite in case of Unix) and how DAPRA investment in Unix created completely unforeseen side effect: BSD Unix that later became the first free/open Unix ever (Net2 tape and then Free/Open/NetBSD distributions). Another interesting side of Unix history is that AT&T brass never understood what a jewel they have in hands.

Salus's Usenix position prevented him from touching many bitter conflicts that litter the first 25 years of Unix, including personal conflicts. The reader should be advised that the book represents "official" version of history, and that Salus is, in essence, a court historian, a person whose main task is to put gloss on the events, he is writing about. As far as I understand, Salus never strays from this very safe position.

Actually Unix created a new style of computing, a new way of thinking of how to attack a problem with a computer. This style was essentially the first successful component model in programming. As Frederick P. Brooks Jr (another computer pioneer who early recognized the importance of pipes) noted, the creators of Unix "...attacked the accidental difficulties that result from using individual programs together, by providing integrated libraries, unified file formats, and pipes and filters.". As a non-programmer, in no way Salus is in the position to touch this important side of Unix. The book contains standard and trivial praise for pipes, without understanding of full scope and limitations of this component programming model...

I can also attest that as a historian, Peter Salus can be extremely boring: this July I was unfortunate enough to sit on one of his talks, when he essentially stole from Kirk McKusick more then an hour (out of two scheduled for BSD history section at this year Usenix Technical Conference ) with some paternalistic trivia insulting the intelligence of the Usenix audience, instead of a short 10 min introduction he was expected to give; only after he eventually managed to finish, Kirk McKusick made a really interesting, but necessarily short (he had only 50 minutes left :-) presentation about history of BSD project, which was what this session was about.