Letters to the Editor
This is a story about how Linux helped in Saving Private Ryan. I thought your readers might be interested in how Linux supported the National D-Day Memorial Foundation both very inexpensively and reliably.
A friend, James Ervin, and I had been involved in the installation of our local Internet access through the cable TV company, Bedford Cablevision, as well as the installation of Linux for web servers, mail servers and firewalls. In Bedford, Virginia, where we live is a small organization called the National D-Day Memorial Foundation. We set up a web presence for them on the Internet with the cable company's help. We put together a computer (an AMD 5x86-based server) for about $350 and installed Linux for a firewall, web and mail server. They had some web pages donated by a graphics design shop, Howlin' Dog Designs. The day after the cable company installed the cable and cable modem, the pages were up on the Internet on their own server. Initial requests for web pages (http://www.dday.org/) were few, about 2000 per month.
A while later, they were contacted by a company called DreamWorks which wanted to do a movie related to D-Day. Support was provided by the Foundation to DreamWorks and eventually the movie was released. Their web traffic then increased to about 2000 requests per day, and Linux has faithfully borne the load. That is the story of how Linux worked behind the scenes during the making of Saving Private Ryan.
—Rich Kochendar email@example.com
I just finished setting up an extra PC as my new router to the Internet. I used the instructions from the article “Getting in the Fast Lane” by Michael Hughes in the June 1998 issue (#50), and although I used a regular modem instead of a cable modem, I was able to connect to the Internet within hours of playing with the kernel and ipfwadm. I must say I was excited to get it working and especially to browse my PC web site from the Internet using the DHCP address from my ISP. I even sent this e-mail from one of the PCs on my internal network. Keep up the good work, guys.
—Danny M. firstname.lastname@example.org
I just wanted to write and let everyone know that Red Hat 5.1 is excellent! From start to finish, the installation was seamless. I recommend novice users buy the boxed version made by Red Hat; it comes with e-mail support, a nice book, a boot disk and a set of three CDs. Not bad for $54.99; the book included is worth that price if you are a novice. Now that I have migrated to Linux, I find myself chanting “Cool, It Works with Linux!”
—Michael T. McGurty email@example.com
I was in total shock when I read the Editor's remarks “How Many Distributions?” in the September 1998 issue of Linux Journal. It seems to me to be the most anti-Linux message I have ever read. What gives you the right to tell the Linux community what is good for it? Isn't that why we don't like Bill Gates? He feels like he should lead the computer industry in the direction he sees fit.
What would have happened if someone had told Red Hat there were too many distributions? What if someone had told Linus Torvalds there were already too many x86 UNIX kernels? After all, BSD, Minix, SCO and Solaris (x86) already existed.
If someone wants to start up a new distribution, my hat is off to them. It's much harder to start up a distribution today and have it succeed than it was just two or three years ago. This is partly due to how great the current distributions are. If a new distribution has binary compatibility problems, no one will want to use it. This should encourage them to make sure their distribution complies with the Filesystem and Binary Compatibility Standards that have been proposed.
Linux is about individuality. I prefer Red Hat, FVWM 1.X and vi. Why should I use Caldera, KDE and Emacs? Too many people are caught up in Red Hat vs. Caldera, KDE vs. Gnome, vi vs. Emacs. Who cares? They all work with Linux! That's what is so great about it all. I can have an operating system tailored to me. People who enjoy Linux should express themselves in whatever manner they like, whether it's creating a new distribution or creating a new resources page.
Maybe I'll express myself by creating a new Linux magazine. I understand there's quite a monopoly in that area.
—Pete Elton firstname.lastname@example.org
The purpose of that column was to express my opinion, not to dictate to the Linux community.
Actually, we do have competitors—in Germany, Spain, Korea and Japan. I've also heard rumors of Linux magazines in Italy and India —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!
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Tech Tip: Really Simple HTTP Server with Python
- Doing for User Space What We Did for Kernel Space
- Rogue Wave Software's Zend Server
- Parsing an RSS News Feed with a Bash Script
- SuperTuxKart 0.9.2 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