- LJ Index, April 2006
- They Said It
- diff -u: What's New in Kernel Development
- On the Web
- Redraw Your Own Conclusions
LJ Index, April 2006
1. Billions of Internet users: 1
2. Number of computers on the Internet in the US in 1969: 2
3. Number of years it took for the Internet to reach its first billion users: 36
4. Estimated year when 2 billion will be reached: 2015
5. Estimated year when 3 billion will be reached: 2040
6. Annualized percentage growth rate in Internet use: 18
7. US percentage of Internet users in 1995: 66
8. US percentage of Internet users in 2005: 23
9. Position of South Korea in broadband penetration: 1
10. Position of China among Internet users under age 30: 1
11. Millions of Firefox downloads by October 2005: 100
12. Minimum Firefox market share in November 2005: 10
13. Number of Netcraft's ten most reliable hosts using Linux: 3
14. Number of Netcraft's ten most reliable hosts using an open-source OS: 7
15. Position of Hostway, which runs Linux, among most reliable hosts: 1
16. Position of Apache among most popular Web servers: 1
17. Apache percentage of all Web servers: 70.98
18. Millions of Weblogs as of January 4, 2006: 24.4
19. Thousands of new Weblogs added each day: 70
20. Thousands of Weblog posts created per hour: 33
1–7: Jakob Nielsen, Useit.com
8–12, Mary Meeker, Morgan Stanley
13–17: Netcraft.com, December 2005 reports
18–20: Technorati data from January 2006 and November 2005
They Said It
Ask the network before you ask the source.
—Jeremie Miller, from an IM with me
...consider this a warning shot for anyone who is relying on closed source modules. What you are doing is trying to take from Linux and not give anything back. The GPL explicitly forbids this, and Linux would not be good enough today for you to be using it without that protection. There is a reason why you are wanting to use Linux for your internal use, and why your customers are asking for it.
—Greg Kroah-Hartman, remarking about his proposed kernel patch that “simply marks all PCI functions as only able to be used by GPL licensed kernel code” (www.kroah.com/log/2005/11/21#gpl_pci_core)
diff -u: What's New in Kernel Development
John W. Linville has announced a new git repository for his fork of the Fedora Core kernels. This repository will take the Fedora kernel releases as its base, and incorporate networking patches from the official kernels on kernel.org. His goals are to allow Fedora users to access bleeding-edge patches they otherwise would have to wait for and to convert the Fedora user community into a testing resource for the kernel (specifically networking) developers.
Eric Dean Moore has assumed maintainership of the previously unlisted LSI Logic MPT Fusion SCSI Drivers. These drivers were split recently from a single driver supporting SCSI and Fibre Channel to multiple drivers each supporting a single interface. The irony of this is that although the developers themselves chose to split the driver this way, the MPT Fusion's main claim to fame is that it provides a single interface to both SCSI and Fibre Channel hardware.
Alessandro Di Marco has begun work on Sluggard, a filesystem intended to make kernel downloads less painful. As the kernel sources continue to grow, it takes longer to download. Sluggard addresses this by putting rsync at its back end. Users read files on the filesystem with their favorite tools, and Sluggard transparently fetches any changed files just prior to access. In this way, files that aren't needed are never downloaded. This has saved Alessandro more than 200MB of disk space, and he says the potential exists to save even more, depending on what kernel features one needs to compile.
Andrey Volkov has coded up support for the ST M41T85 real-time clock chip, basing his work on Mark A. Greer's ST M41T00 driver. In fact, there is some talk of merging Andrey's work into Mark's original driver. However, due to many small differences in the hardware, it's not clear what the best approach would be to avoid too many #if statements. It may turn out that merging the two would create more complexity than a unified driver would be worth. But, both Andrey and Mark have indicated that they'd be happy to do a merge if it seemed like the right way to go.
Since Sun released its ZFS filesystem source code, Tarkan Erimer recently asked if this meant it might be ported to Linux at some point in the future. However, this doesn't seem likely, because Sun used the CDDL license, which allows linking to other code released under nonfree licenses, thus making it incompatible with the GPL. Unless Sun decides to dual-license ZFS under CDDL and the GPL, there is no way a direct port of ZFS to Linux could be legally included in the official tree. It is still possible that someone will do a clean-room reimplementation of ZFS, without looking at any of Sun's sources.
If Linus Torvalds' stance on CVS was not clear before, it is now. When it was suggested that the kernel include documentation about existing CVS-based kernel repositories, Linus said, “I'd argue against it. CVS is a piece of crap, and anybody who maintains stuff in CVS just makes it harder to ever merge back. That's not just a theory—we've had that situation happen in real life over the years, which is why I definitely don't want to see any external CVS trees given any kind of recognition at all.” There you have it.
One of the strengths of the Linux development philosophy is that it won't blindly adhere to standards just because those standards exist. The standards have to make sense as well, and in the case where a good standard has not been followed for some reason, it has to make practical sense to change into conformance with it. This came up recently when Matthew Wilcox tried to fix the NO_IRQ definition to bring it into conformance with the PCI standard. Linus pointed out that the standard had been ignored by hardware makers for years, and that changing the NO_IRQ definition would break a lot of existing drivers. In fact, the Linux kernel would be clearer and simpler if some change were made to at least bring the various kernel architectures into conformance with each other; and if all drivers could be fixed to reflect this change, it would be the right thing to do. However, Linus rejected that proposal, affirming that the existing design was a mistake, but saying that the fix would break too much outside code.
On the Web
Need some advice on figuring out the best way to get the most out of OpenOffice.org? Now that the 2.0 versions are available, more and more people are using this free office suite. You can find your way around OOo well enough if you're moving from another suite, but you'll definitely be more productive with some OOo know-how under your belt. That's where LJ.com columnist Bruce Byfield comes in, with his bi-monthly series OOo Off the Wall. Recent topics include:
Find and Replace (www.linuxjournal.com/article/8791): how to search for and replace text and strings.
Master Documents (www.linuxjournal.com/article/8735): how to create and manage large documents comprised of smaller OOo files.
Domesticating AutoCorrect (www.linuxjournal.com/article/8688): how to set up the AutoCorrect feature so it doesn't drive you crazy—and how to turn it off altogether.
And, for an overview of “What New Users Need to Know about OpenOffice.org” (www.linuxjournal.com/article/8443), Bruce offers advice on on-line help, interface workings, templates and other OOo particulars. In coming months, Bruce will be moving on to Calc, OOo's spreadsheet program.
Regular contributor Colin McGregor is working on a new how-to article for LJ.com readers about the Linux Infrared Remote Control (LIRC) Project (www.linuxjournal.com/article/8811). He'll explain what it is, what hardware/software is needed and how to set up the software. For those of you feeling more adventuresome, Colin also will share some thoughts on building your own infrared hardware.
Redraw Your Own Conclusions
Back in July 2001, I had fun looking up Google search results for a bunch of different terms, and listed them in the October 2001 issue of the magazine.
So, we revisited those same items for this issue. Here are the results.
|Term||July 2001||January 2006|
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|
- The Firebird Project's Firebird Relational Database
- Stunnel Security for Oracle
- My +1 Sword of Productivity
- SUSE LLC's SUSE Manager
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Parsing an RSS News Feed with a Bash Script
- Google's SwiftShader 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