Letters to the Editor
My company sells CAD software for Windows NT, we run the company on Macintoshes, and we serve our data from Linux. I was surprised how easy Linux was to get up and running.
However, once upon a time there were two UNIX tribes: the Open Software Foundation and UNIX International. Each tribe was trying to rubber-stamp UNIX for the masses. As the two camps fought, a third tribe from the Northwest called Microsoft provided business with Windows NT. Windows NT did not provide anything great; in fact, it was largely based on an operating system from Digital Equipment Corporation called VMS. The UNIX tribes had beaten this operating system years before.
Linux has a real opportunity to compete in business beyond the server. All that is needed is a single standard desktop. Forget about KDE and GNOME. Merge them, do whatever you must with them, but get a single desktop environment for which developers can write applications and users will prosper.
I am convinced Windows NT cannot serve my business. Unfortunately, until Linux provides a common desktop, Apple's OS X may be the only way to finally bring the power of UNIX to the business user.
—Jeff Millard President, SolidVision, Inc. firstname.lastname@example.org
I am writing in regards to the article “Linux Certification for the Software Professional” by P. Tobin McGinnis in LJ April 1999. First, I have been working with PCs since I got my first Apple back in the early 80s. When I went to college, I started using the x86 platform. After finishing my college degree, the Air Force sent me to Keesler AFB to teach computers to new recruits. There I first heard the word “certification” in regards to Novell's CNE program. We were teaching Novell 4.x to our students. People started talking about Novell certification, and of how much one could make if they had this certification. A couple of years later, I was working as a contractor for the Corp of Engineers in Mobile, AL on a team that went to field sites to convert Novell servers to NT. Once again, I heard the certification buzzword, this time from Microsoft, and the buzz of big money if one had the MCSE certification.
People began to scramble to get certified at great cost to themselves—$100 US per test, $50 US per book, and in some cases, thousands of dollars for classes. Now, many of the questions and answers for these certification tests can be found on the Web. People are passing the test who have never installed the NT OS. Yet because they are certified, they are called experts—their certificate is meaningless.
Now I read in Linux Journal the buzz about Linux certification. I thought Linux was better than that. Certification has always been a way for companies to market their products. The training companies are the only ones getting rich from certification. Linux has grown exponentially without certification. I am against certification.
Please don't promote Linux certification. It will ruin the Linux movement. The movement was created by people who rebelled against the likes of MS, Novell and many other companies. Now it seems we are running to join their ranks with the same certification nonsense.
—Kyle Enlow email@example.com
I am writing this after reading the article “Linux in a Public High School” by Andrew Feinberg in your March issue. I am currently one of two system administrators at Bridges Academy, located in Los Angeles, California. My associate, Brook Elliot, and I run a Debian 2.0 box with the 2.0.36 kernel. The Linux box runs on a T1 line, and using DHCP, we enable students to plug in to any of the Ethernet jacks around the school and check their e-mail or browse the Web. Although most of these students are using Windows 9x machines, a select few of us use the full Linux potential.
Both Brook and I are students at this school. We currently have a web page up for the school at http://www.bridges.edu/, which runs under Apache.
—Matthew Kaufman xel@Bridges.Edu
Many years ago, Byte magazine was a technically oriented magazine that I enjoyed reading as I enjoyed reading the December issue of Linux Journal. Early last year, Byte was publishing fluff. I hope the March 1999 issue of Linux Journal is not an indication of more fluff to come. With the exception of the GNU gettext article, where are the items that show a reader how to use a Linux system in a new or more productive way, to use a new programming library, to reduce incoming spam, etc.? One or two articles on interesting uses of Linux is fine (such as “Linux for the International Space Station Program” by Guillermo Ortega), but please don't go the way of Byte.
—Richard Film. Unix. Mirkwood@disney.com
I wouldn't call discussions of Internationalization “fluff” myself, but everyone has his own opinion. As always, we try to remain as balanced as possible between technical and non-technical articles. I hope April and May were more to your liking —Editor
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