Letters to the Editor
Over a year ago, you ran an article by John Little (“Setting up a Sun SPARCstation”, October 1997) on getting a SPARC up and running on Red Hat 4.2. Shortly after reading it, I came across an old SPARC IPX at the local computer graveyard that essentially needed a CMOS battery to function properly. I snapped it up and never got around to installing Linux on it until recently. Since I've moved, I couldn't find the original article and was overjoyed when I found it in its entirety on your web site. That information along with the Red Hat Powertools 5.1 disc allowed me to get the IPX up and running in under an hour.
Thanks again for all the great information with no fluff! —Leon Hauck email@example.com
I just received the October issue of Linux Journal and was alarmed to discover that I had omitted from my “Future of Linux” report the most important “Resource” link of all: that of the on-line version of the article itself, which I continue to update almost weekly:
Recent developments include Linux product announcements from Caldera (Netware), Citrix and Sybase; a San Francisco Chronicle report that the last of the large databases without a Linux port, IBM's DB2, will be announced for Linux by the end of September; and news about Dell's Linux pre-installations, a number of Open Source announcements and a new Linux quarterly in French: Linux Magazine France.
More important, perhaps, is the fact that the dozens of links embedded in the text (e.g., for the Top 500 supercomputer list or the AP1000+ multi-computer) are available. —Greg Roelof firstname.lastname@example.org
It's ironic that when I was reading Griffin Caprio's letter in the October issue, I had the July issue in my briefcase to take to work in order to photocopy two articles for some coworkers. Please do not let the prospect of big circulation lead you to water down the content of LJ. I have seen other computer magazines go that way, and abandoned them. LJ is now the only one to which I still subscribe. —Tom Kuiper email@example.com
In the article “Applixware vs. StarOffice” that appeared in the October LJ, Mr. Butzen states that his criteria for testing included portability, specifically the “... ability to import and export files to Microsoft Office.” While he touched on this issue briefly with his experience exporting to Word 6.0, he neglected a major issue in this regard.
To my knowledge, neither suite's presentation package will export to Microsoft PowerPoint format. While this may seem like a minor point to some, it is a huge issue for those of us who use presentation software as a routine part of our jobs. Most of us are not fortunate enough to have access to PC/projection systems running Linux and the appropriate presentation software, let alone fortunate enough to find someone willing or able to create 35mm slides from either of these formats. While exporting presentations to Windows Meta Files is supported, this is a poor substitute compared to having the project saved in a format that is easily edited and displayed, particularly when one is far from his friendly Linux box.
I have been a StarOffice 4 user for about six months. While I find it a bit slow, the major factor preventing me from completely abandoning Microsoft Windows95 and Microsoft Office is StarOffice's inability to export presentation files to a more “universal” format. I'm surprised that with Linux's popularity in the scientific community and the common use of presentation software in those endeavors, this subject has not received more attention. —Frank Lynch, MD firstname.lastname@example.org
I enjoyed the October “Stop the Presses” column, but felt it was rather dated by the time it hit my mailbox, given the recent actions by Oracle, Sybase and IBM(DB2). Have you considered running the column on the LJ web site instead, so as to keep the column from becoming too out of sync with current Linux events?
I've been working in the database industry for the past 2 1/2 years now, so I naturally feel that the database market will be critical to Linux's future success. As such, I've kept a close eye on the Informix, Oracle, Sybase and IBM announcements of late. Although the Informix-centric information was most excellent, another article covering the recent adoption of the Linux platform by all the major database names would be most welcome. (I'd be interested in finding out whether my own suspicions about the meaning of these trends are shared by others.)
Regardless, I'm planning on photocopying the “Stop the Presses” article and posting it outside my door as the latest salvo in my long-running Linux-PR campaign I've been waging within my company.
Many thanks, and keep up the good work! —Peter Kuklaf email@example.com
We do sometimes put the “Stop the Presses” column on the web as soon as it is written, usually in our on-line e-zine Linux Gazette. However, that did not happen for this particular column —Editor
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
- Tech Tip: Really Simple HTTP Server with Python
- Non-Linux FOSS: Caffeine!
- Returning Values from Bash Functions
- Managing Linux Using Puppet
- Doing for User Space What We Did for Kernel Space
- Rogue Wave Software's Zend Server
- 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