I much appreciated the article by Jan Schaumann, “More than Words” in the November 2001 issue. Not only did I learn some new ways to deal with .doc files, but I was pleased to see him plug TeX and LaTeX. Word processors were invented for those who want to aid and abet in their own victimization, and the users of word processors deserve all the problems and version incompatibilities they experience.
I've been a TeX and LaTeX user since 1985, and everything I've written since then still runs through typesetting with the same results. Using a simple text editor, one can generate PostScript files, Portable Document Format files and HTML files—that is, one source document can be a printable manual, a downloadable manual and a web presentation. We even use LaTeX to generate e-commerce click-to-buy pages, the generation of which is easily automated. The make utility automates generation of all of the mentioned outputs with dependency checking. Multiple authors can take part in an “expression” and have it present a consistent and always up-to-date content. Examples of our usage can be found at www.amplepower.com and www.pwrtap.com. Word processors? No thanks, I have work to do.
(LJ, November 2001)
The article read:
Favorite Desktop Environment
1. KDE 2. GNOME 3. Window Maker
This was one of the most popular categories, and KDE is the clear winner, receiving 40% of all votes. GNOME came in second with 24.5%, and the favorite write-in was xfcr. And special mention, of course, for the command line.
The “favorite write-in” mentioned above should be spelled XFce and not xfcr.
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|
- Stunnel Security for Oracle
- The Firebird Project's Firebird Relational Database
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Google's SwiftShader Released
- SuperTuxKart 0.9.2 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