Letters to the Editor
In the syntax section of the April article “grep: Searching for Words”, Jan Rooijackers mistakes shell expansion with regular expressions. The grep command grep flip * does indeed use the regular expression “flip”, but it never sees the *, as the shell has expanded that asterisk to be each file in the directory. Mr. Rooijackers incorrectly explains that grep is using the asterisk as a regular expression meaning all the files in the directory.
—Michael Jones email@example.com
Linux Journal is amazing, and issue #60 was no exception. However, I'd like to point out a minor typing mistake in the article “Linux 2.2 and the Frame-Buffer Console”; the text says the frame buffer device files are /dev/fd*. Shouldn't that be /dev/fb*?
—Celso Kopp Webber firstname.lastname@example.org
Yes, you found a typo we missed. Thanks for pointing it out —Editor
I received my free issue of Linux Journal today and began reading the article “Creat: An Embedded Systems Project” by Nick Bailey. It contains the URL http://ryeham.ee.ryerson.ca/uCinux/ for the Linux/Microcontroller home page. I tried to access this site, with no luck. Can you tell me the correct URL?
Pesky typos! The correct URL is http://ryeham.ee.ryerson.ca/uClinux/ —Editor
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)
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Doing for User Space What We Did for Kernel Space
- Tech Tip: Really Simple HTTP Server with Python
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- 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