Letters to the Editor
I read with interest the article in the June issue (#63), “MP3 Linux Players” by Craig Knudsen. It seemed to imply the Empeg product was the only solution for MP3 players in cars. I would like to suggest braver readers take a look at http://www.mp3car.com/. The site has great examples and links on how to build one yourself. Thanks.
—Alistair Hedge firstname.lastname@example.org
Great article! Thanks for printing “Stuttgart Neural Network Simulator” by Ed Petron, July 1999. I have been working with neural networks for two years now in my high school science fair projects. This article provided a good introduction that I would have loved to have had handy when I first started working with neural networks. I really enjoy seeing Linux being used not only as an alternative OS, but as an OS with scientific and educational purposes.
—Michael Katz-Hymanm email@example.com
The first thing I did after reading the Guest Editorial entitled “The Point Really is Free Beer” was to check the cover date on the magazine to see if it was an April Fool's joke—sadly, the issue date was July 1999.
People like Eric Hughes lead the Open Source movement in the same way that the front bumper on my truck leads me down the highway: it's along for the ride, but it really has nothing to do with who's driving the machine or how we get where we are going.
He states that “To be generous, maybe one-quarter of the total value of software comes from the product.” To see what a lie that statement is—it is only necessary to imagine his proposed institution without the software. What value does it have? The answer is zero. All of the well-dressed staff, administrators and planners are of no value whatsoever without the people who produce the product.
The converse is not true; programmers like Linus and the other open-source developers have great value to all of humanity without the participation of institutionalized parasites in the process.
Mr. Hughes points out that most of the work so far has gone into building software tools. Well, duh—first you build tools—then you use those tools to build applications. You can't do it any other way.
Mr. Hughes has the audacity to accuse those of us who write open-source code of having selfish ends. Wow! What about Mr. Hughes' goals? Assume that two-thirds of the 25 million dollar grant he wants to get the ball rolling would go to “the talent”. That leaves about 8.3 million. Building construction and furnishing will eat up most of that: can't look chintsy—have to look solid to impress the idiots.
That will leave about one million for staff salaries. Since I assume Mr. Hughes will be willing to lead us, I guess his take will be about five hundred thousand a year, with the rest to be split up among the other drones at the institution. Bah.
Instead of giving grants to useless institutions or to groups of programmers, why not give the whole thing to the individuals who do the work? I can promise you my needs are awfully small compared to some institutionalized thief. Fifteen hundred a month would keep me writing open source pretty much full-time. It is about time the worker bees realize they are the ones with the sting—not the drones.
One hundred per cent of the value of software comes from the product. Period—end of discussion.
—Bob Canup firstname.lastname@example.org
I was chatting with someone and mentioned that Linux Journal was just full of advertisers with affordable Alpha systems, and sent him to you. He couldn't find a list of your advertisers. Sounds like a business opportunity to me. List hardware vendors and software vendors. Let me search for vendors by name and by product. Then I could choose to buy from your advertisers, or I could find one that sells what I am about to buy and patronize them.
Thanks for doing everything else right. The guy I was talking to will probably be subscribing now. I gave him four links to Alpha vendors on the Web right out of the handiest issue. (Then I quoted the rates, and he replied, “cheap”.)
—Duane Smecker email@example.com
A list of advertisers in each issue can be found on the web site Table of Contents page for each. This list includes links to the advertisers' web sites —Editor
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