Letters to the Editor
In Linux Journal, November 1997, there is an article by Marc Allen about Linux running a gasoline station. Mr. Allen, an employee of the vendor of the system, Schlumberger, states: “We are, however, the only Unix-based one.”
Not a bad story, but not completely true. At the gasoline station where my brother works, the whole system (pump control, sales, e-cash) has been working under SCO Unix for more than 1 year—24 hours a day, 7 days a week, running on a 80486 PC.
The company that makes the software is Sofitam of Belgium (Satam is the gasoline station equipment).
—Groeten Ben Erkens, The Netherlands firstname.lastname@example.org
I would like to point out that in the article called “Linux as a Proxy Server” by Peter Elton in the December issue of LJ there was absolutely no mention of Linux's built-in firewalling and proxying support. As I think most seasoned “roll your own” kernel compilers will know, Linux can do almost all of what Peter describes without resorting to any extra user-level daemons or utilities. I am speaking specifically of the kernel's IP Masquerading, Transparent Proxying, Accounting and Firewalling features. From the included Listing 1, it seems that Peter was using a very antiquated kernel indeed and perhaps these features did not exist. When writing about bleeding-edge operating systems one should do the proper homework to be aware of current OS features.
—Oliver Jones email@example.com
I have been following LJ for over a year now and can't believe how good it's getting. I like the design changes, the way you shortened the “What is Linux” part, and every issue is a better mix of topics than the last one.
If you want to hear something funny, my brother works at a major American software company, and he tells me that developers there are bringing up the topic of porting their products to the Linux platform more and more frequently. Apparently there is a lot of Linux quietly installed around the world (enough to be seen as a significant market by a large American software player).
—Harold Sinclair firstname.lastname@example.org
I'm writing in response to the review of the “Microway Screamer 533” by Bradley Willson which appeared in the January issue of Linux Journal. This review is especially timely for me as the research group I work with is purchasing a new computer for development work, and the price and performance of the Alpha-PC running Linux are extremely attractive. As I started to read the article, however, my excitement quickly waned. Nowhere in the review of the Screamer 533 are there meaningful benchmarks. Moreover, the benchmark that the author put together is worthless for precisely the reasons mentioned in the article: so why include it?
The author would have done better for Linux Journal and Microway if he had included results from the SPEC benchmarks (SPEC benchmarks run on the Screamer 533, not benchmarks from Digital with the 533/21164A chip running Digital Unix in some form of an Alpha Station), the BYTE and Bonnie benchmarks and, perhaps, some of Microway's own programs. All benchmarks have shortcomings but they are much more useful to convince coworkers and bosses with than stories of fast cars.
Please Linux Journal, give us meaningful hardware reviews.
—Rich McClellan email@example.com
I wrote to Ann Fried and asked her if she would make 533 benchmark numbers available on their web site. I have not received a reply yet.
For you, the article did not satisfy your questions and for that I apologize. I wrote the article for a less technical audience because of market demographics. There are simply more Intel/Linux users than Alpha/Linux people. The focus of the piece was to direct their attention to a machine they might otherwise overlook because of price, technical astigmatism or both. The academic and technical audiences generally have resources that allow them to own an Alpha and understand it, as you have demonstrated.
I realize that this does not help you sell the machine to management, and to that end I will continue to work with Microway to get some meaningful numbers to you.
—Bradley J. Willson firstname.lastname@example.org
—Joey Hess email@example.com
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
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- 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