September 2013 Issue of Linux Journal: HOW-TOs
How'd Ya Do That?
I tend to read science fiction or fantasy for entertainment and/or escape from reality. In fact, I suspect my childhood would have been far less tolerable had I not been able to escape to Mordor for a time or hide from the bugs with Johnnie Rico. And as much as I loved watching the exploits of Captain Picard and his crew, there was never an episode on how to build a replicator. Or a holodeck. Or a phaser. And that's what I've loved about Linux Journal for far longer than I've been on staff: it shows how to do stuff!
This issue not only continues that legacy, but it also even focuses on it! I apologize in advance for any lost productivity at work while you live out the How-To issue this month.
Reuven M. Lerner starts out with a look back at 20 years of Web development. It's hard to believe it's been 20 years since the first www was put in a browser's address bar, but what a 20 years it's been! No more blink tags and far fewer animated GIFs make the Web a lot more fun, even if it is still "Under Construction".
Necessity truly is the mother of invention, and Dave Taylor knows that better than anyone. As he continues to battle with a DDOS on his server, he shares his process with us all. While scripting is the Swiss Army knife of system administration, it's not terribly helpful if your scripts have a "dull blade". Dave shows some best practices on creating scripts that can provide invaluable information.
Kyle Rankin reveals that he's really been lying all these years, and that he uses Windows Vista on a 17" sports utility laptop. Okay, that's a complete lie—I couldn't resist, sorry Kyle. In true Kyle Rankin form, he describes how to use and manipulate a command-line calendaring app, gcalcli. If you want to use Google Calendar, but don't want to load up that pesky browser, Kyle's article is for you.
Rather than teach how to do something this month, I took the time in my column to show you how I do things. I get lots of e-mail asking what sort of hardware and software I use, so I figured the How-To issue was a good time to spill the beans. Some of my setup is probably not surprising, but part of it might be. I'm looking forward to feedback and to seeing what everyone else uses.
Next up, Peter Cook provides a review and tweak guide for the Acer C7 Chromebook. While targeting a similar market to the ARM-based Samsung Chromebook Bill Childers reviewed recently, the C7 uses the Intel architecture, and sports a full hard drive. It's upgradeable, and after reading Peter's article, you'll see it's quite customizable.
Janos Gyerik follows with an excellent article on command-line tricks. I've been using Linux for almost two decades, and I learned a lot from Janos' cornucopia of CLI tricks. Somewhere, Kyle Rankin has to be proud. I also learned some cool things from Petros Koutoupis this month with his article on hard drive caching. Hard drives are slow, and even the fastest spinning media is the bottleneck in any system. By caching to RAM or SSD, Petros explains how to take advantage of Linux's powerful caching abilities.
Bill Childers finishes up our How-To articles with his tutorial on setting up vcsh for managing configuration files. If you've ever tar'd up your /etc directory, and called that good enough, you won't want to miss Bill's article. In fact, most articles in this issue start with the premise of, "you used to do it this way, but you should try this!" That's part of the reason I love the Linux community so much. The old saying "if it ain't broke, don't fix it" is all well and good, but if you're a Linux user, a better saying might be, "if it ain't broke, good, that means we can work on making it better!"
This issue showcases what made me a Linux Journal reader years before I was on staff. I love to read about stuff, but nothing is quite as exciting as getting to do that stuff yourself. I hope you enjoy this issue as much as we've enjoyed putting it together. Now if you'll excuse me, I'm going to use my replicator and make some Earl Grey, hot. Beam on over and I'll make you a cup too.
Available to Subscribers: September 3
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
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
- Doing for User Space What We Did for Kernel Space
- Parsing an RSS News Feed with a Bash Script
- Google's SwiftShader Released
- Rogue Wave Software's Zend Server
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