Newton's Telecom Dictionary
Author: Harry Newton
Publisher: Telecom Library, Inc. ISBN: 0-936648-42-2
Reviewer: Phil Hughes
Newton bills his book as the “world's number 1 selling telecommunications dictionary”. This new edition weighs in at 1110 pages and is totally filled with computer and telecommunications terms. Although you probably won't be looking for everything in the book you can be fairly sure that what you are looking for is there.
For example, look under “error control protocols” and you will find a very good explanation of V.42, MNP and LAP-M stretching to about a page. Or look up “group 1, 2, 3, 3bis & 4” and get another one-page explanation of various FAX standards. I even found “pentium” in the book. I had to look for PEP, Telebit's proprietary modem protocol, to stump the book.
If it has anything mildly to do with telecommunications it seems to be in the book. That's the good news. But there's some bad news as well. First, the whole book is set in Helvetica type. This works ok for short definitions but it becomes just plain hard to read for longer explanations. The type face is fairly large so that isn't a serious problem, but Harry could have made a better book and saved a lot of paper by doing the work in a serifed face and smaller point size.
The second problem with the book is an assortment of small errors. For example, the 8088 is described as the 8-bit version of the 16-bit 8080. Most anyone knows the 16-bit cousin is the 8086, not the 8080, but such an error makes me nervous that there may be some real hidden “gotchas” hidden in the more technical information. The book even defines the 80387SX as the coprocessor for the 80385SX microprocessor. Yeah, we all know that this was supposed to be the 80386SX as the book has already said but, once again, simple typos like this scare me.
The bottom line? I think Newton's book is worth purchasing, but I hope the 7th edition addresses these concerns.
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!
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Tech Tip: Really Simple HTTP Server with Python
- SuperTuxKart 0.9.2 Released
- Doing for User Space What We Did for Kernel Space
- Google's SwiftShader Released
- Parsing an RSS News Feed with a Bash Script
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