Universities are very cost-conscious, and the relatively low expense of Intel systems combined with organic availability of Linux is quickly becoming the norm, especially at reputable engineering schools. The free availability of the source code leads universities to standardize on Linux for computer science courses.
—Billy Marshall, Red Hat
Continuing core development of version 3 is mostly paid for by Hans Reiser from money made selling licenses in addition to the GPL to companies who don't want it known that they use ReiserFS as a foundation for their proprietary product. And my lawyer asked “People pay you money for this?” Yup. Hee Hee. Life is good. If you buy ReiserFS, you can focus on your value add rather than reinventing an entire FS.
—mkreiserfs, in reiserfsprogs 3.6.5
The first discovery I'd like to present here is an algorithm for lazy evaluation of research papers. Just write whatever you want and don't cite any previous work, and indignant readers will send you references to all the papers you should have cited.
Comparing UNIX and Linux like-for-like, we found that we get two to five times the amount of throughput [messages per second] on one of the Intel boxes than on a Sun Sparc box, at half the cost.
—Casey Merkey, Global Linux Program Manager, Reuters' Market Data System
—David A. Bandel
I often have a low-priority task that takes some time running in the background, like a large FTP download. With trickle, I can manage bandwidth usage on a per-program, per-IP-address basis, so my SSH sessions are still responsive, my FTP sessions continue (albeit at a slower pace), and family members and coworkers don't get upset. Its only drawback is that you must remember to use trickle to invoke the program for which you want the traffic shaped. Requires: libevent, libnsl, libdl, glibc.
—David A. Bandel
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
- Parsing an RSS News Feed with a Bash Script
- Rogue Wave Software's Zend Server
- 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