UNIX: An Open Systems Dictionary
Authors: William H. Holt, Rockie,. Morgan
Publisher: Resolution Business Press
Reviewer: Laurie L. Tucker
When my boss first picked up this book, he went in search of the word “Linux”. To his great surprise he found it, and then declared that this was a book worth having. After using this dictionary for the past two months, I have to agree; and not just because it contains a definition for Linux in it.
The book includes over 6,000 entries and does a fairly good job of keeping definitions as free of jargon as possible. As a result, it can be used by people with a broad range of Unix experience, from the “newbie” (not defined, but we know what that is!) to the “wizard”.
As the Assistant Editor for Linux Journal, and a fairly new sysadmin, the book has come in handy quite a few times. I've used it to figure out what POSIX really stands for (Portable Operating System Interface for computer environments (X)), and I've used it to better understand what I read in articles that are submitted to Linux Journal for publication.
The book contains such basic terms as: pop-up window (with a figure showing one), command line, directory, port, space bar, kernel (with the standard bull's-eye graphic), software, CPU, and edit. These are all described so that true computer novices can better understand computers. Lots of acronyms are included, like ASCII, FTP, TCP/IP, VMS, SCSI, RISC, MTA, and LAN.
There's information on Unix-style word processing: serif, sans serif, roff, nroff, troff, and mm macros.
Important people: Dennis Ritchie and Brian Kernighan.
Unix operating systems: SVR, BSD, UNIX, XENIX, and SunOS.
The Information superhighway: Internet, WWW, nslookup, archie, gopher, WAIS, hypertext, T-1, PPP.
Sysadmin terms: wtmp, sendmail.cf, mountd, mnttab, named. local, /dev/null, DNS, telinit, a whole bunch of /etc/* entries.
This book even contains historical gossip about the Michelangelo virus!
What don't I like about the book? It includes pronunciations of words, like WA-BEE, SCUZZY, NAME-D, NROFF, GOO-IE, etc., listed as entnes. I think it's kind of hokey. But these pronunciations are also included with the “real” definitions, and the dictionary does a very good job of cross-referencing.
It also includes a scattering of figures and tables which enhance the text definitions.
At the end of the book there are a number of useful appendices, including references for basic vi commands, basic Emacs commands, FTP commands, lpc commands, RFS parameters, signal values (preSVR4, SVR4, BSD), Telnet stuff, and some commonly used talk-mode jargon.
Five years ago, Bill Holt decided that this was a book he needed. Since there wasn't one available, he and Rockie Morgan wrote it. That's one of the best reasons for creating something, and this dictionary is something I'm glad I have.
Laurie Tucker (firstname.lastname@example.org) is the assistant editor of Linux Journal, cover designer of the September issue, and sysadmin of linuxjournal.com; a Linux system
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
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- Google's SwiftShader Released
- Parsing an RSS News Feed with a Bash Script
- LiveCode Ltd.'s LiveCode
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