Letters to the Editor
For several years, my son has been telling me about free software, and I have failed to understand completely what he meant. I associate “free” with “without cost”, and since I spend very little on software anyway, I have felt no need to use “free software”. I did not until recently understand that the freedom to change the software, which access to the source code provides, is far more important than lack of cost.
This misunderstanding is widespread. Therefore, I would like to propose an alternate term for software with source code—“liberated” software. Liberated software liberates the programmer. —Daniel L. Johnson, M.D., F.A.C.P email@example.com
Once again I'm at work in front of my HP workstation, about to request more information on a software product I noticed in an LJ ad, that just might solve a problem a co-worker asked me about last week. A few months ago my system administrator bought BRU (from an LJ ad I gave him) for an HP workstation headed to a tele-commuting co-worker's house. I occasionally daydream about having time to explore my Linux system at home, but I consistently read LJ because its columns, articles, and advertisements give me information I use at work. —Greg Deitrick firstname.lastname@example.org
I would like to say that I was absolutely impressed with the May issue of the Linux Journal, especially with the articles which dealt directly with system administration such as how to set up a WWW site, the article of an ISP using Linux, the Majordomo setup/configuration article, etc.
Keep up the good work. Now I remember why I subscribed to this magazine in the first place! —John Coy email@example.com
Several times your articles have mentioned a guy from NASA who uses PVM instead of supercomputers, and that he gave a talk on it at a conference, etc.
Please have him, or someone in attendance, paraphrase what he is doing, and perhaps speculate that nnn Pentium 90's equals such and such Supercomputer, at so many gigaflops, etc.
Please also consider a `Porting Corner' article every month to summarize the progress of ports to other computers (i.e. Alpha, MIPS, PowerPC, etc). Only a quarter page or smaller would be required, with a line or two on each port. —Doug Fortune
In response to your first point, we do intend to have an article on this system. However, there is no way to say that nnn Pentium 90's is equivalent to any supercomputer; a loosely-coupled parallel system like that works well only on certain problem domains. We intend to have an article on the Beowulf system, but it is currently an ongoing research project, and is not ready for an article at this time.
The architects of Beowulf are about to build a second-generation system based on their current experience and research with their first system, and the results from that system will be more interesting and worthwhile to readers with a serious use for the technology. All the software that they are using will be released as a package, and when it is, we will certainly pursue an article.
In response to your second point, progress on the ports to various architectures does not progress in a way that facilitates monthly reporting. We will report on significant progress on the ports. In particular, our “Stop The Presses” article in this issue mentions that the Linux/Alpha port is now self-hosting. We will also report on the state of all ports from time to time, as we did recently.
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!
- Paranoid Penguin - Building a Secure Squid Web Proxy, Part IV
- SUSE LLC's SUSE Manager
- Google's SwiftShader Released
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- SourceClear Open
- SuperTuxKart 0.9.2 Released
- 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