Letters to the Editor
In my previous letter you published in the “Letters to the Editor” column, I referred offhand to “redirecting output to Console 9, as described in a previous issue of Linux Journal”. I have received quite a few inquiries as to which issue that was in and how to do it.
The issue was #31, the column was “Novice to Novice: Keyboards, Consoles and VT Cruising” by John M. Fisk and the page was 17, the section heading “Putting that Unused VT to Work”. However, you don't have to look up that issue, as it is quite simple. Just add the following line to /etc/syslog.conf:
and all your syslog messages are sent to console 9 as well.
Thanks, Linux Journal, for publishing that tip back in November 1996. It has made a lot of system administration tasks easier. —Cynthia Higginbotham email@example.com
I have been using Linux since 1992 and have built up a successful business providing offices with an effective cheap alternative to expensive Microsoft servers and products. Up until the beginning of this year, it did not matter which distribution you used; everything worked just fine. Okay, each distribution worked slightly different, but they all used the same libraries and kernel. When I read in the computing press that the big software houses were starting to support Linux, I knew that before long, Linux would rival MS on the same level for both back end and desktop.
However, within a few weeks of Intel buying a stake in Red Hat, I read that some products will work only with the Red Hat version of Linux. We must stop this now, or in two years we will have a situation of Intel-Hat becoming the next Microsoft with an 85% stake in the Linux market. Last week I installed a mail, Samba and web proxy server into an office in London. I was asked, “Is this Red Hat you are installing?” I said “No, it is Linux.”
I believe we must push for a common standard. Any product released for Linux must work on all distributions. Please don't let Intel-Hat muscle their way in or we will be in the same position in two to three years as we are with Microsoft now. —Robert Weeks firstname.lastname@example.org
I read LJ here in Germany and have often read good reviews in your magazine. Anyway, this special review “Applix vs. StarOffice” by Fred Butzen in the October issue is somewhat incorrect.
StarDivision released StarOffice 4.0 some time ago, and three service packs have already reached the users. Since 4.0, they are no longer using Motif but their own StarView GUI which has a Windows look and feel. Speed, features and reliability have all been improved greatly since the 3.0 version. By now, the Linux StarOffice 4.5 preview release is out and can be tested. This preview got released even before the other 4.5 preview releases had been shipped. You can even buy an official version of StarOffice 4.5 including the handbook and a sheet with notes about the differences between the Windows and Linux versions. They are actually selling the 4.0sp3 version now, with the guarantee of sending you the new 4.5 CD-ROM as soon as it is no longer a preview/beta version. —Holger Lehmann 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
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- Google's SwiftShader 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