The cover of your April 2002 issue has the words “Antiquing Your Desktop”. Huh? Wherzat? Admittedly, I only scoured the index and flipped through each page, not yet having had time to read the thing cover to cover (okay, Playboy arrived at the same time). But I have had my interest seriously piqued by what appears to be a non-existent article. Please, Oh Great Ones, shed some light!
Andrew, the antiquing your desktop referred to Marcel Gagné's article “Interoperate with Me”, where he “revisits a few familiar desktop environments from the past”. I apologize if our sorry little play on words had you looking for something on furniture restoration. I hope you find Marcel's article equally interesting.
I'd like to say that I found Robert Adam's article “The m4 Macro Package” (in the April 2002 issue of LJ) to be very interesting and immediately useful. I read it on the train ride to work and put m4 to good use that very day! Thanks for keeping me hooked on LJ with articles like these.
The article “The CodeWeavers CrossOver Plugin” in the April 2002 issue was very exciting to read. However, the hope instilled by the article was false because of one requirement the article failed to mention: an x86 processor. It was very disappointing to discover that requirement only after checking the web page.
I would have thought the writers and editors of Linux Journal would have been aware of the existence of instruction set architectures other than x86. There are actually quite a number of different hardware architectures on which Linux runs very well. For my part, I have chosen to use an architecture superior to x86 out of simple disgust for segment registers, prefix bytes, the A20M pin, a register model based on the 8008, etc.
—Robert M. Riches Jr.
Please note the correction to the web address on page 89 of the February 2002 issue, from www.mesa.org to www.mesa3d.org, regarding the Mesa 3-D Graphics Library.
Practical Task Scheduling Deployment
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.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- The Firebird Project's Firebird Relational Database
- Stunnel Security for Oracle
- My +1 Sword of Productivity
- SUSE LLC's SUSE Manager
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Parsing an RSS News Feed with a Bash Script
- Google's SwiftShader Released
- Doing for User Space What We Did for Kernel Space
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