New Procedures for 2005 Readers' Choice Awards: Send Us Your Nominations Now
It's almost time to begin the voting process for the Linux Journal 2005 Readers' Choice Awards, and we've been listening to your comments and suggestions about how to make it work better. First of all, the big Web form is gone, and both nominations and voting will take place by e-mail this time. Don't worry, we won't spam you. But, we will take reasonable precautions to make sure there's only one vote per e-mail address. We'll simply count the last vote per address, so if you make a mistake simply send in a new version.
We require plain text e-mail for nominations and votes, so no HTML or attachments.
We're making the most important change first: the nomination process now is open to our readers. You can add nominees right at the beginning, instead of doing write-ins later on, and you even add suggested categories.
Send your nominations to email@example.com, one category and nomination per line, in category: nominee format. For example, if you want to nominate coffee for your favorite programming beverage, send us the line:
programming beverage: coffee
You can use our existing set of categories, make up your own or send some of your own and some of ours--it's up to you. The only rule is a category name cannot have a colon in the middle, because that's how we separate the category name and the nominee.
Yes, you can nominate your own project or your own company's product. Keep in mind, too, that you're more likely to get votes if you nominate a general product or project, such as Example.com NiftyServer Series or L Desktop Environment, than if you nominate the Example.com NiftyServer 4242A or LScreenShot DooDad 15.9.
Our latest list of categories is:
Linux web site:
distributed file sharing system:
web hosting service:
system administration tool:
network or server appliance:
instant messaging client:
If you want, you can cut this list and paste it into an e-mail message right now. That address again is firstname.lastname@example.org .
Category names are not case-sensitive, but nominees' are. Please capitalize your nominees' names as their official sites do.
We will consolidate category names or nominations if we feel that doing so would make voting more fair. For example, if ImageMagick's convert and mogrify both got nominated for best image-handling tool, we'd consolidate them into ImageMagick.
The categories that receive the most nominations will go on to the next round.
The nomination period closes on May 25, 2005. On May 27, we'll publish the ballot for the elimination round of voting. The categories receiving the most nominations and the top nominees in those categories will be on the ballot. Vote for your favorite in each of the categories and mail the ballot back to us. You will be able to do write-in votes at this stage.
This step is what it sounds like, the final vote. It will be like the elimination round, but only the top vote-getters from the elimination round are eligible. No write-ins votes are allowed in the final voting.
We want to hear from you, so let's see some nominations. Remember, send your nominations to email@example.com.
Don Marti is Editor in Chief of Linux Journal.
Heather Mead is Senior Editor of Linux Journal.
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
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- Google's SwiftShader Released
- Parsing an RSS News Feed with a Bash Script
- 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