I was pleased to see the LINUX license plate in your February 2003 issue [Letters], particularly as I have the same five letters on my car! I too was surprised to find that LINUX had not been chosen in my home state (Northern Territory, Australia). Having a LINUX license plate is certainly a talking point around town. I'd like all the owners of LINUX license plates from around the world to send a picture to LJ, along with a few words about their particular part of the world.
A few years ago, when I first subscribed to LJ, someone made a mistake and sent two copies of each issue. One was sent to me, and the other was addressed to Eric W. Sattler, which was strange because there was nobody by that name that I'd ever heard of. I laughed at it, and that was that. In 2001, when our son was born, my wife and I were having trouble coming up with a name, and we remembered Eric from Linux Journal. It sounded better than anything we had thought of on our own, so Eric it was. He'll be two years old this June, and I wanted to send this mail to thank you for helping us name our son.
In the March 2003 issue, the From the Editor column talks about community and the fear of spam people have when posting on Usenet or web forums. But there is something old that has become new. Cheap hardware and cable modems have caused a renaissance in the BBS scene, and one of the major factors in this is a GNU operating system named Linux. Why choose to eat spam when you can telnet into a friendly BBS?
Although Bolivian users held an installfest at 11,000 feet, astronomers at Mauna Kea regularly install Linux at 14,000 feet. At that height we need extra cooling, usually by placing big fans (ten inches at least) near the monitor, which seems to produce the most heat. The lower efficiency of cooling is a big problem at these altitudes; yet, Linux runs well up there too.
I find a T-shirt on the Linux Journal web site to be very offensive. The shirt has a typical Christian fish with the words “Linux Saves” inside. I'm surprised the person(s) involved with designing this T-shirt, its advertising and sale aren't offended.
I remember you used to sprinkle little tech tips, command one-liners and other useful everyday kinds of knowledge throughout your magazine. What happened to those? I found them very helpful. I wrote a script called rpmff (RPM File Finder) to search RPMs looking for a specific file and find it useful.
Look for rpmff elsewhere in this issue.
I bought two products that recently have been featured on the Linux Journal web site: a Hawking PN7127P print server [www.linuxjournal.com/article/6509] and a copy of Eric Meyer on CSS: Mastering the Language of Web Design [www.linuxjournal.com/article/6618]. Both are great. I appreciate having the articles, the reviews and even the ads. You folks have found the right balance.
I just read the article on weblogging by Doc Searls and Dave Sifry [LJ, March 2003]. Nice work. And, just to add another option for Linux, there is the Python Desktop Server (pyds.muensterland.org). It is similar in spirit to Radio Userland but runs on systems where Radio isn't available. In combination with the Python Community Server Software (pycs.net), you can get your own community server up with people participating quite fast.
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
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- Google's SwiftShader Released
- Rogue Wave Software's Zend Server
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