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!
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SuperTuxKart 0.9.2 Released
- Google's SwiftShader Released
- Parsing an RSS News Feed with a Bash Script
- SourceClear Open
- Doing for User Space What We Did for Kernel Space
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide