From the Editor - Don't Kill Peer-to-Peer, Make It Stronger
At a recent demonstration of a network statistics tool, the presenter pointed out a bar on a chart and said that about half of the bandwidth used at the site was for a peer-to-peer (P2P) system called Kazaa.
P2P systems have enormous potential to free independent artists and Web sites from big ISP bills, sneak political information past censors and, perhaps most importantly for our readers, provide a challenging new platform to develop software ideas. But, Kazaa is proprietary, mostly unencrypted and, with a little work, can be filtered out. On page 56, Chris Lowth explains how.
Please do it. Read the article and filter your company's Kazaa users into oblivion. It's one of the projects you shouldn't have trouble convincing management to approve, because legal threats for hosting illegal copies of files on P2P systems are big news. With the techniques covered in Chris' article, you might be able to get a Linux firewall approved for a company that doesn't use Linux yet. There's always a first Linux project for every company, and this makes a good one.
However, there's another, more important reason to block Kazaa. The gap between what P2P needs to do in order to be a useful free and anonymous speech system and what Kazaa bothers to do, is shocking. If you can detect Kazaa traffic, repressive regimes certainly can. Help encourage the development of strong P2P by blocking inadequate P2P.
Ready to start working on a P2P system of your own? Brandon Wiley introduces a fundamental technique, distributed hash tables, on page 71.
And, because the theme of this issue is system administration, we cover two of the classic problems: how to design a backup plan for quick and painless restores and how to set up robust, sane file servers. Now that blank CDs are cheap, it makes sense to give each system its own custom recovery CD. Craig Swanson and Matt Lung cover Mondo for bare-metal restores on page 46. Erez Zadok lays out the problems with NFS and covers a flexible automount solution you can live with, on page 52.
After the movie industry, the next big leap for the Linux desktop is into electronic design automation (EDA). Not only are open-source EDA projects gaining features, the established EDA vendors are porting their proprietary tools to Linux as well. Michael Baxter explains how you can do hardware design almost at the speed of software with Xilinx chips and development tools on page 74.
Reuven Lerner's series on open-source content management systems for the Web continues with coverage of Bricolage on page 12. And, Eric Jeschke is back by popular demand with more GIMP techniques on page 80.
All you kernel hackers and scalability fans out there can check out page 18 where Paul McKenney explains the read-copy update (RCU) algorithm he developed at IBM and how he and other kernel hackers are making it work in the eagerly anticipated 2.6 kernel. Don't forget to download and test a 2.6 kernel with your own favorite apps and hardware. With the freedom to hack comes the responsibility to report bugs.
Don Marti is editor in chief of Linux Journal.
Practical Task Scheduling Deployment
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.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- Stunnel Security for Oracle
- The Firebird Project's Firebird Relational Database
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Google's SwiftShader Released
- SuperTuxKart 0.9.2 Released
- Doing for User Space What We Did for Kernel Space
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