I'd just like to pass along my praise for the article “Algorithms in Africa” by Wayne Marshall in the June 2001 issue. This is a definite upgrade over the typical Linux success story. Insightful, committed, poignant, experienced and informed, you should consider Mr. Marshall's perspective as paradigmatic for covering the emerging global presence of Linux. The principles and values here have definite application to domains such as India (where the FSF is opening a branch office), China (where the government has adopted free software, if not political freedom, as its own) and many other areas of the world such as Eastern Europe and South America. Please keep us up to date on global development. And thanks for a superb magazine.
—William G. McGrath
I just wanted to write to let you know that I've consistently found Linux Journal to have the highest quality content in the magazines that cover Linux and technology. I am constantly getting refresher courses, learning about new code and projects, and generally getting fantastic info from your publication.
I especially wanted to compliment you on your regular sections: At the Forge, Cooking with Linux and Paranoid Penguin. Much of the information is applicable to other *nix to boot, making your publication one I keep around for a long time (much to the consternation of my wife). Anyway, thanks folks, and keep up the good work.
In the July 2001 LJ article “Debugging Memory on Linux”, I noticed that the open-source memory checker I've been using was not listed in the article. The checker contains a replacement malloc library plus patches for gcc. The gcc patches wrap C++-like constructors around local variables and insert tests before memory references. This allows checked programs to detect memory overwrites of local variables and some global variables in addition to malloced buffers, and the checking catches overwrites as soon as they happen. You may freely mix object modules compiled with and without checking. The checker also includes replacements for mem* and str* routines and can detect invalid calls against checked memory objects, even from modules compiled without bounds checking.
There are links to the checker from the gcc extensions page at gcc.gnu.org/extensions.html.
In your article “Debugging Memory on Linux” in the July 2001 issue of LJ, you list Purify from Rational as a proprietary tool. As far as I can tell from their web site, they do not support Linux. Also, a while back I did talk to a Rational salesperson who said they didn't have any plans to support Linux. Do you know something else?
Sorfa replies: It looks like you are right. At the time of writing the article (early this year), there was a hint that Purify would be supported on Linux. I assumed (wrongly) that by the time the article made it to press, it would be available. It is a pity and I apologize for the incorrect info. It looks like the only proprietary alternative is Insure++.
I must respectfully disagree with Allan Hall in his letter of the July 2001 issue. Certification per se is certainly no substitute for experience, but it does show that a candidate at least took the initiative to attend some classes, read some books and pass some tests. It also usually requires putting a few hundred dollars up front.
I don't see how one could give a certified candidate anything but an edge over an uncertified one, experience levels in the two being equal.
Just want to write to let you know that Robin Rowe's article “MPEG-1 Movie Players” (May 2001) was very helpful and also convinced me to renew my subscription to Linux Journal. I wanted to play movies on my new notebook and had played with xanim before, but your recommendation of MPlayer was great. It compiles, installs and works like a charm. Thanks again.
It's articles like “CVS: an Introduction” (July 2001 issue of LJ) that keep me subscribed to Linux Journal. I've been doing basic RCS for years and knew there had to be a better way. But let's face it, the man page for CVS is a little overwhelming to the uninitiated. But the day after reading the article, I was using CVS at work (the magazine is opened on my desk to page 72 right now), and I'm feeling much better about long-range management issues now. Keep 'em coming! So many thanks to you and Ralph Krause for putting this together.
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!
- Paranoid Penguin - Building a Secure Squid Web Proxy, Part IV
- SUSE LLC's SUSE Manager
- Google's SwiftShader Released
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- SourceClear Open
- SuperTuxKart 0.9.2 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