A Quarter Century of Unix
Author: Peter H. Salus
Publisher: Addison-Wesley 1994
Reviewer: Danny Yee
Summary: From Space Travel to Plan 9 and Linux
A Quarter Century of Unix is a history of Unix, a kind of annotated collection of reminiscences. It begins at the “birth” of Unix, with Ken Thompson looking for a machine to play Space Travel on, then jumps back to provide the context, both in the history of computing in general and in the particular setup at Bell Labs. Part two describes the work done up to 1974, both on Unix and on the tools and language (C) so closely associated with it. Part three tries to pin down some of the things that made Unix unique: its style, the strong contributions by users and user groups, and the key role of some of its more famous tools. Parts four and five trace the expansion of Unix: the development of BSD and the commercial Unixes, the creation of SUN, the ambivalent relationship with DEC, legal issues and attempts at standardization. The final section offers an overview of the current status of Unix in its many different versions and offers some ideas about where it is heading. There is also a very brief glance at some of the systems that it has influenced, including Bell Lab's new Plan 9 system. The finale has Dennis Ritchie, Brian Kernighan and others offering their ideas on what made Unix work. Particularly noteworthy is the solid treatment of legal issues (three chapters altogether) and the coverage of events outside the United States (in Australia, Europe and Japan).
The format of A Quarter Century of Unix, with most of the text in the form of extended quotations, runs the risk of discontinuity and lack of focus. Salus has chosen and edited his source material well, however, and inserted his own summary and exposition in appropriate places. The result is a great read, with the voices of the various creators providing unique perspectives on the events they participated in (some scores of people are quoted from at length).
I did spot a few minor inconsistencies in the text—on page 155 we read “It was 32V that became 3BSD in 1979”, though the Unix versions tree on page 61 shows no such influence—and errors—on page 253 we have “It was clear that AT&T hadn't objected to other derivatives: Linux, MINIX, etc. In the autumn of 1988...”, implying that Linux existed in 1988 (and Linus' name is misspelled in the index, too). But these are just quibbles. A more weighty criticism would be that the book sometimes reads more like myth than history, with the participants portrayed like epic heroes. (It's rather obvious that Salus himself is a Unix fan.) This may worry the historians, but in a way it is the legends and myths that are the most influential, so the distinction is perhaps moot.
A Quarter Century of Unix doesn't assume specialized knowledge, but the more you know about Unix (and to a lesser extent, about architectures and operating systems) the more you will get out of it—if you've never used awk, for example, you will probably have little interest in reading about its origins and development. The main audience will be programmers, administrators, and users with extensive Unix experience. Historians and sociologists of the computer industry will find Salus' work an essential source of primary material, and marketing types might well learn a thing or to from it. A Quarter Century of Unix should be a great success; it's just unfortunate that it wasn't written years ago!
|Dynamic DNS—an Object Lesson in Problem Solving||May 21, 2013|
|Using Salt Stack and Vagrant for Drupal Development||May 20, 2013|
|Making Linux and Android Get Along (It's Not as Hard as It Sounds)||May 16, 2013|
|Drupal Is a Framework: Why Everyone Needs to Understand This||May 15, 2013|
|Home, My Backup Data Center||May 13, 2013|
|Non-Linux FOSS: Seashore||May 10, 2013|
- Dynamic DNS—an Object Lesson in Problem Solving
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Using Salt Stack and Vagrant for Drupal Development
- New Products
- Drupal Is a Framework: Why Everyone Needs to Understand This
- Validate an E-Mail Address with PHP, the Right Way
- A Topic for Discussion - Open Source Feature-Richness?
- Download the Free Red Hat White Paper "Using an Open Source Framework to Catch the Bad Guy"
- The Secret Password Is...
- New Products
3 hours 20 min ago
- Keeping track of IP address
5 hours 11 min ago
- Roll your own dynamic dns
10 hours 24 min ago
- Please correct the URL for Salt Stack's web site
13 hours 36 min ago
- Android is Linux -- why no better inter-operation
15 hours 51 min ago
- Connecting Android device to desktop Linux via USB
16 hours 19 min ago
- Find new cell phone and tablet pc
17 hours 17 min ago
18 hours 46 min ago
- Automatically updating Guest Additions
19 hours 55 min ago
- I like your topic on android
20 hours 41 min ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi
It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?