A Quarter Century of Unix
Author: Peter H. Salus
Publisher: Addison-Wesley 1994
ISBN: 0-201-54777-5
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!
Today’s modular x86 servers are compute-centric, designed as a least common denominator to support a wide range of IT workloads. Those generic, virtualized IT workloads have much different resource optimization requirements than hyperscale and cloud applications. They have resulted in a “one size fits all” enterprise IT architecture that is not optimized for a specific set of IT workloads, and especially not emerging hyperscale workloads, such as web applications, big data, and object storage. In this report, you will learn how shifting the focus from traditional compute-centric IT architectures to an innovative disaggregated fabric-based architecture can optimize and scale your data center.
Sponsored by AMD
Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6
Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.
Learn more about catching the bad guy in this free white paper.
Sponsored by DLT Solutions
| 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 |
| Trying to Tame the Tablet | May 08, 2013 |
| Dart: a New Web Programming Experience | May 07, 2013 |
- RSS Feeds
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- New Products
- Drupal Is a Framework: Why Everyone Needs to Understand This
- A Topic for Discussion - Open Source Feature-Richness?
- Home, My Backup Data Center
- Validate an E-Mail Address with PHP, the Right Way
- Tech Tip: Really Simple HTTP Server with Python
- New Products
- Trying to Tame the Tablet
Enter to Win an Adafruit Prototyping Pi Plate 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 Prototyping Pi Plate 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
- Next winner announced on 5-21-13!
Free Webinar: Linux Backup and Recovery
Most companies incorporate backup procedures for critical data, which can be restored quickly if a loss occurs. However, fewer companies are prepared for catastrophic system failures, in which they lose all data, the entire operating system, applications, settings, patches and more, reducing their system(s) to “bare metal.” After all, before data can be restored to a system, there must be a system to restore it to.
In this one hour webinar, learn how to enhance your existing backup strategies for better disaster recovery preparedness using Storix System Backup Administrator (SBAdmin), a highly flexible bare-metal recovery solution for UNIX and Linux systems.




3 hours 23 min ago
3 hours 45 min ago
3 hours 55 min ago
3 hours 59 min ago
4 hours 30 min ago
7 hours 21 min ago
7 hours 56 min ago
7 hours 57 min ago
7 hours 58 min ago
8 hours 6 sec ago