Advertisement
Interested in hardware, diags, validation, Linux, C, ARM, Microcode and low level programming and blazing networks?
LWN Weekly Edition
Leading itemsSecurity
Kernel development
Distributions
Development
Linux in the news
Announcements
Letters to the editor
->Multipage format
This page
Previous weekFollowing week
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
LWN.net Weekly Edition for January 4, 2007Looking forward to 2007Predictions, as they say, are hard - especially when they involve the future. It's easy to get them wrong and look like a total fool. Your editor, however, has long since gotten over his fear of coming across as a total idiot in front of large numbers of people; when you have already tipped your hand, there is no point in holding back any longer. So here's a few things which, in your editor's view, might just come to pass in 2007. As always, these predictions come with no warranty whatsoever.
Legal issuesVersion 3 of the GPL will be adopted, perhaps after one more draft round. Your editor has no clue of how the FSF will respond to the criticisms of their anti-DRM provisions. If that language remains, uptake of the new license will be somewhat lower; the FSF may try to avoid that scenario by making "distribution on restrictive hardware without the associated keys" an optional permission which can be granted by the copyright holders. Somebody will be sued for distributing proprietary kernel modules. Threats of lawsuits have been muttered for some time, but the late-2006 discussion on banning those modules made it clear that GPL infringement suits are the strongest weapon available to those who oppose proprietary modules. Given the way the frustration level is rising, it is only a matter of time until somebody uses that weapon. We will see the end of SCO in 2007. Chances are that the company's case against IBM will not even survive until the planned trial date in the (northern hemisphere) fall. Look for fun around March, when dispositive motions can be heard. There will be serious talk of patent reform in the U.S. The EFF is unlikely to succeed in its attempt to get the U.S. Supreme Court to throw out patents on software altogether; the current chief justice places a heavy emphasis on deciding no more than the current case requires, and software patents are not at issue in that case. But the pain caused by these patents is severe and growing; something will eventually have to be done. Whether that "something" will help to lift the clouds of legal uncertainty from free software remains to be seen, however.
DevelopmentLinux will have fewer problems with closed hardware one year from now. There is already a clear path to support for most wireless network adapters. On the video front, a palpable determination to address the problem has come together over the last year. The Nouveau project can be expected to make significant progress over the next twelve months, and developers are beginning to talk about a project to support ATI's R500 engine. A decision by AMD to open up ATI's hardware would be a nice bonus. But, either way, the need to solve this problem is well understood, and developers are increasingly interested in attacking it. Closed hardware problems will not go away, however. The content industry, with Microsoft's help, is pushing for a new generation of hardware which is intended to be "trusted" not to give too much control to its owner. "Trusted content paths" are fundamentally incompatible with free software. So we will continue to have trouble in carrying out straightforward tasks - like watching movies - on our free systems until the industry comes to its senses. The war on bloat will get serious as people get tired of running out of memory. The increasing use of Linux on small and embedded systems will also create pressure for lower resource usage. Tools are emerging which will help developers track down wasted memory; their employment should lead to leaner systems for all of us. The previous item notwithstanding, Java will move into the free software community as Sun follows through on its promised code releases. Thus far, the amount of free software written in Java has been relatively small. Once free Java support is available for all Linux systems, the number of developers of free Java code can be expected to grow. Fedora will come into its own as a free, community-oriented distribution. Fedora's transition from a corporate product into a community product has been slow at best, and it is far from complete. The right things are happening, however; the combination of a more open process, a 100% free software policy, and a high-quality base should lead to good things. Debian will get the Etch release out this year. Honest. What could possibly go wrong? Thereafter, the Debian developers will go back to arguing about firmware in the kernel. Free software will move into online gaming as a critical mass of interested developers comes together. Many of the necessary pieces exist now as free software, and the possibility of acquiring some cast-off corporate code still exists. Meanwhile, Second Life has shown the possibilities inherent in hackable online platforms. These environments are too much fun - and too much a part of our future - to leave to the proprietary software companies.
CommerceThe Microsoft/Novell deal will blow over with few consequences. Most of the angry ink has already been spilled, and it still seems unlikely that Microsoft will launch a patent attack against Linux. Novell will have lost credibility in the community, and may yet lose more developers, but it has not really changed the nature of the patent threat. The "open source" term will take a beating as various semi-open companies try to look like free software operations. Some companies have already needed to be told to take the "open source" label off their code; others will certainly follow. The need felt by these companies to attach non-free provisions to their licenses may lead to the creation of a "shared-source"-like replacement term by the end of the year. The first round of OLPC systems will be distributed to millions of children in the developing world. That much can be predicted by looking at the project's timeline. Much harder to predict is what will happen when millions of children learn to use systems which are open, Linux-powered, and network-connected. This project may well change the free software community - and the world as a whole. Desktop Linux will grow as corporate managers realize they already have more desktop systems deployed than they had thought. As always, these predictions will be reviewed in December of this year.
Trademarking the snakeA quick search shows that there are almost 200 trademarked terms in the U.S. using the term "Python." This name has been reserved for use with lacrosse sticks, bungee cords, musical instruments, tape libraries, arc welding torches, radio-controlled toys, wire rope, motorcycle exhaust systems, perfumes, cryogenic pipes, floor polishers, carbonated beverages, "providing online adult entertainment by means of a global computer network," orthodontic adhesive, herbicides, garage door openers, and much more. There is also a registration for a programming language. The term "Python," in this context, belongs to the Python Software Foundation (PSF), and has since early 2004.In November, the PSF announced the adoption of a formal policy for the use of the Python trademark. This policy has version 1.2.2, despite being the first posted policy for the use of this name. The rules disallow calling any other language "Python," so it's no fair slipping in a Perl interpreter; they also forbid using the term "in ways that confuse the community as to whether the Python programming language is open source and free to use." One clause regarding how the term "Python" can be used has attracted a small amount of attention in the Debian community, however. It reads:
Use of the word "Python" when redistributing the Python programming
language as part of a freely distributed application -- Allowed. If
the standard version of the Python programming language is
modified, this should be clearly indicated. For commercial
distributions, contact the PSF for permission.
This rule would appear to take in commercial Linux distributors, all of whom should, from a strict reading, be getting permission from the Foundation. Debian, as a non-commercial distributor, should not be directly affected by this language, but anybody who redistributes Debian on a commercial basis could be. The question which comes up is: what uses of the word "Python" fall under this policy? Is providing a python command sufficient? How about in the introductory text printed when python is run interactively? Does listing Python in an online package database count? Can the release notes brag about the version of Python shipped? How about running a "now includes Python 3000" Superbowl advertisement? The final case is covered by a separate term which forbids the use of "Python" in advertisements without prior permission. But the real location of the line separating free use from that which requires permission is not entirely clear. At this time, there would appear to be little cause for concern; the PSF has little interest in harassing people who are using or distributing its code. After inquiring with the PSF, your editor was told that the policy was created as part of the legal requirement that trademarks be enforced if the holder wants to keep them. The PSF has not seen any misuses of the name that it felt the need to crack down on, and it does not feel that noting the inclusion of Python within a commercial product necessarily requires permission. Noting that a product contains Python is acceptable in just about any circumstances. The PSF wants to promote the use and development of Python; it appears to be uninterested in legal silliness. That said, there are a couple of things which should be kept in mind here:
The number of free software projects with trademarks and associated policies would appear to be growing. The issues surrounding the Firefox trademark have been well discussed here and elsewhere. Xen has a trademark policy which is quite strict on whether a distributor can claim to ship Xen; see the Xen trademark FAQ for a view of their approach to trademark management. There are trademark policies for Perl, MySQL, GNOME, and, of course, Linux. The KDE and OpenOffice.org trademarks have been registered, but there does not appear to be a posted policy for their use. Fortunately, an attempt by Unipress to trademark "emacs" was not successful. In recent times, there has been some concern over license proliferation, resulting in a determined effort to reduce the number of free software licenses in active use. It makes sense; every software license brings its own set of conditions and interactions to worry about. Every trademark license is unique, however; each one has its own set of quirks, any of which can be changed at any time with no public participation or notification. The continuation of this trend could lead to an increasing series of hassles for distributors; the long-term result could be more software shipped under iceweasel-like names. It would be nice if free software projects would stop worrying about trademarks and get back to working on the code. Abuses of free project names have been few and far between. This outcome seems unlikely, however. Nobody likes to see their chosen name hijacked, and commercial organizations can be positively paranoid about the idea. So a more realistic solution might be the creation of some sort of standardized free trademark license. A known set of trademark terms, the same for each mark and drafted with an eye toward keeping the associated software free, could do much to make life easier for software distributors. It seems like a better alternative than being neck-deep in iceweasels.
No free Ryzom; what next?One month ago, LWN looked at the Free Ryzom Campaign, which was trying to raise enough money to buy (and free) the source to the Ryzom game in bankruptcy court. The Free Software Foundation got into the game (so to speak) with a $60,000 pledge. On December 21, however, the bad news was posted: another bidder had come in with a better offer. The campaign was left with a pile of pledges and nothing to buy.Whenever a project gets that sort of energy and resources together, it is a shame to just let it all fade away. So the campaign organizers have been discussing possibilities for achieving their goal by other means. One of the immediate outcomes is the creation of the Virtual Citizenship Assocation, which is essentially the Ryzom campaign with the brand names removed. The organization is still soliciting pledges on the chance that the source for an interesting game may come available from somewhere else. One expects, however, that the number of pledges is unlikely to grow quickly until prospective donors can see what the organizers would like to buy. There is a real chance that a game platform could be obtained this way. The history of free software projects starting with freed corporate code is long; Mozilla, OpenOffice.org, and InterBase are just some of the more prominent examples. The online gaming market is tough, with many failed offerings. Perhaps one of those proprietary failures could yet be turned into a free software success. Beyond that, the possibility of an open-source Second Life is still real. The history of corporate code offers other lessons, though; among them is the fact that such code can often require a great deal of work. Mozilla treaded water for some time until it decided to simply toss much of its Netscape legacy and start over. It would be a shame to put a large pile of donated money into a code base which, in the end, needs to be thrown out and rewritten properly. It might be better to just start over from the beginning and do it right. Except that starting from the beginning would not be necessary. The NeL library - the engine at the core of Ryzom - is already free software. Arkhart is a project to develop a GPL-licensed engine and game. The Planeshift engine is also free software - though the associated artwork is not. The WorldForge project has been working in this area for a long time. Other interesting projects exist as well. There are a couple of conclusions to be drawn from this situation. The first is that we do have the interest - and the ability - to create game engines which can implement compelling virtual worlds. The code and the developers are out there; we don't have to buy that code from a failing company. The other side of the coin, however, is that code is only part of the problem. Top-quality online games need top-quality artwork, sound effects, music, storylines, and more. If our community is going to create a great online virtual world, we must do a better job of soliciting and integrating contributions from artists, writers, and others who are not software developers. Without them, all we have is a pile of code. So there are a number of challenges to the creation of truly successful, completely free online worlds. But our community has always been good at overcoming challenges. This one, too, will fall, and we will, eventually, have our free online worlds. Your editor's kids think it can't happen too soon.
Security A Firefox PDF plugin XSS vulnerabilityA particularly nasty cross-site scripting (XSS) vulnerability has surfaced that impacts Firefox users who have installed the Adobe Reader (Acrobat/PDF) plugin. Proof of concept exploits have been published on Bugtraq as well as several blogs (here for example). Adobe has fixed the problem in Acrobat version 8; which is only available for Windows, no word yet on a fix for the Linux plugin (which is based on Acrobat version 7). The technique was first disclosed last week at the 23rd Chaos Communication Congress by Stefano Di Paola and Giorgio Fedon in their Subverting AJAX presentation. Sven Vetsch discovered another wrinkle and publicized it on his blog. The crux of the vulnerability is a link with a URL of the following form:
http://host/path/to/file.pdf#anystring=javascript:malicious_code_here
The host and path to file are legitimate URL paths to a PDF file that is
hosted somewhere on the net, quite possibly at a site that is trusted
by the user. The attacker need not have any access to the PDF file,
but can have his code executed while appearing to be a simple download from
the affected site. It is the ability to turn any PDF hosted on any site
into an XSS attack that makes this vulnerability so insidious.
The vulnerability exploits a feature of the Adobe plugin that is not shared with other mechanisms for viewing PDFs from the web (including using the acroread external program that is also supplied by Adobe). Arguments can be passed to the plugin via the information after the '#' and can be used to specify a specific page or search string in the PDF. It can also be used to populate PDF forms using '#FDF=URL' arguments and the information for the forms is retrieved from the URL. Evidently Adobe does not check for FDF or two other similar argument types (which is why 'anystring=' works) and blindly asks the browser to fetch the URL specified. If the URL is javascript code as described above, the plugin does not detect that case and in effect forces the browser to execute it. Any site hosting a PDF file is vulnerable and there is little that the site can do; there is no indication that the request is anything out of the ordinary because the string after the '#' is not passed as part of the request. Concerned sites could stop hosting PDF files, but that seems rather unlikely. Other server-side solutions are being discussed as there is a concern that users are unlikely to upgrade their browser plugins. Hosting sites would much rather that they be in control of whether their PDF files can appear in links with malicious content. Most XSS problems can be handled by proper server side filtering of user supplied content, but this particular vulnerability is different. So far there are no reports of other PDF plugins that follow Adobe's lead in retrieving URLs that appear in links to PDF files. In this author's experience, PDF viewing utilities are separate programs that get invoked by the browser after it downloads a PDF file. For xpdf and kpdf (and presumably others), this works just fine but Adobe chose to provide a means of more closely integrating PDF viewing into the browser. Unfortunately, the fact that this plugin is closed source implies that users, especially Linux users, must wait for Adobe to fix the problem. We cannot fix it ourselves. One could certainly imagine a similar mistake being made by one of the other PDF viewer development teams; Adobe is hardly alone in making bad choices in developing software. However, the fix for an open source PDF viewer would likely be available within hours of the report. Adobe was notified about this problem on 15 October according to the advisory, but there is still no fix for Linux. Disabling the plugin would seem to be prudent. Fixing the affected software is just the start of the task of fixing the overall problem. As mentioned above, users are not particularly good at picking up security fixes even when they know about them. Getting the message out on this particular problem is a big hurdle. The alternative is to educate users so that they can recognize maliciously crafted links to PDFs and that is almost certainly a harder task. The potential for a widespread outbreak exploiting this vulnerability is fairly high and this will probably not be the last we will hear about it. It certainly has the possibility of damaging the reputation of PDF amongst even casual web users and that is probably keeping some folks at Adobe awake at nights.
New vulnerabilities cacti: multiple vulnerabilities
denyhosts: denial of service
elog: multiple vulnerabilities
mono: source disclosure attack
openser: buffer overflow
w3m: denial of service
Updated vulnerabilities apache: cross-site scripting
apache-mod_auth_kerb: off-by-one error
bind: denial of service
bugzilla: multiple vulnerabilities
busybox: insecure password generation
bzip2: race condition and infinite loop
cpio: arbitrary code execution
vixie-cron: privilege escalation
cscope: buffer overflows
cscope: buffer overflows
Cyrus-SASL: DIGEST-MD5 Pre-Authentication Denial of Service
dbus: denial of service
dovecot: index cache file handling error
elinks: arbitrary file access
ffmpeg: buffer overflows
Mozilla stuff: multiple vulnerabilities
freeradius: several vulnerabilities
freetype: integer overflows
ftpd: privilege escalation
gcc: file overwrite vulnerability
gdb: buffer overflow
gdm: improper file permissions
gedit: format string vulnerability
gnupg: stack overwrite
grip: buffer overflow
gv: stack-based buffer overflow
gzip: multiple vulnerabilities
gzip: arbitrary command execution
imagemagick: buffer overflows
ImageMagick: buffer overflows
imlib2: arbitrary code execution
kdegraphics: stack overflow
kdelibs: integer overflow
kdelibs: kate backup file permission leak
kernel: denial of service
kernel: bridging code buffer overflow
kernel: denial of service
kernel: denial of service
kernel: denial of service by memory consumption
kernel: denial of service
kernel: denial of service
koffice: integer overflow
krb5: local privilege escalation
libgadu: memory alignment bug
libgd2: denial of service
libgsf: heap buffer overflow
libmodplug: boundary errors
libpng: buffer overflow
libpng: heap based buffer overflow
libtiff: buffer overflow
libvncserver: authentication bypass
libxml2 - arbitrary code execution
libxml2: multiple buffer overflows
linux-restricted-modules: nVidia driver vulnerability
lynx: arbitrary command execution
mysql: format string bug
MySQL: privilege violations
MySQL: logging bypass
nbd: arbitrary code execution
openldap: security bypass
openoffice.org: several vulnerabilities
OpenSSH: denial of service
openssh: privilege separation issue
openssh: remote denial of service
php: several vulnerabilities
php: buffer overflows
phpbb2: missing input sanitizing
phpbb2: multiple vulnerabilities
postgresql: SQL injection
proftpd: denial of service
proftpd: stack-based buffer overflow
quake: buffer overflow
rpm: arbitrary code execution
shadow-utils: mailbox creation vulnerability
squirrelmail: multiple cross-site scripting vulnerabilities
unzip: long file name buffer overflow
virusscan: DT_RPATH vulnerability
w3c-libwww: possible stack overflow
xine-lib: buffer overflow
xine-lib: buffer overflow
xine-ui: format string vulnerabilities
xinit: race condition
X.org: local privilege escalations
X.Org: buffer overflow
xpdf: buffer overflow
Page editor: Jonathan Corbet Kernel development Brief items Kernel release statusThe current 2.6 prepatch is 2.6.20-rc3, released by Linus just before he went out to celebrate the new year. It contains the fix for the file corruption bug (see below) and a few hundred other fixes.Previously, 2.6.20-rc2 was released on December 23 with another big set of fixes. Just a few patches have been added to the mainline git repository since -rc3 came out. There are currently six entries in the known unfixed regressions list maintained by Adrian Bunk. The current -mm tree is 2.6.20-rc2-mm1. Recent changes to -mm include a new version of the user-space drivers patch, more paravirtualization hooks, a generic time implementation for x86_64, and a generic GPIO driver core. For older kernels: 2.6.16.37 was released on December 28 with a long list of fixes. 2.4.34 came out on December 28. It has a number of security fixes and support for the gcc 4.x compilers.
Kernel development news Quote of the week
I don't care much, really. But then, I understand how all this
stuff works. Try explaining to someone the relationship between
pte-dirtiness, page-dirtiness, radix-tree-dirtiness and
buffer_head-dirtiness.
Device resource managementWriting device drivers can be a tricky task. Simply getting a piece of hardware to operate as desired - perhaps working from erroneous or nonexistent documentation - can be a frustrating process. Beyond that, however, the driver must allocate several different types of resources for the device; these resources can include I/O memory mappings, interrupt lines, blocks of memory, DMA buffers, registrations with multiple subsystems, etc. All of these allocations must be returned to the system when the device (or its driver) goes away. It is not uncommon for driver writers to forget to deallocate something, leading to resource leaks.The problem can get worse, however, in the face of initialization errors. If the driver is unable to properly set up its device, it must undo any registrations which had been done up to the point of failure. Attempts to handle initialization failures usually take the form of several goto labels within the initialization function or some sort of global "initialization state" variable describing where cleanup should begin. Either way, these paths tend not to be well tested, so the chances of an initialization failure leading to some sort of resource leak are quite good. Tejun Heo, who has done much to improve the Linux serial ATA subsystem over the last year, has had enough of these sorts of initialization problems. So he has put together a device resource management patch which, if accepted, has the potential to make driver code simpler and more robust. The core idea is simple: every time a driver allocates a resource, the management code remembers the allocation and any information needed to free that allocation. When the driver disconnects from the device, all of the remembered allocations are returned to the system. This sort of allocation tracking cannot be added to the current API in any sort of coherent way. Tejun's patch, instead, creates new "managed" versions of various allocation functions. The new functions look like the old ones with (1) the addition of "m" (or "devm") to the name, and (2) a struct device argument if the function did not already have one. So, for example, the managed versions of the interrupt allocation functions are:
int devm_request_irq(struct device *dev, unsigned int irq,
irq_handler_t handler, unsigned long irqflags,
const char *devname, void *dev_id);
void devm_free_irq(struct device *dev, unsigned int irq,
void *dev_id);
The patch also includes managed functions for dealing with DMA buffers, I/O memory regions, plain memory allocations, and PCI device setup. They allow the driver author to replace a whole set of deallocation calls with a simple call to devres_release_all(), simplifying the code significantly. In fact, even that call is unnecessary; the driver core will call it when the driver detaches from the device. For more complicated situations, there is also a "group" concept. Groups can be thought of as markers in the stream of allocations associated with a given device. The allocations performed within a specific group can be rolled back without affecting any others. In brief, the group API is:
void *devres_open_group(struct device *dev, void *id, gfp_t gfp);
void devres_close_group(struct device *dev, void *id);
void devres_remove_group(struct device *dev, void *id);
int devres_release_group(struct device *dev, void *id);
A call to devres_open_group() will create a new group for the given device, identified by the id value. Any allocations performed thereafter will be considered to be a part of that group until devres_close_group() is called. If initialization works as desired, however, devres_remove_group() can be used to get rid of the group overhead while leaving the allocations (and their tracking information) untouched. In the failure path, devres_release_group() will return all allocations belonging to the given group. There has been very little discussion of this patch set, as of this writing. Driver writers, perhaps, are still recovering from the holiday festivities. It is not too hard to imagine that there could be some discomfort about the extra overhead involved in tracking all of those allocations - especially since things do function normally almost all of the time. In the end, however, the promise of correct operation in a wider range of situations may be enough to motivate the inclusion of the new interface.
A nasty file corruption bug - fixedThe December 20 LWN Kernel Page contained an article about a file corruption bug generally (but not exclusively) seen with ext3 filesystems. Certain applications which have unusual patterns of access to memory-mapped files could, at times, see gaps where data had not made it all the way to the disk. The rtorrent tool was one such application; other test cases were found (and developed) as the hunt for this problem intensified. The problem is now solved, but it offers some interesting lessons on how this kind of subtle bug can come about - and how to get it fixed.
There are a couple of different kernel data structures which contain information about this page, making the diagram a bit more complicated:
The page may be mapped into one or more process address spaces. For each such mapping, there will be a page table entry (PTE) which performs the translation between the user-space virtual address and the physical address where the page actually lives. There is also some other information in the PTE, including a "dirty" bit. When the application modifies the page, the processor will set the dirty bit, allowing the operating system to respond by (for example) writing the page back to its backing store. Note that, if there are multiple PTEs pointing to a single page, they may well disagree on whether the page is dirty or not. The only way to know for sure is to scan all existing PTEs and see if any of them are marked dirty. The kernel maintains a separate data structure known as the system memory map; it contains one struct page for every physical page known to exist. This structure contains a number of interesting bits of information, including a pointer to the page's backing store (if any), a data structure allowing the associated PTEs to be found relatively easily, and a set of page flags. One of those flags is a dirty bit - another flag which notes that the page is in need of writing to its backing store. (For those following closely, it may be worth pointing out that the red arrow pointing to the page does not actually exist as a pointer field; it is implicit in the structure's position within the memory map). Finally, there is another set of structures which may be associated with this page:
The "buffer head" (or "bh") goes back to the earliest days of Linux. It can be thought of as a mapping between a disk block and its copy in memory. The bh is not central to Linux memory management in the way it once was, but a number of filesystems still use it to handle their disk I/O tracking. Note that there is not necessarily a bh structure for every block found within a page; if a filesystem has reason to believe that only some blocks need writing, it does not need to create bh structures for the rest. Among other things, the bh structure contains yet another dirty flag. With all of these different flags representing what is essentially the same information, it is not entirely surprising that some confusion eventually came about. The maintenance of redundant data structures can be a challenge in any setting, and the kernel environment adds difficulties of its own. Deep within the kernel, there is a function called set_page_dirty(); it is used by the memory management code when it notices (via a PTE or a direct application operation) that a page is in need of writeback. Among other things, it copies the dirty bit from the page table entries into the page structure. If the page is part of a file, set_page_dirty() will call back into the relevant filesystem - but only if said filesystem has provided the appropriate method. Many filesystems do not provide set_page_dirty() callback, however; for these filesystems, the kernel will, instead, traverse the list of associated bh structures and mark each of them dirty. And that is where the problem comes in. The filesystem may well have noticed that a block represented by a given bh was dirty and started I/O on it before the set_page_dirty() call. When the I/O is complete, the filesystem clears the dirty flag in the bh. If the set_page_dirty() call comes while the I/O on the block is active, the filesystem will not notice the fact that the block's data may have changed after it was written. Instead, the block will be marked clean, even though what was written does not correspond to what is currently in memory. File corruption results. Linus's fix is simple. When the virtual memory subsystem decides that it is time to write a page, a new call to set_page_dirty() is made. That ensures that all buffer heads will be marked dirty at the time the filesystem's writepage() method is called. That change ensures that all blocks of the page will be written; testers have confirmed that it makes the file corruption problems go away. The patch has gone into the mainline git repository; it should show up in the next 2.6.19 stable update as well. The longer-term solution is to continue pushing buffer heads out of the kernel's I/O paths. As Linus puts it:
The buffer head has been purely an "IO entity" for the last
several years now, and it's not a cache entity. Anybody who does writeback
by buffer heads is basically bypassing the real cache (the page cache),
and that's why all the problems happen.
I think ext3 is terminally crap by now. It still uses buffer heads in places where it really really shouldn't, and as a result, things like directory accesses are simply slower than they should be. Sadly, I don't think ext4 is going to fix any of this, either. Ted Ts'o responds that a fix for ext4 could yet happen, but it involves other filesystems as well. The ext3 filesystem is probably going to stay with buffer heads, however, meaning that the kernel will have to continue to work with them indefinitely. Finally, this story illustrates just how hard it can be to track down and fix certain kinds of kernel bugs. Early in the process it was hard for the interested developers to reproduce the problem, so they had to rely on the initial reporters to try out various patches. Those reporters stuck with the process, building and testing a lot of kernels before the problem was flushed out. They deserve much of the credit for the resolution of this problem.
Asynchronous buffered file I/OAsynchronous I/O (AIO) operations have the property of not blocking in the kernel. If an operation cannot be completed immediately, it is set in motion and control returns to the calling application while things are still in progress. This functionality allows a suitably-programmed application to keep multiple operations going in parallel without blocking on any of them.While Linux has long offered a set of system calls for asynchronous I/O, support within the kernel has been spotty and slow in coming. Most char devices do not provide the necessary methods - generally because there is no pressing need for them to support asynchronous operations. Networking supports AIO reasonably well. At the block level, all I/O is asynchronous, but that is not true when dealing with the virtual filesystem layer. Quite a bit of work went into supporting asynchronous direct filesystem I/O, making the big database vendors happy. But most applications do not use direct I/O, and the system as a whole usually benefits from the use of buffered I/O. So asynchronous buffered I/O support is arguably the biggest remaining hole. Various buffered filesystem AIO patches have been posted over the course of some three years, but none have made it into the kernel. Recently, Suparna Bhattacharya has restarted this work with a new file AIO patch which attempts to add this capability in the least intrusive way possible. This work may now be simple enough that few will be able to find things to object to. Like previous versions of the patch, the current code adds a special wait queue to each process's task structure. That queue is used for normal synchronous operations, while asynchronous operations each have their own, dedicated queue. The current wait queue is passed into filesystem I/O operations which could block. That enables a couple of special tricks to be performed:
The normal buffered filesystem read code, simplified almost into oblivion, looks something like this:
for each file page to be read
get the page into the page cache
copy the contents to the user buffer
The real code can be found in mm/filemap.c as do_generic_mapping_read(), but the leading comment notes that "this is really ugly." It is one of only three functions so marked in that file, so, trust your editor, and go with the simple version above. In the pseudocode version, the place where things block is clearly the step where the file page is read into the page cache. If the page is not already cached, the kernel will have to set up a disk I/O operation and wait for it to be carried out. That code proceeds the way it always did, until it gets to the "wait" part, at which point the AIO wait queue will be noticed and the code will return to whatever it was doing before. Once the read completes, the special wakeup function associated with the AIO queue will pick up where things left off. One might well wonder just how that "pick up" part works. The wakeup function will not be running in the process of the original calling application, and may well not be running in process context at all. So it queues up a workqueue function which will examine the state of the outstanding I/O operation and, if necessary, jump back into the loop above to continue the work. Before doing so, however, the workqueue function carefully tweaks its memory management context so that it shares the original application's address space. That tweak is necessary to make the final line above (copy the page to the user buffer) work as expected. The workqueue function will perform that copy, then proceed on to the next page (if any). Likely as not, that next page will need to be read in from disk, so the workqueue function will, after ensuring that the operation is started, simply quit. This process repeats until all of the requested data has been read, at which point the application can be notified that the operation is complete. On the write side, one might think that no changes are required - buffered file writes are already asynchronous, with the flush to disk happening in the background. The exception, however, is when O_SYNC is in use. There are situations where applications want to know when the data has found its way to the disk platter, but they still don't want to block waiting for that to happen. A very similar approach is used to make asynchronous O_SYNC writes work, though the patch is a little larger. A couple of the low-level page writeback functions required modifications so that they would pass the relevant wait queue around. Even with this change in place, writes can still block on occasion. In particular, any operation which requires allocating disk blocks for the file may block while those allocations are performed. This issue can probably be worked around, but that work has not yet been done. The result of all this is a working asynchronous buffered file I/O capability which makes almost no changes to (and adds little overhead to) the "normal" synchronous code. If no serious objections are raised, the Linux AIO subsystem might just become a little more complete in the near future.
Patches and updates Kernel trees
Core kernel code
Development tools
Device drivers
Documentation
Filesystems and block I/O
Janitorial
Memory management
Networking
Architecture-specific
Virtualization and containers
Miscellaneous
Page editor: Jonathan Corbet Distributions News and Editorials New special purpose distributions - Firmware Linux and NSLU2-LinuxTwo highly specialized Linux distribution projects were added to our Distribution List over the holidays and they are worth a closer look. These aren't your typical desktop distributions, or LAMP server distributions, but they do scratch a particular itch.The first one we'll cover is Firmware Linux. It was introduced in this comment as an example of a Linux system that does not rely on GNU software, although it's not quite there yet. "Currently, building it still requires four gnu packages (gcc, binutils, make, and bash), but replacements for all four are in the works. (The replacement for gcc/binutils is tcc, which still needs some work, and I'm writing my own shell and when that's ready, my own make.) If your final system doesn't need to be a development environment, then it doesn't have to have any gnu code in it at all." Firmware Linux is designed to be a build system that produces a bootable single file Linux system for various hardware platforms. Along the way, the build produces a relocatable cross compiler for the target hardware, and also a native build environment. This is a very young project, with only a few months of development so far, however, according to the news page as of changeset 68 it does build a native build environment with a working toolchain. The second project is a bit more mature and has a family of Linux systems in development. The NSLU2-Linux project exists to discuss, develop and modify the firmware and hardware of the Linksys NSLU2, the Synology DS101, the Iomega NAS100d, the D-Link DSMG600, and other ixp4xx-based devices with large attached storage. SlugOS is the collective name for a group of firmware distributions which are derived from a common source base. The post to the NSLU2 mailing list summarizes the current state of the project. Here are some highlights:
LinuxDevices covered the Debian etch support in is this November article: "Now, the newly available RC1 release of debian-installer for Etch makes installing Linux on the Slug much easier, according to Debian ARM hacker Martin Michlmayr. For one thing, the generic IXP4xx kernel in Debian ARM now appears to support the device." There's also an article on SmallNetBuilder, Hacking the Linksys NSLU2 - Debian and more with a look at the project's history.
New Releases BLAG-60000 (puente) Beta ReleasedBLAG Linux and GNU has announced the first beta of BLAG 60000, a new series based on Fedora Core 6, with many new applications. Since September 3rd, 2006, over 50 alpha versions of BLAG-60000 have been spun. Now the first beta is ready for testing.
Announcing the Fedora 6 Zod live CD and live CD toolsThe first official Fedora live CD has been announced. This live CD is based on packages from the Fedora Core 6 (codenamed "Zod") and Fedora Extras package collections and is such 100% free software. The live CD is currently only available for i386 architectures. Support for other architectures including ppc and x86_64 is planned. Click below for download information.
Kate OS Linux rev adds graphical package manager (DesktopLinux)DesktopLinux takes a look at the recent release of KateOS 3.2. "The KateOS project team, which maintains a full-featured Linux distribution derived from Slackware Linux, last week released an installation version. KateOS version 3.2 features a 2.6.18 kernel, Xfce as its default desktop, and native support for the KDE and GNOME desktop environments. The latest release also boasts a new graphical package management tool, KatePKG, said to enable easy and intuitive installation, removal, and updating of packages."
KNOPPIX 5.1 releasedVersion 5.1 of the Debian-based KNOPPIX live CD and DVD is available. It features a 2.6.19 kernel, ntfs-3g and beryl. See the release notes for more information. (Thanks to Phil Lewis)
Musix 0.79 releasedMusix GNU+Linux has released version 0.79. Musix is a free multimedia operating system for music production, graphic design, audio and video edition, and more.
Trustix Secure Linux 3.0.5 Beta 3Trustix Secure Linux 3.0.5 Beta 3 is available. "Thanks to many reports and suggestions, this release contains some critical fixes and improvements in the installer and other software."
Amulet launches Japanese Yellow Dog Linux v5.0 for PS3Terra Soft Solutions and The Research and Development Department of AMULET, Inc (Chiyoda-ku Tokyo) have announced the launch of Japanese Language Package of Yellow Dog Linux v5.0J for the Sony Computer Entertainment PLAYSTATION3, slated to ship January 4, 2007.
Distribution News Debian 'etch' release update - main blockers for releaseWhile it does look like the Debian stable 'etch' release will not happen this year, it is getting closer. Here's an update from Andreas Barth. "There are a few items to resolve so that we could actually release. We need your help there - in whichever area you want to help us, please do so. Please remember: Releasing of Debian is a common effort of the whole community."
Fedora Legacy shutting downHere's an official announcement from the Fedora Legacy project. "In case any of you are not aware, the Fedora Legacy project is in the process of shutting down. The current model for supporting maintenance distributions is being re-examined. In the meantime, we are unable to extend support to older Fedora Core releases as we had planned. As of now, Fedora Core 4 and earlier distributions are no longer being maintained."
OpenPKG Project Policy Changes for ContributionsThe OpenPKG project has made some changes to its policies on contributions and asks contributors to explicitly agree to the new OpenPKG Contributor Agreement (OCA) document.
openSUSE @ FOSDEM 2007 call for papers/speakers/participantsThe openSUSE project has a "devroom" at the Free Open source Software Developers' European Meeting (FOSDEM) taking place February 24 - 25, 2007 in Brussels (Belgium). "For 2007, we dare to challenge all of us, the community, to play a much more active role in making FOSDEM 2007 a great success. Therefore we would like to open a "call for papers" and encourage everyone to send proposals to the opensuse-project@opensuse.org mailing list. Proposals should be submitted by January 15, 2007."
Distribution Newsletters Debian Weekly NewsThe Debian Weekly News for December 26, 2006 covers the 400,000th bug report, a call for participation in the Debian mini-conf at linux.conf.au, 20,000 submitters for popularity contest, five years of debianforum.de, ARM is now the third most-popular Debian Architecture, installing Debian without a CD-ROM, an Etch-CD with KDE as the default desktop, Etch frozen, Debian powers Australia's largest satellite network, Debian Package of the Day, and much more.
Gentoo Weekly NewsletterThe Gentoo Weekly Newsletter for December 18, 2006 looks at EFIKA overlay opens, Quickstart 0.3 and several other topics.
DistroWatch Weekly, Issue 183The DistroWatch Weekly for January 1, 2007 is out. "With another exciting year safely behind us, we'll start the first issue of DistroWatch Weekly in 2007 with a statistical look at the popularity of Linux distributions and other interesting data collected here during the past year. The news section will then bring a varied collection of happenings from the distro world, including news about the latest beta release of SimplyMEPIS, updates about the forthcoming Fedora 7, information about the release blockers delaying Debian GNU/Linux 4.0, links to interviews with the developers of Ulteo and SabayonLinux, and alerts to articles of interest to users of PCLinuxOS, openSUSE and Yellow Dog Linux. Finally, we are pleased to announce that the December 2006 DistroWatch donation goes to SabayonLinux."
Package updates Fedora updatesUpdates for Fedora Core 6: frysk (split to several rpms), wget (bug fixes), jpackage-utils (update to latest jpackage-utils), htdig (fixed htfuzzy's sigfaults), gtk2 (bug fixes), evince (fix a copy-and-paste error in the %post script), gnome-applets (bug fix), desktop-printing (bug fix), selinux-policy (bug fix), dvd+rw-tools (bug fix), poppler (solve conflict with xpdf-utils), gnome-python2-extras (rebuild against firefox), scim (bug fixes), frysk (new upstream version), dbus-glib (bug fixes), autofs (bug fixes), xen (update to xen-3.0.3-8.rhel5), libvirt (new upstream release), kernel (update to 2.6.18.6 final), gtk2 (bug fixes), virt-manager (bug fixes), python-virtinst (bug fixes), less (bug fixes), cups (bug fixes), logwatch (bug fixes), m17n-db (bug fix), gphoto2 (update to 2.3.1), hal (bug fix), libgnomeprint22 (bug fix), smartmontools (bug fix), eclipse-cdt (update autotools plug-in to 0.0.6).Updates for Fedora Core 5: frysk (split to several rpms), dvd+rw-tools (bug fix), frysk (new upstream version), xen (add vmxassist fix), less (bug fixes), gphoto2 (update to 2.3.1).
Mandriva updatesUpdates for Mandriva Linux 2007.0: lsb (bug fix).
rPath updatesUpdates for rPath Linux 1: httpd, mod_ssl (MIME type and path corrections).
Trustix updatesUpdates for Trustix Secure Linux 2.2 & 3.0: hwdata, mysql (various bug fixes).
Ubuntu updatesUpdates for Ubuntu 6.10: control-center (upload to edgy-updates).
Newsletters and articles of interest Red Hat's next Linux due before March (ZDNet)ZDNet covers the release schedule for Red Hat Enterprise Linux 5. "Red Hat Enterprise Linux 5 had been scheduled to ship by the end of 2006. However, the company began giving itself scheduling wiggle room in September, when Red Hat released the first RHEL 5 beta. A second beta arrived in November. Now Red Hat is being more definitive. "I'm sure we will ship a gold (version) on February 28," Chief Executive Matthew Szulik, referring to the final version, said in an interview after the company reported its quarterly financial results."
How To Compile A Kernel - The Debian (Sarge) Way (HowtoForge)HowtoForge builds a custom kernel on a Debian Sarge system. "Each distribution has some specific tools to build a custom kernel from the sources. This article is about compiling a kernel on Debian Sarge systems. It describes how to build a custom kernel using the latest unmodified kernel sources from www.kernel.org (vanilla kernel) so that you are independent from the kernels supplied by your distribution. It also shows how to patch the kernel sources if you need features that are not in there."
Sabayon Linux Interview (KnoLinux)KnoLinux has an interview with Sabayon Linux developer Christopher Villareal. "Knolinux: Hello Chris, Why did you start working on a new Linux distro? Chris: Let's see, my gnu/linux experience started about 6 years ago when I started out with the major binary distributions. Since then, I got agitated by the fact that I didn't have as much control over the system as I wanted. Then I came to gentoo after trying out some other source distros due to the tools that were available to me. As such, I was doing some searching and found a distro called RR4/RR64 which looked extremely promising. So on Dec. of '05 I joined the forums and started making post. Soon, I got used to helping others and really enjoyed the RR experience and had the pleasure to speak with the Lead on occasion. 6 monthes of hard work, I threw the idea to Fabio (lxnay) to become his co-lead and I really liked the fact of helping people come to an excellent distro. Its all about the community effort, and I wanted to help. Currently I am helping maintain the main chroot environment, our custom overlay, and just managing bugs and interacting with the users through irc, the forums, and jabber."
OpenVZ On Debian Etch For Webservers (HowtoForge)HowtoForge sets up OpenVZ on a Debian etch system. "This guide is written during an install of a Supermicro machine with 2 dual-core opterons (64-bit), 2 identical disks (for RAID) and a load of memory. Why OpenVZ and not XEN or the recent KVM kernel module? Well, XEN is not very stable for 64-bit architectures (yet), and it comes with quite a bit of overhead (every VM runs its own kernel) due to its complexity. KVM is very simple but restricts you to run a kernel as one process, so the VM cannot benefit from multi core systems."
Distribution reviews Review: VectorLinux 5.8 (Linux.com)Linux.com has a review of VectorLinux 5.8. "VectorLinux, a lightweight, fast Linux distribution for the x86 platform, just released its new version 5.8 this week. This user-friendly distribution makes the average computer user's life easy by supplying office software, Web browsing, photo editing, and archiving on top of a fast, clean Xfce window manager."
The well-tempered Debian desktop (DesktopLinux)Rick Lehrbaum reviews a Debian Etch install on an old Thinkpad. "I began by downloading RC1 of the Debian "testing" net-install CD (aka "etch RC1") iso file from here. It's a quick download, being a 100-150MB file. I like that. After burning the CD from the iso, I popped it into the Thinkpad, and booted it up."
Page editor: Rebecca Sobol Development CherryPy reaches the 3.0.0 milestoneCherryPy is a Python-based cross-platform object-oriented web development framework:
CherryPy allows developers to build web applications in much the same way they would build any other object-oriented Python program. This usually results in smaller source code developed in less time.
CherryPy is now more than three years old and it is has proven very fast and stable. It is being used in production by many sites, from the simplest ones to the most demanding ones.
The basic operation of CherryPy is explained:
Your CherryPy powered web applications are in fact stand-alone Python applications embedding their own multi-threaded web server. You can deploy them anywhere you can run Python applications. Apache is not required, but it's possible to run a CherryPy application behind it (or IIS).
Passing interactive data to CherryPy is simple:
You write request handler classes that you tie together in a tree of objects, starting with a root object. CherryPy maps incoming request URIs to this object tree. The URI '/' represents the 'root' object, '/users/' the 'root.users' object, and so on. Requests are handled by methods inside these request handler classes.
Examples of a simple Hello World program and the passing of GET/POST variables to methods show the simplicity that CherryPy development offers. CherryPy version 3.0.0 brings the following changes:
System Applications Database Software Firebird 1.5.4 announcedVersion 1.5.4 of the Firebird DBMS has been announced. "This sub-release introduces a number of bug fixes backported from the Firebird 2.0.x branches."
PostgreSQL Weekly NewsThe December 25, 2006 edition of the PostgreSQL Weekly News is online with the latest PostgreSQL DBMS articles and resources.
PostgreSQL Weekly NewsThe January 1, 2007 edition of the PostgreSQL Weekly News is online with the latest PostgreSQL DBMS articles and resources.
Embedded Systems BusyBox 1.3.1 releasedStable version 1.3.1 of BusyBox, a collection of command line utilities for embedded systems, is out. "Closing 2006 with new release. It includes only trivial fixes accumulated since 1.3.0"
Libraries PyTables 1.4 releasedVersion 1.4 of PyTables has been announced. "PyTables is a library for managing hierarchical datasets and designed to efficiently cope with extremely large amounts of data with support for full 64-bit file addressing. It is based on the HDF5 library for doing the I/O and leverages the numarray/NumPy/Numeric packages so as to deliver the data to the end user in convenient in-memory containers. This is a new major release of PyTables, and probably the last major one of the 1.x series (i.e. with numarray at the core). On it, we have implemented better code to deal with table buffers, enhanced the capability for reading native HDF5 files, enhanced support for 64-bit platforms (but not with Python 2.5: see ``Special Warning`` section below), better support for AIX, optional automatic parent creation and the traditional amount of bug fixes."
Mail Software poMMo - The post modern Mass MailerBrice Burgess has sent us an announcement for his poMMo mailing list manager project. "poMMo is versatile mass mailing software. It can be used to add a mailing list to your Web site or to organize stand alone mailings. Unique Features such as the ability to mail subsets of your subscribers set it apart from alternatives. poMMo is written in PHP and freely provided under the GPL."
Postfix 2.4 Snapshot 20061229 releasedSnapshot 20061229 of the Postfix mail transfer agent is out. See the CHANGELOG file for details.
Desktop Applications Audio Applications das_watchdog V0.2.5 and jack_capture 0.9.3 announcedNew versions of the audio applications das_watchdog and jack_capture have been announced. "Whenever a program locks up the machine, das_watchdog will temporarily sets all realtime process to non-realtime for 8 seconds. You will get an xmessage window up on the screen whenever that happens. ... jack_capture is a program for recording soundfiles with jack."
AWN Issue 4 released (KDE.News)KDE.News has announced issue #4 of the Amarok Weekly Newsletter: "Late but worthy - thats how one can call this issue of AWN. It talks about new or updated Amarok features, and continues to provide tips and links to interesting scripts. As a bonus, kind of New Year gift, we provide you an experimental RSS feed, for your pleasure. Enjoy!"
Desktop Environments GNOME 2.17.4 releasedVersion 2.17.4 of the GNOME desktop environment is available. "This is our second development release on our road towards GNOME 2.18.0, which will be released in March 2007. New features are coming in at a nice rate, and that's great. A lot of bug fixes too. And some crashers are appearing here and there: that's the fun of unstable releases!"
GARNOME 2.17.4 announcedVersion 2.17.4 of GARNOME, the bleeding-edge GNOME distribution, is out. "This release includes all of GNOME 2.17.4 plus a whole bunch of updates that were released after the GNOME freeze date. This is the fourth release in the unstable cycle, with more features, more fixes and yet more madness added. It is for anyone who wants to get his hands dirty on the development branch, or who'd like to get a peek at future features."
GNOME migration to Subversion finishedThe migration of the GNOME desktop to the Subversion version control system has been completed. "For those that haven't noticed, the subversion migration is now complete. In the end, it took about 49 hours. Apologies for the downtime involved."
GNOME Software AnnouncementsThe following new GNOME software has been announced this week and last:
KDE Commit-Digest (KDE.News)The December 24, 2006 edition of the KDE Commit-Digest has been announced. The content summary says: "A new game, KSquares, is imported into KDE SVN, with KLines starting on the (now familiar) path towards scalable graphics and general improvement. Usability and other improvements in Okular. Support for multiple "identies", alongside a festive basket of other enhancements in Mailody. Search support and plugin handling improvements in KGet. In Amarok, the "yauap" engine (a redeveloped GStreamer interface, using D-Bus interaction) progresses, with support for audio CD's. Improved OpenFormula specification compliance in KSpread. A much-enhanced implementation of "run-around text" comes to KWord. A work-in-progress python parser for KDevelop is imported into KDE SVN. Work begins on the Oxygen-themed widget style and window decoration for KDE 4."
KDE Commit-Digest (KDE.News)The December 31, 2006 edition of the KDE Commit-Digest has been announced. The content summary says: "The KDE Commit-Digest 2006 retrospective. blinKen and KNetWalk become the latest applications to move to scalable graphics. KSquares further develops, with an AI player implemented. More maps and a more sophisticated divisions and capitals implementation in KGeography. Support for password-protected RAR archives in the kio_rar interface. Work to support drag-and-drop of transfers in KGet. Import of "koregressions" test suite for KOffice. Longstanding KWeather and KHTML bugs fixed. Major refactoring in the "sonnet" natural language checker. Version 1.0 of Eigen, the library for vector and matrix math, is released."
KDE Software AnnouncementsThe following new KDE software has been announced this week:
The Road to KDE 4: SVG Rendering in Applications (KDE.News)KDE.News presents a short overview of some of features going into KDE 4. "Since KDE 4 development is in full swing with plans for a KDE 4.0 release sometime later this year, I thought I'd put together a weekly piece entitled The Road to KDE 4. The idea is to have a short overview of one or two of the features that show progress in KDE 4. For my first issue, the goal is to show off some of the great SVG work that has taken place so far."
Xorg Software AnnouncementsThe following new Xorg software has been announced this week and last:
Electronics KJWaves 1.1.0 releasedVersion 1.1.0 of KJWaves, a Java program for viewing RAW SPICE electronic simulation files, has been announced. "New version allows adding of traces to previous graphs and improves on ability to add current through a component analysis."
Games Battle for Wesnoth 1.2 releasedVersion 1.2 of the game Battle for Wesnoth has been announced. "The single player mode has a new tutorial, and 3 new campaigns: Two Brothers, The South Guard, and Under the Burning Suns. The first one was intentionally designed to be easy for beginning players. The last one is set in an environment quite different from that of the typical Wesnoth campaign, and includes a few changes to game rules. The existing campaigns include new scenarios, dialogue, items, and optional bonus victory objectives. Replay of saved games has been improved considerably, allowing one to show single turns at a time, navigate through the replay, and toggle fog-of-war at will." Many more changes have been included.
Imaging Applications PDFCube 0.0.2 releasedVersion 0.0.2 of PDFCube is out. "PDF Cube is an OpenGL API-based PDF viewer that adds a compiz/Keynote-like spinning cube tra[n]sition effect to your PDF presentations (including Latex, Beamer and Prosper). You can also zoom on 5 predefined areas of any presentation page with a smooth zooming effect."
Interoperability Wine 0.9.28 releasedVersion 0.9.28 of Wine has been announced. Changes include: OpenGL in child windows should work again, Better mouse support in games, Beginnings of new state management in Direct3D, Improved audio and font support on Mac OS and Lots of bug fixes.
Medical Applications Synapse EMR (LinuxMedNews)LinuxMedNews reports on the Linux port of Synapse EMR, an electronic medical record system. "Synapse EMR port to Linux has now gone beta. Download from http://www.compkarori.com/emr/linux/. Almost all of the non-Windows specific functionality is now available for the Linux client."
Music Applications amSynth 1.2.0 releasedVersion 1.2.0 of amSynth, a virtual music synthesizer, is out. Changes include better graphics, better MIDI all-off handling, a new about dialog, better installation and bug fixes.
BEAST/BSE v0.7.1 announcedVersion 0.7.1 of BEAST/BSE and BSE-ALSA have been announced, it features a security fix and other improvements. "This is a development version of BEAST/BSE, the BEdevilled Audio SysTem and the Bedevilled Sound Engine. BEAST is a powerful music composition and modular synthesis application released as free software under the GNU GPL and GNU LGPL, that runs under unix. BSE-ALSA is an ALSA driver for BSE."
rtsynth 1.9.5 alsa+jack announcedVersion 1.9.5 of RTSynth, a midi event triggered real time synthesizer is out with support for dynamically loaded jack drivers, a new --polyvoice command line option and bug fixes.
Office Applications Bruce The Presentation Tool, release 1.2Release 1.2 of Bruce The Presentation Tool has been announced. "Bruce the Presentation Tool is for Python programmers who are tired of fighting with presentation tools. In its basic form it allows text, code or image pages and even interactive Python sessions. It uses PyGame and is easily extensible to add new page types."
Office Suites OpenOffice.org NewsletterThe December, 2006 edition of the OpenOffice.org Newsletter is out with the latest OO.o office suite articles and events.
Science First public release of ANUGA hydrodynamic modelingThe ANUGA hydrodynamic modeling system has been launched. "ANUGA is a software implementation of a hydrodynamic model which is specifically designed to model wetting and drying processes. ANUGA implements a Finite-Volumes technique for solving the Shallow Water Wave Equations. ANUGA is a joint development project between Geoscience Australia (GA) and the Australian National University (ANU) and is being used to simulate the impact from natural disasters such as tsunami and storm-surge on coastal communities. ANUGA is also suitable for detailed dam-break simulations."
Web Browsers Mozilla Firefox and Thunderbird 1.5.0.9 Released (MozillaZine)Versions 1.5.0.9 of the Mozilla Firefox web browser and the Mozilla Thunderbird email client have been announced. "Security and Stability updates for Mozilla products based on the Gecko 1.8.0 branch have been released. Firefox 1.5.0.x will be maintained with security and stability updates until April 24, 2007. All users are strongly encouraged to upgrade to Firefox 2."
Mozilla Firefox 2.0.0.1 released (MozillaZine)Version 2.0.0.1 of the Mozilla Firefox web browser has been announced. "Mozilla Firefox 2.0.0.1, a security and stability update for Firefox 2, has been released. This release addresses several critical security issues. All users are encouraged to upgrade to this release."
Languages and Tools Caml Caml Weekly NewsThe December 26, 2006 edition of the Caml Weekly News is out with new Caml language articles.
Caml Weekly NewsThe January 2, 2007 edition of the Caml Weekly News is out with new Caml language articles.
FORTRAN Gfortran year end status reportA year end status report for Gfortran, the GNU FORTRAN compiler project, has been published. "Gfortran has achieved many milestones this year and hopefully the contributors can continue to move forward with bug fixes, conformance to Fortran 95 standard, and the implementation of Fortran 2003 features."
Haskell Haskell Weekly NewsThe January 2, 2007 edition of the Haskell Weekly News is online. This week brings a new release of vty and HsColour, and some interesting discussion over the holiday break.
Java Review/Preview: 2006 and 2007 in Java (O'ReillyNet)Chris Adamson looks at recent and upcoming Java developments on O'Reilly. "2006 will be remembered as the year that Sun open-sourced Java under the GPL, that EJB 3.0 finally shipped, and that Google surprised everyone with its Google Web Toolkit. But how will history record the results of these events? For the 2006 year-ender, ONJava editor Chris Adamson looks at the year's events through the lens of how they may play out in 2007."
JUnit Reloaded (java.net)Ralf Stuckert discusses the latest changes to JUnit on java.net. "Let's face it, JUnit is the most widely used (unit-) testing tool in the Java world. There are other powerful test frameworks out there, such as TestNG (which is very comprehensive), but they've never enjoyed the broad acceptance JUnit has. With version 4, Kent Beck and Erich Gamma introduced the first significant API changes in the last few years. When the first release candidate was available back in 2005, you could hardly use it in a productive working environment due to the lack of tool support at that time. By now, most build tools and IDEs come with support for JUnit 4, so it's about time to give it a try. This article describes what's different compared to JUnit 3.8.x."
Perl Weekly Perl 6 mailing list summary (O'Reilly)The December 17-23, 2006 edition of the Weekly Perl 6 mailing list summary is out with coverage of the latest Perl 6 developments.
Weekly Perl 6 mailing list summary (O'Reilly)The December 24-30, 2006 edition of the Weekly Perl 6 mailing list summary is out with coverage of the latest Perl 6 developments.
99 Problems in Perl 6 (O'Reilly)Curtis Poe solves some problems using Perl 6 in an O'Reilly article. "Have you wanted to start playing with Perl 6 but find yourself wondering what to write? I use Pugs, a Perl 6 implementation being written in Haskell and have been tremendously enjoying Perl 6. Like many, Im impatient, but the work on Perl 6 has been progressing quite well and Im quite keen to see the alpha. However, if youre like me, you probably do better with a new language by actually writing something in it. Well, not only do I have something for you to write, you can actually help out the Perl 6 effort!"
Ruby Looking Ahead at Ruby in 2007 (Linux Journal)Pat Eyler looks ahead to Ruby developments in 2007 in a Linux Journal article. "Last week, I looked back at Ruby in 2006. This week, it's time to look ahead. Here are 10 Ruby things I think are going to be hot in 2007:"
Tcl/Tk Dr. Dobb's Tcl-URL!The December 29, 2006 edition of Dr. Dobb's Tcl-URL! is online with new Tcl/Tk articles and resources.
Tcl-URL!The January 2, 2007 edition of the Tcl-URL! is online with new Tcl/Tk articles and resources.
XML A Theory of Compatible Versions (XML.com)XML.com presents an article by David Orchard entitled A Theory of Compatible Versions. "Creating XML languages that are compatible and extensible is a difficult problem. This week David Orchard argues for a theory of compatibility in which he describes some of the conditions for creating compatible XML languages."
Debuggers A New Approach To DebuggingRobert O'Callahan talks about the Amber debugger project in his web log. "I have built a system, which I'm calling Amber, to record the complete execution history of arbitrary Linux processes. The history is recorded using binary instrumentation based on Valgrind. The history is indexed to support efficient queries that debuggers need, and then compressed and written to disk in a format optimized for later query and retrieval. The history supports efficient reconstruction of the contents of any memory location or register at any point in time. It also supports efficient answers to "when was the last write to location X before time T", "when was location P executed between times T1 and T2", and other kinds of queries. I can record the 4.1 billion instructions of a Firefox debug build starting up, displaying a Web page, and exiting; the compressed, indexed trace is about 0.83 bytes per instruction executed." (Thanks to Jerome Lacoste.)
IDEs eric3 3.9.3 releasedVersion 3.9.3 of eric3, an IDE for Python and Ruby, is available. "This release fixes a few bugs and enhances compatibility with subversion 1.4."
Page editor: Forrest Cook Linux in the news Recommended Reading A cost analysis of Vista content protectionPeter Gutmann has posted a lengthy look at the costs of the DRM features built into Windows Vista. Reading it is a sort of Alice-in-Wonderland experience, highly recommended. "If a graphics chip is integrated directly into the motherboard and there's no easy access to the device bus then the need for bus encryption is removed. Because the encryption requirement is so onerous, it's quite possible that this means of providing graphics capabilities will suddenly become more popular after the release of Vista. However, this leads to a problem: It's no longer possible to tell if a graphics chip is situated on a plug-in card or attached to the motherboard, since as far as the system is concerned they're both just devices sitting on the AGP/PCIe bus. The solution to this problem is to make the two deliberately incompatible, so that HFS can detect a chip on a plug-in card vs. one on the motherboard."
Predictions for 2007 (and how I did on 2006) (LinuxWorld)Don Marti takes a look at his predictions for 2006 and makes some new predictions for 2007. ""Platforms get granular for self-defense. Tired of worms that attack software you don't use, but that you need to patch anyway because it's part of the 'platform'? In 2006, you'll get better dependency checking to deploy just what you need, and update services that are smart enough not to bug you about software you don't need to update because you don't have it." Partial hit. The hot distribution was Ubuntu, which borrows its easier to manage approach from Debian. Package management is getting better all the time, but there still aren't enough tools to detect software that isn't being used and encourage new sysadmins to remove it."
The Ultimate Distro (Linux Journal)Glyn Moody examines the advantages of distribution forks in a Linux Journal article. "This is one of free software's greatest and least-appreciated strengths: the fact that it can continue to evolve in an almost organic fashion, untrammelled by constraints of economics, or even feasibility. It is this fecundity that drives free software forward unstoppably, and that distinguishes it from the sterile code monster that is Windows, which, trapped within the carapace of its closed source, only slouches towards Redmond to be born every five years or so." The article mentions the Linux distribution timeline, which gives a graphical representation of distribution forks.
Companies Jeremy Allison Has Resigned from Novell to Protest MS Patent Deal (Groklaw)Groklaw reports that Samba hacker Jeremy Allison has left Novell in protest. "Whilst the Microsoft patent agreement is in place there is *nothing* we can do to fix community relations. And I really mean nothing. We can pledge patents all we wish, we can talk to the press and "community leaders", we can do all the right things w.r.t. all our other interactions, but we will still be known as GPL violators and that's the end of it."
Financial firms back Microsoft Linux deal (The Register)The Register reports on some recent high profile SUSE Linux subscription customers. "Three big financial firms have come out of the closet and confirmed they have taken delivery of SUSE Linux subscriptions from Microsoft. Deutsche Bank, Credit Suisse and AIG Technologies have all signed up to the Franken-deal in the belief that it will make it easier to run Linux-based systems alongside Microsoft software."
Red Hat results kicks rump, takes names (Linux-Watch)Linux-Watch looks at Red Hat's financial results. "Red Hat Inc. on Dec. 21 announced its financial results for its fiscal year 2007 third quarter. The Raleigh, NC-based Linux company's numbers were, in a word, great. The total revenue for the quarter was $105.8 million, an increase of 45 percent from the year-ago quarter and 6 percent from the prior quarter. Subscription revenue was $88.9 million, up 48 percent year-over-year and 5 percent sequentially."
Linux at Work Linux powers controllable Christmas lights for charity (Linux.com)Joe 'Zonker' Brockmeier takes a look at a web-controlled Christmas light display that is powered by Linux. "During the holiday season, Komarnitsky says that he runs four Linux servers to keep up with the load -- one for each webcam, and one that serves up the pages to the public. Komarnitsky says that the entire system is run by Linux, with the exception of the laptop that displays messages typed in by users. Komarnitsky uses three D-Link DCS-6620G webcams, one of which was donated by D-Link."
Legal Apple, Google, Napster Face Intertainer Patent Suit (Bloomberg)Bloomberg briefly reports on a software patent suit filed against Apple, Google, and Napster. "Culver City, California-based Intertainer's investors include Microsoft Corp., the world's biggest software maker, and Intel Corp., the world's biggest semiconductor maker." The patent in question would appear to be #6,925,469, which covers distribution of "digital media content" in very general terms.
Interviews Ubuntu Founder On Microsoft "Challenge" (Red Herring)The Red Herring interviews Mark Shuttleworth. "Microsoft and others, a lot of them say that free software and open source is all about copying what was being done before in proprietary software, and for a lot of time that was true. The world we are seeing is that, as soon as the free software reaches a point where it's as good as the proprietary software, suddenly all the innovation shifts to the free software."
Resources Bandwidth Monitoring Tools for Ubuntu Users (Ubuntu Geek)Ubuntu Geek takes a look at a number of network bandwidth monitoring tools. "Here is the list of bandwidth monitoring tools for your network bandwidth: bmon, bwbar, bwm, bwm-ng, iftop, iperf, ipfm, speedometer, cbm, ibmonitor, pktstat, mactrack, MRTG, Cacti. Now we will see each tool separately."
Linux Gazette #134 is outThe January edition of Linux Gazette is available. Articles include Fun with FUSE, Mounting remote resources as filesystems via FUSE (Filesystem in Userspace), Away Mission -- OracleWorld '06, San Francisco, Installing Mandriva, OSI, GAP, and "Exhibit B" licences, Perl One-Liner of the Month: The Count of Corpus Christi (TX), and much more.
Reviews The Buzz About Aldrin (Linux Journal)Dave Phillips reviews Aldrin on Linux Journal. "For the past month I've been building and playing with Leonard 'paniq' Ritter's Aldrin, a music production system that combines a tracker-style composition interface with audio synthesis and processing modules called machines. Users of the famous Buzz music software will probably recognize Aldrin's design at once. In fact, it may be fair to describe Aldrin as Leonard Ritter's interpretation of the original Buzz."
A Good Beginning (And Some Holiday DSP) (Linux Journal)Dave Phillips looks at DSP software in the Linux Journal. "[Sonic Visualizer] truly emphasizes visualization, with data view formats such as various spectrograms, amplitude waveform, piano roll (for MIDI plot), chronogram, pitch envelope, and power curve. The user scrolls through the views with the Navigate cursor (the pointing hand) and uses the Select tool (the arrow) to make selections within the view. Edits are limited to cut/copy/paste, but the program isn't intended for audio processing. It is primarily a tool for audio analysis and visualization, and an excellent tool at that. Highly recommended for serious research and viewing enjoyment."
Low-cost laptop could transform learning (Yahoo)Yahoo has an AP article on the OLPC project. "Nicholas Negroponte, who launched the project at the Massachusetts Institute of Technology's Media Lab two years ago before spinning One Laptop into a separate nonprofit, said he deliberately wanted to avoid giving children computers they might someday use in an office. 'In fact, one of the saddest but most common conditions in elementary school computer labs (when they exist in the developing world), is the children are being trained to use Word, Excel and PowerPoint,' Negroponte wrote in an e-mail interview. 'I consider that criminal, because children should be making things, communicating, exploring, sharing, not running office automation tools.'"
Book review: OpenOffice.org 2 Guide (Linux.com)Linux.com reviews a book about OpenOffice.org. "OpenOffice.org expert Solveig Haugland has published a massive new manual called the OpenOffice.org 2 Guide. This 520-page tome will be useful both for OOo newbies and power users who are interested in learning arcane features of the office suite. What does Haugland's $28 book have that the free online guides don't? The primary distinction is that Haugland's book is one work in one place, whereas the community's guides are available for sale in the form of separate books on the main OOo programs (Writer, Calc, Draw, Impress) for generally $10 to $20, or for free download."
A first look at Thunderbird 2.0 (Linux.com)Linux.com looks at Thunderbird 2.0. "After many months of development, Thunderbird 2.0 is almost ready to debut. The Mozilla Foundation released the first beta of Thunderbird 2.0 last week, and I've been using it to manage my mail since then. The new release boasts tagging, history navigation, new mail alerts, improved extension support, and a number of other features. Thunderbird 2.0 won't knock your socks off with exciting new features, but it's a nice, gradual improvement over the Thunderbird 1.5 series."
Google Toolbar 3.0 beta improves browsing experience (Linux.com)Linux.com looks at the Google Toolbar 3 beta for Firefox. "I tested the toolbar with Firefox 2.0 and Flock 0.7.9. You'll see a warning before you install the toolbar on Flock that the extension wasn't designed specifically for Flock, but I haven't run into any problems with it so far in Flock. Once I had it installed, I signed out of Google services and signed in using the Google Toolbar sign-in feature. I was then authenticated for Gmail, Google Apps, Google Bookmarks, Blogger, and the whole kit and caboodle of Google services I tried, with the exception of AdSense."
New Xen better for desktops (ZDNet)ZDNet looks at a new release of Xen, a commercial virtualization system. "On a desktop system, Xen virtualization promises to keep separate zones for test, work, personal and management software. So far, however, that promise has been hampered by a major weakness: the inability to display multiple graphical user interfaces for these "guest" operating systems. Xen 3.0.4 changes this. By including what's called a virtual frame buffer, Xen's controlling "host" operating system can capture video data written to a specific part of memory and then send it to the display. The technology lets users see virtual machines through a graphical interface, a feat competitors such as EMC's VMware can already accomplish, rather than the text-based command line suitable chiefly for the technically proficient."
Miscellaneous Creative Commons gets new chairman; Lessig to continue as CEO (NewsForge)NewsForge reports that Lawrence Lessig has retired from his position as the Creative Commons chairman of the board. "After four successful years of revolutionizing how content is shared in the real world, Lawrence Lessig, founding chairman of Creative Commons, announced his retirement as chairman of the board last week. Lessig passed the CC torch to Joi Ito, a venture capitalist from Japan. Creative Commons (CC) is a non-profit organization and is known for its Creative Commons copyright licenses. "We provide free licenses," Lessig writes, "that mark creative work with the freedom the creator wants it to carry, so others can share the work, or remix the work, or both share and remix the work, as the author chooses.""
South Korea's ETRI develops advanced Linux desktop search systemZDNet Korea looks at antbear, a desktop search system that addresses problems in the searching of text written with Asian character sets. "Advanced word recognition technology gives more reliable search results Linux desktop search, thus far, had some limitations due to its lacking features compared to Windows environment that has various features. Although 'Beagle' has been available for supporting Korean and other Asian languages (Chinese, Japanese), its 'bigram' search method in many situations fails to recognize true meanings of Asian characters for the search. For example, it breaks down and indexes the search word(s) into two separate characters, which can generate unrelated results. The reliability of the search result gets even worse when its search is based on larger number of files."
Grant funds open-source challenge to Google library (ZDNet)ZDNet reports that the nonprofit Internet Archive has received a million dollar grant from the Alfred P. Sloan Foundation. "The archiving organization's Open-Access Text Archive is an open-source alternative to book-scanning efforts like the ones from Google and Microsoft. Internet Archive, perhaps best known for its WayBack Machine archive of Web pages by date--is also an online digital library of text, audio, software, images and video content."
2006: The year the FSF reached out to the community (Linux.com)Linux.com looks at the Free Software Foundation. "The list of the community-based actions the FSF has taken in the past year is a long one. It begins with an expanded role for some of its longstanding institutions. Throughout the year, the FSF's high-priority list seems to have exerted some influence on such items as the open source release of the Java code and the growing interest in LinuxBIOS by chipset manufacturers. Similarly, the FSF's compliance lab, although now more than five years old, enlisted five volunteers to answer licensing questions using a ticket system, and now fields more than 75 questions each week, according to compliance engineer Brett Smith. In the last couple of years, too, rather than maintaining just the GNU Project Web site, the FSF has also started a non-developer site that Peter Brown, executive director of the FSF, describes as carrying "more of a mainstream message.""
Page editor: Forrest Cook Announcements Non-Commercial announcements The Council of the EU does not support LinuxIt seems that the Council of the European Union has a streaming service so that people can watch the meetings. That's a great idea, but they are using a proprietary format for the feed so that it can only be viewed on Microsoft Windows and Macintosh platforms. From the FAQ:
On which platforms can I view the live streaming media service of the
Council of the European Union?
A petition
has been created by Stefan Esterer, asking the council to make the feed
available to all by using a free codec. So if you are in the European
Union and would like to watch the council meetings you should consider
signing the petition.
The live streaming media service of the Council of the European Union can be viewed on Microsoft Windows and Macintosh platforms. We cannot support Linux in a legal way. So the answer is: No support for Linux
The Free Ryzom campaign is unsuccessfulThe Free Ryzom Campaign has announced that its bid to buy the Ryzom game from its bankrupt creator was turned down by the court. "At the end, there were three offers presented, and the other two were bigger than our's. They are keeping more employees than we do, and offer more money." The project is now discussing how it could continue and achieve its goal of creating a free multi-player online game. With the energy and resources they have pulled together, they could yet do interesting things. (Thanks to Dafydd Walters).
Nouveau driver pledgeThe nouveau driver project is working on an open source 3D acceleration driver for nVidia cards. To help out the project David Nielsen has started a pledge drive. He's looking for 1000 people to each pledge $10 USD by February 8, 2007.
OLPC announces its user interfaceThe One Laptop Per Child project has sent out a press release proclaiming the virtues of the user interface it has developed. "The Sugar UI, jointly developed with Red Hat and Pentagram, is the first to have been purpose-built as an educational environment for children using laptops. It is designed to support the learning experiences of elementary- and secondary-school children in poor, often rural communities by providing them with opportunities to freely explore, experiment and express themselves."
Rwanda to deploy OLPC systemsThe One Laptop Per Child project has announced that Rwanda will be rolling out OLPC systems. "In recognition of children being Rwanda's most precious natural resource, the government of Rwanda has committed to provide one laptop per child to all primary school children within five years."
Commercial announcements Digium launches AsteriskNOWDigium has announced the availability of "AsteriskNOW," a version of Asterisk bundled with an (unspecified) Linux distribution. It is claimed that, with AsteriskNOW, a functioning Asterisk phone system can be up and running within 30 minutes.All the software is GPL, but registration is required to download it. Worse, registration requires agreeing to terms of use including this gem: "Digium hereby authorizes you to copy materials published by Digium on the Website solely for non-commercial use by you or internally within your organization (or if you are a Digium Distributor or Partner, your customer's organization) solely in support of Digium products. No other use of the information is authorized." Update: the problem with the terms of use has been fixed.
eyeon Software Ships Fusion for Linuxeyeon Software has announced the availability of Fusion for Linux. Fusion is a visual effects software system. "Based on the recent December release of version 5.1, Fusion on Linux is the companys next universal platform initiative. We have been working hard on Fusion Linux, discovering along the way the necessary changes required to provide a product equal to the task of both the Fusion and Linux communities. And were really proud to deliver this in time for the holidays I need some sleep and a beer."
OpenRPT 2.0 open-source report writer announcedOpenMFG has announced version 2.0 of OpenRPT, a dual-licensed report writer. "OpenRPT 2.0 was retooled from the ground up to take full advantage of the underlying Qt 4 framework. Qt is an open source, comprehensive development framework that includes an extensive array of features, capabilities and tools that enable development of high-performance, cross-platform rich-client and server-side applications. Among the new OpenRPT features enabled by updating from Qt 3 to Qt 4 is the ability to export to Adobe PDF natively for both the OpenRPT API and the rendering application."
Open Source Virtualization for Sun UltraSPARC T1The OpenVZ project now runs on the Sun UltraSPARC T1 processor. "The OpenVZ project today announced its open source virtualization software is available for servers using Sun's breakthrough UltraSPARC(r) T1 CoolThreads(TM) processor. The operating system-level server virtualization software technology helps increase server utilization rates."
Red Hat Reports Third Quarter Fiscal Year 2007 ResultsRed Hat has announced their third quarter FY2007 financial results. " Total revenue for the quarter was $105.8 million, an increase of 45% from the year-ago quarter and 6% from the prior quarter. Subscription revenue was $88.9 million, up 48% year-over-year and 5% sequentially. Net income for the quarter was $14.6 million or $0.07 per diluted share compared with $11.0 million or $0.05 per diluted share for the prior quarter. Non-GAAP adjusted net income for the quarter was $29.6 million, or $0.14 per diluted share, after adjusting for stock compensation and tax expense as detailed in the tables below. This compares to non-GAAP adjusted net income of $22.7 million, or $0.11 per diluted share in the third quarter of last fiscal year."
Resources Commercial is not the opposite of Free-Libre / Open Source SoftwareDavid A. Wheeler presents an essay that looks at how commercial and open-source software are not mutually exclusive entities. "When I talk with with other people about Free-Libre / Open Source Software (FLOSS), I still hear a lot of people mistakenly use the term commercial software as if it had the opposite meaning of FLOSS (aka open source software, Free-Libre Software, or OSS/FS). Thats in spite of the rise in commercial development and support for FLOSS, most FLOSS projects goal to incorporate improvements, which are actually a form of financial gain, official definitions of commercial item that include FLOSS, and FLOSS licenses and projects that clearly approve of commercial support. Terms like closed source or proprietary software are plausible antonyms of FLOSS, but commercial is absurd as an antonym."
Contests and Awards Voting Has Opened for the 2006 LinuxQuestions.org Members Choice AwardsLinuxQuestions.org has announced that voting for the 2006 LinuxQuestions.org Members Choice Awards is now open. The Members Choice Awards allow the Linux community to select their favorite products in a variety of categories. Awards will be given out in 21 categories this year, including Distribution of the Year, Browser of the Year, Office Suite of the Year, Desktop Environment of the Year and Database of the Year. The polls will close on February 18th and the winners will be announced shortly after.
Surveys BasKet Note Pads Usability Survey (KDE.News)KDE.News has announced a new survey for BasKet Note Pads. "The aim of the BasKet Usability Project is to improve the usability of the BasKet Note Pads tool. Usability, as I (the project maintainer) see it, not only depends on the user interface, but also on the underlying assumptions that are made about the users and their context of use. So, knowledge of users, their contexts and claims are of vital importance for improving usability."
Education and Certification Test Your Knowledge of Samba Topics (Sys Admin)Sys Admin has published a free Samba quiz. "Samba is one of those technologies that you must know if you are working with integration today. Its importance is such that it is a focal point of the newly announced LPIC-3 certification from the Linux Professional Institute. Following are fifty questions on general aspects of Samba that anyone working with it at an advanced level should know. Good luck (answers are at the end of the article)!"
Calls for Presentations ICMC 2007 call for participationA call for participation has gone out for ICMC 2007, the International Computer Music Conference. "We are pleased to announce the general call for submission to the International Computer Music Conference 2007, which will take place at Holmen Island in Copenhagen starting Monday, August 27 and ending Saturday, September 1st, 2007. We invite original contributions in all areas of the computer music field in a number of formats. We are also open to any proposal, and encourage all submissions, including those that do not fit the categories below." The submission deadline is April 30.
SambaXP 2007 Call For PapersA call for papers has gone out for SambaXP 2007. "From April 23th to 25th 2007 developers and users will meet again in Goettingen, Germany at the sixth international SAMBA conference, the "samba eXPerience 2007"." Papers are due by February 5.
ShmooCon, Washington DC call for papersThe next ShmooCon will take place in Washington DC on March 23-25, 2007. Papers are due by mid January.
The O'Reilly Tools of Change for Publishing ConferenceO'Reilly has announced the 2007 Tools of Change for Publishing Conference along with a call for proposals. "To raise the level of technology knowledge in the publishing industry and to provide a meeting ground for those leading the charge into the future of publishing, O'Reilly Media is launching the first Tools of Change for Publishing (TOC) Conference. The TOC Conference will take place June 18-20, 2007 in San Jose, California. The call for participation is now open; proposals are due no later than January 22, 2007."
Upcoming Events European Patent Conference, BrusselsThe European Patent Conference will take place in Brussels, Belgium on January 24, 2007. "EUPACO-1 is the second in a series of events aimed at constructing a new European patent system through dialogue and collaboration based on research and data."
Call for Location OOoCon 2007 - Deadline ExtendedA call for location has gone out for the 2007 OpenOffice.org Conference. "The annual OpenOffice.org Conference (OOoCon) continues to go from strength to strength, with this year's glittering event in Lyon, France attracting over 600 registrations and enjoying a civic reception laid on by the Mayor of Lyon in the historic town hall. Can your team do even better next year?" The deadline for choosing the location has been extended to January 31, 2007.
Events: January 11, 2007 to March 12, 2007The following event listing is taken from the LWN.net Calendar.
If your event does not appear here, please tell us about it. Web sites GNU Herds - Free Software AssociationThe GNU Herds site has been launched. "GNU Herds is a not-for-profit and true-democratic association which aims to encourage the professional development of Free Software contributors."
Page editor: Forrest Cook Letters to the editor Recent comments
Dear Editor, Recent comments posted to articles on LWN have not been of the usual quality I have come to expect from LWN readers. A number of comments have been rude, used foul language, and consisted of personal attacks and childish name calling. I would like to ask LWN readers to please carefully consider their comments before posting them. LWN is not the place for such behaviour. The Internet is certainly large enough that such comments can find a more suitable forum. James Rich It's not the software that's free; it's you. - billyskank on Groklaw
Page editor: Jonathan Corbet
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![[Cheezy diagram]](/images/ns/kernel/DirtyPageBug1.png){kind=small}
In an attempt to explain what was going on, your editor will once again
employ his rather dubious artistic skills. To that end, readers are kindly
requested to look at the diagram to the right and suspend enough disbelief
to imagine that it
represents a page in memory - a page containing interesting data, and which
represents an equivalent set of blocks found within a file on the disk.
The distinction between the page and its component blocks is important,
which is why the dotted lines divide up the page. A 4096-byte page in
memory is likely represented by eight 512-byte disk blocks (which are, most
likely, merged back together by the drive, but we'll pretend that isn't
happening).
![[Second diagram]](/images/ns/kernel/DirtyPageBug2.png)
![[Third diagram]](/images/ns/kernel/DirtyPageBug3.png)
![[CherryPy]](/images/ns/cherrypy.png)
