Letters to the Editor
Just a note about a type-o in your March 1995 Kernel Kornel. On page 52, column one, paragraph 4.
You use request_irq() instead of request_dma() and you wrote “IRQ channel” instead of “DMA channel”.
I don't think this caused any confusion because it is evident that you were talking about DMA.
Anyway, just thought I would bring this to your attention. Besides it gives me a chance to say keep up the good work.
—Don Hiatt, firstname.lastname@example.org
Michael Responds: ACK! You are absolutely right. Mea culpa.
I've read the System Administration article (“How to log friends...”) in the March edition of Linux Journal and found it quite useful. But I think the following remark is useful, too: if the logging level is set to =something, i.e. =debug, then only messages with this level are logged.
By the way, the syslog configuration can be tested with “syslog_tst”, which I found in /usr/sbin on my Slackware 2.0.1-based system. I do not find a man page for it, and there is no mention of it in the syslog man page.
—Joachim Schaaf, JS@Coopy.Fido.De
I am writing to inform you that my address has changed.
Basically, my house burnt down and I was forced to move. Fortunately all of my back issues of LJ were on loan to my scungy mates, who had not returned them for 3 months or so, and thus were not burnt.
—Leon Harris, email@example.com
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
- Google's SwiftShader Released
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