UNIX for the Hyper-Impatient (CD-ROM only version)
Authors: Paul W. Abrahams and Bruce R. Larson
Price: $28.95 US for the book or the CD-ROM and $49.95 US for both
Reviewer: Daniel Lazenby
Looking for an on-line reference that cuts to the chase and is written toward the technically oriented and somewhat Unix aware? If so, UNIX for the Hyper-Impatient may be worth your consideration.
The book is actually a hypertext repackaging of UNIX for the Impatient, Second Edition. The content of the original book contained many internal cross references and pointers to related information. I believe the existence of these “links” is one of the reasons the book was released in an all-electronic hypertext format. There seems to be little difference between the content of the electronic and hard copy versions of the book.
The book is organized functionally and divided into fourteen chapters and six appendices. You might want to read the Introduction and Concept chapters sequentially. Then again, you may find yourself randomly skipping in and out of the other chapters. Chapters 3, 4 and 5 are functionally arranged to answer the question “What command(s) can I use to ___” (you fill in the blank). Chapter 3 focuses on operations that may be performed on files. Chapter 4 addresses data manipulation using filter commands. Chapter 5 discusses utility programs used to monitor and manage your Unix environment. Titles of the remaining chapters include Chapter 6 “The KORN and POSIX Shells”, Chapter 7 “Other Shells”, Chapter 8 “Standard Editors”, Chapter 9 “The GNU Emacs Editor”, Chapter 10 “Emacs Utilities”, Chapter 11 “Mailers and Newsreaders”, Chapter 12 “Communicating with Remote Computers”, Chapter 13 “The X Window System” and Chapter 14 “Managing Your System”. The Appendix contains an Alphabetical Summary of Commands, Comparison of MS-DOS and Unix, a Resource list, a Glossary and an Index.
Chapters 6 through 14 are largely factual in nature. These chapters often state the basic facts, concepts and identify the relevant files. To me, these chapters seem to present the “what”, “where” and a little of the “why” of the selected topic. An example of this approach is the X chapter, which opens with an explanation of what the X Window System is and what it does for you. It continues by describing how the various parts of X look and what they do. This chapter then describes the high level flow of events that initiate an X session, including the role the X initialization files play in the initialization process. Descriptions often contain information as to why one would be interested in the particular X file, or would want to use the particular X feature or function being discussed. This chapter on X is a complete walk through the X environment, files and file contents. From a user's perspective, few stones have been left unturned. This type of reference would have saved me a lot of angst when I encountered my first X environment.
The Alphabetical Summary of Commands is divided into an alphabetical listing and a summary of the commands. There are two hypertext links for each command in the alphabetical listing. One link jumps to a summary of the command and the other jumps to a detailed explanation of the command. The command summary provides the level of detail I associate with O'Reilly's Linux (or Unix) in a Nutshell book. Detailed command explanations are well written descriptions that include examples.
Addison-Wesley's web site provides access to the preface of this book. Reading the on-line preface will give you a feel for reading an entire book on-line. It is also a good example of the authors' style.
A product called DynaText displays the hypertext book and provides the user interface (see Figure 1, Reader Window). In addition to the expected read, browse, search and print functions, DynaText provides the user with the ability to define his own bookmarks, notes, and cross references. A journal feature allows the user to record and retrace his path through a series of topics.
About ten short pages describe how to use the DynaText software and supply the meaning of the various icons. The DynaText on-line User's Guide is also useful, as some of the interface features work a bit differently than what you might expect. For example, the “Bookmark” button remains greyed out—until you actually highlight some text. Clicking on the active Bookmark button produces a dialog box to record your bookmark. The button greys out again after the bookmark is defined. The same process is true for the “Notes” button. User-specified names are assigned to bookmarks and notes at the time of creation. DynaText did not allow me to use the same name for a bookmark and a note I associated with it. Buttons on the tool bar are nice, yet I got more utility out of the bookmark and notes accelerator keys. The appropriate “Annotation Manager” menu option must be used to access any user-created bookmarks or notes.
Most of the hypertext links are colored green and quite obvious. These green hypertext links may be a title, a Chapter section number, a page number or an Appendix reference number. Another set of hypertext links is indicated with one of several icons. A third type of hypertext link presents no immediate visual indication of its existence. If a pointing finger cursor appears when you place the cursor over a word, then there is an active hypertext link. This style of a hypertext link is used with glossary words. Clicking on any one of these hypertext links opens another window containing the referenced content.
Every predefined hypertext link opens a new window. This technique makes it easy to see text at both the point of origin and destination. On the other hand, this technique can quickly cause the screen to become cluttered with windows. With several windows open, I found it difficult for me to tell which window belonged to which hyperlink jump.
Considering the keyword search capability of the browser, I was disappointed not to find an accelerator key that placed the cursor into the on-screen search field. I found one other search characteristic annoying. The browser left the search word in the search field upon completion of the search. Since each jump opens a new window, as soon as a new window opened, the browser would search for the word in the previous window's search field. I received several “not found” dialog boxes that I had to clear after making a jump.
A VCR style button panel is used to represent the “Journal”. A Journal is created by clicking on the “Record” button and navigating through the book. There is no need to worry about wrong turns or jumps. The Copy, Paste and Cut buttons allow you to re-sequence or remove topics. You can even add topics you may have missed. Once established, this journal may then be used to retrace the same path or to guide another person through the same set of topics. There are two journal playback modes: continuous and frame by frame. Out of the box, the continuous playback interval is set to three seconds, but can be adjusted. Frame by frame uses the VCR fast forward and reverse buttons to page forward or page backward, one page at a time. The VCR panel is a bit large for my tastes. I found myself moving it around the screen to get it out of the way while recording and during the playback.
If you do not feel the predefined links meet your needs, you can add your own one- or two-way hyperlink to the book. A hyperlink simply jumps from one book location to another. Creating a user hyperlink is as simple as marking text at the starting point, the ending point, indicating one- or two-way link and naming the link. A user-created hyperlink does not open a new window. This type of link jumps directly, within the same window, to the destination point. As with Bookmarks and Notes, you may have to use the Annotation Manager to locate user-created hyperlinks.
Printing excerpts produced some odd results. I selected two short chapter topics to print (Chapter 6.5 and 13.1). Each of these sections happens to have a “Page Icon” on it. These sections were printed across two pages. The first few lines of the section were printed on one page and the remainder was printed on another page. Several words were dropped from the sentence split between the two pages. Selections and chapter sections did not contain a Page Icon printed as expected.
|Speed Up Your Web Site with Varnish||Jun 19, 2013|
|Non-Linux FOSS: libnotify, OS X Style||Jun 18, 2013|
|Containers—Not Virtual Machines—Are the Future Cloud||Jun 17, 2013|
|Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer||Jun 12, 2013|
|Weechat, Irssi's Little Brother||Jun 11, 2013|
|One Tail Just Isn't Enough||Jun 07, 2013|
- Speed Up Your Web Site with Varnish
- Containers—Not Virtual Machines—Are the Future Cloud
- Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer
- Linux Systems Administrator
- Non-Linux FOSS: libnotify, OS X Style
- Senior Perl Developer
- Technical Support Rep
- UX Designer
- Android's Limits
- Reply to comment | Linux Journal
1 hour 5 min ago
- Yeah, user namespaces are
2 hours 21 min ago
- Cari Uang
5 hours 52 min ago
- user namespaces
8 hours 46 min ago
9 hours 12 min ago
- One advantage with VMs
11 hours 40 min ago
- about info
12 hours 13 min ago
12 hours 14 min ago
12 hours 15 min ago
12 hours 17 min ago
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?