Letters to the Editor
I love your high-quality magazine and look forward to each issue. Only one complaint: you've started putting a thick black border around the feature article pages. The ink sticks to my fingers and gets smudged all over the pages, making it much less appealing to read. Please get rid of the borders! I would also like Metro-X to get rid of all the black on their back page ad, which also smudges all over the place, but I guess that's another letter to be written to their marketing department. Or maybe your whole magazine is just too hot to read! Thanks.
—Walter Cooke email@example.com
We added the border to call attention to the feature section—makes it easy to find. The smudge factor did not occur to us and doesn't happen on the copies we receive. However, yours is not the only complaint we have received and we are talking to the printer about possible solutions. Perhaps we need to rethink this one. Thanks for your comments —Editor
I will be the first to admit there are no absolutes in this world, but the comment offered by Shawn McMahon in the Letters section, Linux Journal, June 1999 issue concerning PCI modems not working in Linux, is absolutely wrong. Unfortunately, your response to his letter was likewise in error, thereby perpetuating this misinformation. You stated, “PCI modems are basically Windows-only.” I realize you used a caveat in your response; however, as the (in my opinion) pre-eminent and “first-class” leader in Linux-related magazines/journals, you should do a little more research before making blanket statements that are inaccurate.
I am limiting my comments to one modem only for obvious reasons, but I must tell you that “some” PCI modems work equally well in Linux and Windows. For example, I recently installed a US Robotics/3Com V.Everything PCI modem in one of my computers, and have not experienced any problems with it whatsoever. I configured the modem to use com2 when operating in an MS Windows environment, and /dev/ttyS1 when using Linux. I connect to my ISP consistently at 48,000 bps (probably due to the antiquated wiring of our local telco) regardless of the OS I am running.
I enjoy perusing your journal immensely; in fact, I anxiously await its arrival every month. When it finally gets here, I scurry into my “library” and don't come out for an hour, much to the chagrin of the rest of the family. Kudos to all at LJ! Keep up the good work!
—Greg Bailey firstname.lastname@example.org
Sorry, everyone I talked to about Shawn's letter agreed he was right. With so much hardware available today, no one can know everything. Congratulations on finding a PCI modem that works for Linux and you —Editor
A Linux lab was constructed in December 1998 by a volunteer group of Linux users in Tucson, Arizona for Corbett Elementary school. All machines within the lab run only Linux, except for the district's server console—we were not given permission to remove Windows 95 from it, unfortunately. Even if it isn't the first Linux lab in a public school within the U.S., it's most likely the first in an elementary school (K-6). It contains 32 Compaq Pentium 90s, one AST Pentium 90 server, one 486 DX-33 Ethernet switch, one Gateway 486 DX/2-66 print server and one Compaq Pentium 200 MMX (district)—all running Slackware 3.6 and 4.0. The lab officially opened late January 1999, and the students love it. Some were having too much fun with XBill though, so we had to remove the gore. The entire district, which constitutes 105 schools, pipes out to the Net on a single T1—not everything can be perfect. On that note, I'm the network administrator for this lab.
—James Daniel email@example.com
I think your article “The Distributions Take a Stand on Standards” by Norman Jacobowitz (June 1999) does not prove a thing. No vendor in his right mind would state that they will not go along with existing and upcoming Linux standards and invent their own for “product improvements”. Not even Microsoft did so before introducing new proprietary software solutions.
At the moment, it's all about market share for a huge upcoming market and who's best in keeping up a good “front show” while thinking about how to get the biggest piece of the pie in the back office. What do you think about new software for Linux labeled as running on “Red Hat Linux”? Check out www.kai.com/C_plus_plus/download.html#intel_linux.
I think Linux needs an independent organization like the OMG for CORBA. At the moment, there is not even one “Linux Standard”. How do you explain to your customer which Linux configuration your software runs on? Some distributions know how to use this fact for their own benefit and could cause standards to go down the drain in a few years. Greetings from Germany.
—Roland Koeckel firstname.lastname@example.org
The Linux Standards Base, written about in “The Past and Future of Linux Standards” by Daniel Quinlan in that same issue, is striving to become that independent organization you are wanting —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|
- The Firebird Project's Firebird Relational Database
- Stunnel Security for Oracle
- My +1 Sword of Productivity
- SUSE LLC's SUSE Manager
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Google's SwiftShader Released
- Parsing an RSS News Feed with a Bash Script
- 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