Letters to the Editor
These comments are about the article entitled “Linux in Lebanon” by Ibrahim F. Haddad which appeared in the January 1999 issue.
I was pleasantly surprised to see LJ cover Linux usage in our country and commend Mr. Haddad on a nicely written article. I would, however, like to point out that company usage of Linux has been somewhat downplayed. Our company is almost exclusively a Linux shop, and we have created very large web sites which are served on Linux machines.
For example, LebHost (http://www.lebhost.com.lb/) is a comprehensive search engine about anything related to Lebanon, and our main web site offers free web sites to Lebanese (http://www.greencedars.com.lb/). Both sites are Linux-based and very heavily visited. We also have dozens of hosted domains on Linux machines as well.
In our case, it was clearly not a matter of “follow the crowds”, even though Microsoft software is “freely available” in a pirated form here. We find Linux much more attractive to use because of performance, flexibility, superb support and source code availability.
—Edmond Abrahamian, PhD. firstname.lastname@example.org
I read the article in February's LJ, “Linux Csound” by David Phillips. I think you should add a link in the “Resources” section to the Quasimodo Project, http://www.op.net/~pbd/quasimodo/.
This project is a rewrite of Csound for UNIX, supporting multi-threading, with enhanced real-time performance, GUI, modular, etc. A first ALPHA (without GUI) is available now. When this project is finished, it will be absolutely the coolest Software Synthesizer System that has ever existed.
SSC's Distribution Choice
I am a little confused over which distribution to get and install on my machine. All seem fine for most tasks. I remembered in a past issue of LJ that SSC uses the Debian distribution. Why was Debian your choice over other distributions? Was it because it is an all-volunteer distribution versus commercially-based distributions such as Red Hat, Caldera and others?
Additionally, if I choose a distribution other than Red Hat, I fear I may not be able to purchase software products because companies are specifically alliancing themselves to support only Red Hat instead of all major distributions (or, rather, certain components used in all distributions). This is reminiscent of Wintel systems versus Apple. More software was made to support Windows. People, like vendors, will go where more is offered. Distributions that are not Red Hat compliant will be left in the dust—a situation that will lead to factions within the Linux community. Companies need to provide products without requiring Red Hat be installed.
—Jean Tellier email@example.com
Yes, our primary reason for choosing Debian was that it is a volunteer effort. Red Hat is part of the effort to develop standards for Linux that will keep applications from being distribution-specific. While many companies have ported their products to Red Hat first, I don't think any have said they will not support other Linux versions. Informix came out for Caldera first but now works for the others as well. Corel's NetWinder comes installed with Red Hat, but Debian also works well on it. I think you can pick whichever distribution you wish without worry —Editor
I saw a question in LJ January 1999 (“Best of Technical Support”) for which I can provide a suggestion. The utility sudo can be configured to provide non-root shutdown capability. sudo (su do) basically allows non-root users to execute a restricted set of commands. It essentially performs an su - root -c command but can ensure more restrictive access control and does not require you to give out the root password.
On my desktop, I configure it so that any time I want to run a root command (I log in under a regular user account called stephen), I just type sudo command, and it executes it for me without hassling me. Of course, you can configure it to require passwords, allow only a single command, etc.
More about sudo can be found at http://www.courtesan.com/sudo/.
—Stephen Thomas firstname.lastname@example.org
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
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- Google's SwiftShader Released
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