At long last, Jeff Dike's User-Mode Linux has been accepted into the 2.5 kernel tree. Now users may invoke the Linux kernel as a user process on a running system. Or to put it another way, users may invoke any number of concurrent virtual Linux systems, which may be Beowulfed together or clustered in some other way, or else used for testing new drivers and other invasive patches that can result in crashed systems. No more lengthy reboots when your new toy blows up—start another instance and keep hacking!
SGI's journaling filesystem XFS has also been accepted into the 2.5 tree, having finally met Linus Torvalds' requirements. For a long time, XFS made some fairly violent changes to areas of the kernel that Linus felt really shouldn't be touched. These have been cleaned up, and the code is in. Users desiring journaling filesystems can now choose between ext3, ReiserFS, IBM's JFS and now XFS.
Threading scalability has just made a huge jump. Now you can start 100,000 threads and run them all concurrently. This came as such a shock to kernel developers that Linus thought he misread the announcement. Ulrich Drepper and Ingo Molnar have been leading this charge, which brings threading scalability far, far above what anyone could reasonably need on a home system. Still, as one developer put it, if nothing else, this shows we're doing something right.
There is currently an ongoing debate that will have a strong impact on virtually all users. The ability to unload a given module from the kernel may be going away. Apparently, the code to handle modules has become too complicated; one proposal is that this can be simplified if modules, once loaded, are simply grafted permanently onto the running kernel. The problem with this is the ability to unload modules is seen as a really useful feature many developers want to keep. So far, the debate looks as though it could swing either way.
Some new code for handling crashes has come to light. One such is a patch to control core-dump filenames. When a program core-dumps, instead of simply producing a file in the current directory called core, it can produce a file in another directory with a name specified by the user. Another bit of code for crash handling is kksymoops, an OOPS handler that decodes the kernel symbols before dumping the OOPS. Previously, OOPS output had to be run through a separate program in order to produce data that would be meaningful to kernel developers. With kksymoops, more and better information is available. This makes it easier for users to report system crashes and easier for developers to debug them.
CheckBook Tracker tony.maro.net
If you've been waiting for a replacement for Quicken, this might be the ticket. I don't have Quicken, so I downloaded my bank files as QIF, and they imported flawlessly into CheckBook Tracker. The interface is clean, efficient and has a number of display modes. This is probably the most intuitive checkbook I've used recently. Requires: libXi, libXext, libX11, libm, libgtk, libgdk, libglib, libgdk_pixbuf, libgmodule, libdl, glibc.
—David A. Bandel
This is a simple curses-based typing practice program. It won't teach you to type (you already need to know how to do that), but it will help improve your speed, using either an xterm window or a VT. You can practice on different keyboards (QWERTY or DVORAK) and alternate hands to give either hand more practice. Requires: libncurses, glibc.
—David A. Bandel
Number of Linux-based Sicom Systems point-of-sale systems being installed in Burger Kings in Puerto Rico: 160
Number of Linux-based PDAs: 16
Billions of searches per month on Linux-based Google: 5
Millions of Linux users: 18
Position of Linux Professional Institute (LPI) on Computer Reseller News (CRN) fastest-rising certification list: 1
Position of Red Hat Certified Engineer (RHCE) on Computer Reseller News (CRN) fastest-rising certification list: 2
Percentage of retail Red Hat Linux customers who use the OS at home: 34
Percentage of retail Red Hat Linux customers who use the OS at work: 13
Percentage of retail Red Hat Linux customers who use the OS both at home and at work: 50
2001 salary in dollars of Hilary Rosen, president of the RIAA: 1,163,729
2001 salary in dollars of Jack Valenti, president of the MPAA: 1,030,000
Average payola in dollars paid by record companies to US commercial radio stations to add a song to a playlist: 1,000
Payola in dollars paid per week by the US record industry: 300,000
Amount paid by US radio stations to record companies or artists to play music: 0
Range of percentage of revenues that will be paid by small webcasters to artists via the RIAA's collection arm: 8-12
Percentage of TV commercials that don't get watched in households using the Linux-based TiVo: 88
Factor by which the cost of processing a single bit declines every 20 years: 1,000
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
- Non-Linux FOSS: Caffeine!
- SUSE LLC's SUSE Manager
- Managing Linux Using Puppet
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Parsing an RSS News Feed with a Bash Script
- Doing for User Space What We Did for Kernel Space
- Google's SwiftShader 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