LWN Weekly Edition
Leading itemsSecurity
Kernel development
Distributions
Development
Linux in the news
Announcements
->Multipage format
This page
Previous weekFollowing week
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
LWN.net Weekly Edition for June 8, 2006Behavioral standards in the free software communityThe GNOME community has recently started a discussion on the adoption of a code of conduct for community members. While a number of people clearly think that such a code makes sense, others are just as clearly uncomfortable with the idea. The free software community is traditionally an open and unregulated group. Its members are concerned with quality of contributions and inclusiveness; there is relatively little interest in conduct rules, and an active dislike for self-appointed enforcers and attempts to exclude potential contributors. So the number of projects with written behavioral codes is relatively small.Such codes do exist, however, whether or not they are written down. Anybody who doubts this fact may want to ponder on the likely fate of a developer who attempts to contribute plagiarized code. But other standards clearly exist as well. Consider, for example, this case: a Debian developer was not only asked to leave DebConf last month, but was removed from the project altogether. A weblog entry from a nearby participant reads:
The difference in values between Ted and the rest of our project
was just too immense. When I was walking out of the room at around
7 in the morning next day my final sentence was "Ted, even if you
spend rest of the Debconf apologizing and making friends, I do not
see a future for you in this project." and the most important was
that Ted and John seemed to agree with me on that
Only two months earlier, Debian went through a protracted debate on whether another developer should be forcibly expelled from the project. In both cases, the issue was not one of plagiarism or other crime; instead, these people are being pushed out for being jerks - for somebody's value of "jerk." Their behavior is said to be so unpleasant, and so off-putting for other members of the project, that their presence is no longer welcome. This is the sort of behavior that the proposed GNOME code of conduct seeks to regulate as well. This proposal contains items like "be respectful and considerate" and "don't be racist." Its supporters are trying to maintain a GNOME community which is pleasant to work in, and which does not drive potential contributors away. They have a point: it has been noted, for example, that female participation in free software projects is often close to zero. That is, as some have observed, below the usual percentage of women in the general population; but it is also well below the percentage of women found working in technical fields. There is a whole population of potential contributors out there who have chosen not to be a part of the free software community. One very possible reason for their absence is the sort of behavior encountered on mailing lists, at conferences, and in other places where the community gathers. Perhaps, if standards of behavior were higher, more people would choose to participate. (Then again, the problem could be elsewhere: Richard Stallman chimed in with a claim that the use of the term "open source" may be the real reason why women chose not to participate. This particular line of reasoning has not attracted a large following, however). Alan Cox points out that the issue is a little broader:
I'd be wary of pursuing just the "women in GNOME" issue, because
many of the same things put off far more than just women. Running
around shouting "pants off" is not, for example, very compatible
with the Japanese cultural expectations.
One can, without great difficulty, make an argument that, as the free software community "grows up" and tries to expand beyond its "western white male geek" stereotype, it should look harder at how its members behave. If one contributor is sufficiently unpleasant to repel the participation of numerous others, then perhaps the community truly is better off without that person. So maybe the community truly does need to be prepared to expel people who are too difficult to be around. Codes of conduct might just make sense. But consider an episode from just over three years ago, when a prominent developer (let's call him "X" for the moment) was stripped of his commit privileges and kicked out of an important project. One of the people involved in this action justified it with these words:
What X has done is among the most low-class, unprofessional,
and tactless things I have ever experienced in my professional
career.... Bottom line, in my opinion, is that what X did
is unacceptable on its face and he deserves to be held accountable
for it. So he's out.
This looks like a clear application of a code of conduct; somebody behaves badly, and is booted from the project. Nothing to complain about. Except that X, in this case, was Keith Packard, who was busily trying to reform the XFree86 project. That project's decision to exclude Keith turned out to be fatal; XFree86 still exists - it even put out a release in May - but nobody cares anymore. This episode highlights the dangers of behavioral codes. They can be used as a way of silencing people who have something inconvenient to say, but sometimes those people need to be heard. Codes of conduct can evolve into a sort of stifling "political correctness" where people become afraid to express their thoughts. The creation of such an environment will suck the life out of a project more quickly than any number of unpleasant people. The community as a whole may well want to think about how people interact, and how that interaction can be made more pleasant and more globally inclusive. Behavior which is rude, sexist, racist, or worse runs counter to our values (one hopes), and it makes us weaker. So discussions of how we wish to treat each other and how we can avoid pushing away people who could make our community richer are worth having. But we must work toward that goal without silencing our more outspoken members; sometimes they are saying something we should hear, even if it makes us uncomfortable.
How clean must the room be?The discussion on what features should be merged into the 2.6.18 kernel has begun (see this week's Kernel Page for the details). One item which was mentioned is the acx100 driver, which has been sitting in the -mm tree for some time. This driver works, is useful to a broad community of users, and appears to be entirely acceptable to the kernel developers who have reviewed it - except for one little problem.This driver, it seems, was developed by reverse engineering a binary-only driver released by TI for the 2.4 kernels. Reverse engineering is not a problem in itself, as long as due care is taken to avoid copying any code from the non-free driver. The normal way of taking due care is to employ a "clean room" technique: the person who does the reverse engineering work writes a document describing how the hardware functions, but does not write any code. Instead, another developer, who has never looked at the original driver in any way, writes the new driver based on the information in the document. This approach shields the developers from any charges of copying code, since they have never seen the code in question. The acx100 driver was not developed in this way; instead, the people who did the reverse engineering went on to implement the new driver directly. Nobody has alleged that these developers copied any code in this process. But the process they used opens the door to such charges in the future. So the code is seen as being tainted, even though it is probably entirely legitimate. This taint has been enough to keep the driver out of the kernel. One kernel developer objects to this course of events, calling it excessive:
I disagree there (not speaking for any company just for myself
here): the "clean room" thing is ONLY a USA thing, and is not even
required in the USA. It is a "we want to be extra safe in the USA"
thing only.
He goes on to say that, if the developers can certify that they copied no code, and especially if the work was done outside of the USA, the driver should be able to go into the mainline kernel. Others disagree, however, noting that "being extra safe" is no bad thing. The SCO case has shown how disruptive a copyright-based challenge to the Linux code base can be. Linux has, by all appearances, come through that challenge looking even better than it did before; the kernel code truly is clean. What a shame it would be to merge code which ends up bringing on another lawyer storm and ruining the kernel's hard-won clean bill of health. Sad though it may be, leaving out the driver might be the better choice. Still, there is a lingering issue here: which laws should be allowed to control which code is accepted into the kernel? By many accounts, the acx100 driver would pass muster in Europe; it is U.S. laws that are of concern. But the laws of, for example, Haiti, Egypt, and Georgia have not been consulted. Complying with laws across the entire planet would be a tall order. Conflicts with laws on, say, spectrum use, surveillance capabilities, or "piracy prevention" in various parts of the world seem increasingly likely. Steering a global operating system through this maze will be an interesting challenge.
The UK Parliament on DRMThe All Party Parliamentary Internet Group is an organization in the UK which "exists to provide a discussion forum between new media industries and Parliamentarians for the mutual benefit of both parties." It is open to members of the House of Commons and the House of Lords; its actual makeup (in terms of party representation and such) is not entirely clear. This group decided to have a hard look at the interaction of digital rights management (DRM) schemes and copyright law. To that end, they received written input from dozens of groups on all sides of the copyright dispute and listened to a large number of interested people. The result of all this work is a report [PDF] and a series of recommendations.This group shows some signs of having actually understood the problem - or parts of it, at least. A reading of the full report is recommended for those who are interested in the issue. For everybody else, here is a set of select quotes. To start with, the group does not buy the notion that DRM schemes will always be easily overcome.
In the future it must be expected that TPMs [technical protection
measures] will rely more and more
upon specialist hardware functionality and that some systems will
prove to be extremely complex to overcome and to develop generic
evasion technology for. It would therefore be unwise to base public
policy upon a continuation of the situation that TPMs are
relatively easy to overcome. It may well be that propping up
technical measures with legislation will become entirely
irrelevant. Equally, assuming that egregious problems caused by
TPMs can be addressed by just `breaking into the system' may become
unrealistic. (¶ 21).
So the "speed bump" view of DRM does not necessarily apply into the future. Often, the discussion at the political level appears to have lost track of what copyright is for. So it is somewhat refreshing that this group has not forgotten entirely:
Copyright is generally understood to be a trade-off. The creator of
copyright material is given a monopoly on exploiting it for a
period of time. Currently for a new song or book this is until the
creator dies plus 70 years. At the end of this period, the created
work enters the public domain and may be exploited by anyone. This
scheme is intended to ensure that there are incentives for
creators, without creating an indefinite monopoly....
However, should all available versions of the material be protected by highly effective TPM systems, it may prove impossible, when the copyright expires, for the exploitation to occur because the material will remain inaccessible except via the monopolistic TPM system. (¶ 32-4). The report goes on, however, to dismiss this concern by claiming that "all available versions" of any given work are unlikely to go under DRM anytime soon. The authors may find themselves surprised by the ambitions of the entertainment industry. At least some of the costs of DRM are understood:
From a completely different perspective, Intel told us that it was
important that the legal infrastructure does not inhibit technical
innovation and they feel that the `trade-off' should address
this as well! As an example, they pointed out that there were no
portable video jukeboxes on the market just devices capable of
video downloads or playing consumer recordings because it was
against the DVD consortium rules to create a portable device.
(¶ 49).
Alternative licenses from the Creative Commons and elsewhere are touched upon:
Several of the rights-holders were rather negative about these
licenses, suggesting that the creators and performers did not
always understand what they were "giving away forever" and how it
could affect an artist's ability to enter into an exclusive license
at a later stage in their career. Although artists should naturally
consider these matters, we suspect that these licenses are clearer
than many media industry contracts. (¶ 71).
The report's authors seem to believe that the worst DRM-related problems will be addressed in the market. But, they say, fully-informed consumers will help to bring that about:
Because, as we have observed, consumers expect to copy CDs, we
believe that all CDs should in future come with a prominent label
saying, "you are not permitted to make any copies of this CD for
any reason"... The prominent label should add, when appropriate,
"and if you try to make a copy, you should note that we have tried
very hard to ensure that you will fail". Doubtless, even clearer
and more accurate wording is possible....
For some types of content the labelling will need to warn the user, "you cannot access some parts of this DVD without a working Internet connection to enable us to record your identity", or "your playing of this song may be recorded in marketing databases in foreign countries". (¶ 100-102). There is also some discussion of what happens if a DRM-using vendor goes out of business or changes policies. The potential loss of an individual's media collection is raised, but the possibility that valuable material could be lost to society as a whole is not. There is little patience with DRM code which ignores users' commands, hides itself, or endangers the host system:
[W]e recommend that OFCOM publish guidance to make it clear that
companies distributing TPM systems in the UK would, if they have
features such as those in Sony-BMG's MediaMax and XCP systems, run
a significant risk of being prosecuted for criminal actions.
(¶ 118).
The authors received input from a number of groups related to free software, but the bulk of that input appears to have been boiled down to about two sentences. The lack of free DVD players is mentioned, as is the effect of governmental DRM mandates. The report claims, however, that no DRM mandates are in view in Europe; evidently broadcast flags and anti-circumvention laws don't count. In general, the needs of the free software community were either not understood or not seen to be important. So, in the end, the APIG report is not all that one might have hoped for. Still, this document shows a higher level of understanding of the issues than can be found in many other government venues. Let us hope that it is a sign of progress in the right direction.
Security New security releases for Firefox and ThunderbirdSecurity vulnerabilities in the Firefox browser and Thunderbird mail client are scary. Both tools are widely used, exposed to arbitrary data from the Internet, and used with important (and confidential) information. A widespread exploit has the potential to affect large numbers of people in highly unfortunate ways. So, whenever the Mozilla Project fixes a set of vulnerabilities, it's worth paying attention.The recently released Firefox 1.5.0.4 addresses a fairly long list of vulnerabilities. Some of the most significant of those (the ones rated "critical") are:
There are also several vulnerabilities which are not considered to be quite as frightening, but which are still in need of fixing. Thunderbird 1.5.0.4 is also out, with its own vulnerability list. Only one of these is deemed critical: a double-free error on an invalid VCard which appears to be exploitable. It is worth noting, however, that Thunderbird uses much of the Firefox code base for rendering HTML, so it can also suffer from Firefox's vulnerabilities. So, in particular, if a user allows the execution of JavaScript in incoming mail (an especially bad idea which is not the default behavior), most of the Firefox vulnerabilities listed above are also exploitable in Thunderbird. There is another common theme found in all of the Firefox vulnerabilities: they can all be mitigated by turning off JavaScript. The sad fact is that executable content seems to be a hard thing to get right; it is an ongoing source of vulnerabilities in almost every context where it can be found. So it is not surprising that many people simply turn off JavaScript entirely. It is unfortunate that so many web sites are inaccessible to browsers running without JavaScript, forcing security-conscious users to enable a problematic feature they might prefer to do without. (See the LWN vulnerability entry for distributor updates addressing these problems. As of this writing, the list of updates is discouragingly short, with only Slackware and rPath getting fixed out within the first couple of days after disclosure).
New vulnerabilities evolution: denial of service
mozilla products have multiple vulnerabilities
mysql: SQL injection vulnerability
rug: remote command execution
spamassassin: arbitrary command execution
xmcd: insecure file permissions
Updated vulnerabilities awstats: missing input sanitizing
binutils: buffer overflow
blender: integer overflow
busybox: insecure password generation
bzip2: race condition and infinite loop
ktools: buffer overflow
cherrypy: information disclosure
cpio: arbitrary code execution
vixie-cron: privilege escalation
cscope: buffer overflows
curl: heap-based buffer overflow
Cyrus-SASL: DIGEST-MD5 Pre-Authentication Denial of Service
dia: format string vulnerabilities
dovecot: information disclosure
firefox: multiple vulnerabilities
Foomatic: Arbitrary command execution in foomatic-rip
freeradius: authentication bypass
gdb: multiple vulnerabilities
gdm: improper file permissions
gedit: format string vulnerability
grip: buffer overflow
gzip: arbitrary command execution
ImageMagick: heap overflow vulnerability
ipsec-tools: denial of service
kdebase: local root vulnerability
kdelibs: kate backup file permission leak
kernel: multiple vulnerabilities
kernel: multiple vulnerabilities
kernel: netfilter memory corruption
kernel: information disclosure
libextractor: heap-based buffer overflows
libgadu: memory alignment bug
libgd2: buffer overflows in PNG handling
libpam-ldap: authentication bypass
libpng: heap based buffer overflow
libtiff: buffer overflow
libtiff: denial of service
libxml2 - arbitrary code execution
libxml2: multiple buffer overflows
lynx: arbitrary command execution
lynx: denial of service
mailman: denial of service
mpg123: buffer overflows
MySQL: logging bypass
mysql: information leaks
nagios: buffer overflow
nbd: arbitrary code execution
ntp: uses wrong gid
openmotif: buffer overflows
OpenSSH: double shell expansion
perl: setuid vulnerabilities
php: multiple vulnerabilities
phpbb2: missing input sanitizing
phpbb2: multiple vulnerabilities
phpMyAdmin: multiple vulnerabilities
postgresql: SQL injection
pound: HTTP Request Smuggling Attack
Py2Play: remote execution of arbitrary Python code
quagga: multiple vulnerabilities
quake: buffer overflow
rsync: integer overflow
scorched3d: multiple vulnerabilities
shadow-utils: mailbox creation vulnerability
squirrelmail: multiple vulnerabilities
sudo: vulnerability via scripts
texinfo: temporary file vulnerability
tiff: denial of service
tin: buffer overflow
typespeed: buffer overflow
unzip: long file name buffer overflow
w3c-libwww: possible stack overflow
xine-lib: buffer overflow
X.Org: buffer overflow
xpdf: buffer overflow
xpdf: denial of service
xpdf: integer overflows
xzgv: heap overflow
Page editor: Jonathan Corbet Kernel development Brief items Kernel release statusThe current stable 2.6 kernel is 2.6.16.20, released on June 5. This one contains several fixes for serious problems; none of them look immediately security-related, however.The current 2.6 prepatch is 2.6.17-rc6, released on June 5. There are enough fixes here that Linus decided to do one more -rc release. Details can be found in the long-format changelog. No patches have been merged into the mainline repository since -rc6, as of this writing. The current -mm tree is 2.6.17-rc6-mm1. Recent changes to -mm include improved force feedback support in the input driver and a large number of patches related to the locking validator.
Kernel development news Quote of the week
The older policy was to get stuff roughly right, merge it into a
tree then beat on it. Now everyone is blocking anything that is the
slightest imperfect which makes it impossible to add anything large
to the tree because it will *never* be perfect before a merge and
hack session and it will never be perfect in everyones eyes...
Perfection is the enemy of progress and of success. We risk moving back to the case we got into in 2.4 when merging got so hard that most vendors shipped kernels bearing no relationship to the "upstream" tree. Probably worse this time as there is no common "unofficial" tree like -ac so they will all ship different variants and combinations. -- Alan Cox
What's not going into 2.6.18The 2.6.17 development cycle is coming to an end, with the final release likely to happen before the middle of June. So, naturally, the attention of the kernel developers is turning toward the 2.6.18 cycle. As a way of encouraging thought on what should happen then, Andrew Morton has posted a 2.6.18 merge plan summary describing how he expects to dispose of the patches currently sitting in the -mm tree. There has been occasional talk of doing a bugfix-only kernel cycle, but it's clear that 2.6.18 won't be that cycle - there are a lot of patches tagged for merging.The features which are expected to be merged are interesting, but they are best discussed once they hit the mainline repository; until then, their fate remains uncertain. So, for now, suffice to say that 2.6.18 will likely include an S/390 hypervisor filesystem, a number of memory management patches, some software suspend improvements, a new i386 hardware clock subsystem, some SMP scheduler improvements, the swap prefetch patches (maybe), priority-inheriting futexes, a rework of the /proc/pid code, a number of MD (RAID) improvements, a new kernel-space inotify API, and a bunch of code from subsystem trees which does not appear in -mm directly. As is usual, a great deal of code will be flowing into the mainline for the next release. It can also be interesting to look at what will not be merged. From Andrew's posting, the following big patch sets are likely to be held back:
All of this is subject to change when the merge window actually opens. Developers are making cases for specific patches; Ingo Molnar is asking for reconsideration of the generic IRQ and lock validator patches, for example. Watch this space in the coming weeks to see what really happens.
Putting a lid on USB powerKernel bugs are bad news. Among the worst bugs are regressions - situations where a once-working system breaks after a kernel upgrade. The kernel developers have been taking an increasingly hard line against regressions; patches which break working systems will usually be reverted, even if those patches fix other problems. The idea, as pushed by Linus, is that once a system works, it should continue to work into the future.As it happens, a number of USB users have found that, on upgrading to 2.6.16, their systems do not work anymore. But, in this case, this "regression" is not seen as such by the developers and is not likely to change. This issue is a good demonstration of the sort of tradeoffs which operating systems developers must make. USB ports can supply power to the devices plugged into them; this power is sufficient to drive many devices, as well as totally unrelated items (such as USB-powered LED lamps). There are limits to the amount of power which can be supplied, however. USB devices will communicate their maximum current draw to the host, which can then decide whether it has the capacity available or not. If sufficient power is not available, the device will not be allowed to configure itself and operate. There are many rules in the USB specification on how power configuration should work. One of those applies to unpowered USB hubs - the ones which lack a power supply of their own. The total current drawn by an unpowered hub cannot be allowed to exceed what the host can supply; in particular, the USB specification limits devices on unpowered USB hubs to 100 mA of current. Even if only one hub port is in use, that single port is limited to that value, despite the fact that a larger draw should work in that situation. Prior to 2.6.16, the Linux kernel did not actually check power requirements before configuring devices. With 2.6.16, however, any device whose stated maximum power requirement exceeds 100 mA will not be allowed to configure itself on an unpowered hub. Thus, devices which worked in that mode in earlier kernels now fail to operate; not all users are entirely pleased. The argument has been made that, since these configurations almost always work in the real world, the kernel should not be shutting them down now. The fact is, however, that running hardware outside of its specifications is always a dangerous thing to do. Often one will get away with it, but sometimes things can fail badly. A fairly large class of USB devices are mass storage devices; the consequences of power-related problems with these devices could include corrupted data and damaged hardware. These are not consequences which the USB developers wish to inflict on their users, so, instead, they refuse to operate devices out of their specifications. To the developers, the fact that some previously-working hardware now fails to operate is not a regression. It is a bug fix, with the kernel finally performing some due diligence which should have been happening all along. They do not intend to change this behavior. As it happens, it is possible to convince the kernel to override its good sense and configure the device anyway. It is not easy, however. Essentially, the steps are this:
Needless to say, this sequence of steps is not entirely easy - and it must be repeated each time the device is plugged in. For those who are comfortable writing udev rules, this configuration change can be automated without too much trouble. Perhaps the desktop environments will eventually be made smart enough to detect this situation and offer (with suitable scary warnings) to override the kernel for specific devices. But it might just be better to buy a powered hub or plug the device directly into the host.
SMPniceA great deal of work has gone into making the Linux scheduler work well on multiprocessor systems. Whenever it appears to make sense, the scheduler will shift processes from one CPU to another in order to keep all CPUs equally busy (in an approximate sense), but, since moving a process is expensive, the scheduler tries to avoid unnecessary moves. SMP performance was problematic on early 2.6 releases, but it has been reasonably solid for the last couple of years.There is one situation, however, where the current scheduler does not work as well as one would like. Imagine a simple system with two processors. If two CPU-bound processes, each running at normal priority, are started on this system, the scheduler will eventually run one process on each CPU. If two niced (low-priority) processes (also CPU-bound) are then started, one would normally expect the scheduler to ensure that those processes get less CPU time than the normal-priority processes. If the processes are distributed such that one normal-priority and one low-priority process end up on each CPU, that expectation will be met; the low-priority processes will get a relatively small amount of CPU time. It is just as likely, however, that both normal-priority processes will end up on the same CPU, with the two low-priority processes on the other. In this case, the two normal-priority processes will be contending for the same CPU, while the low-priority processes fight for the other. As a result, the low-priority processes will get as much CPU time as the others, their reduced priority notwithstanding. That is almost certainly not what the user had in mind when the process priorities were set. The problem is that the scheduler looks only at the length of the run queue on each CPU, without taking priorities into account. So, in either case above, the CPUs appear to be equally busy, and no redistribution of processes will occur. To fix this problem, the load balancing code must be made to understand that not all running processes are created equal. A solution can be found in the "smpnice" patch set, implemented by Peter Williams with input from a number of other developers. The smpnice code changes the load balancer so that it does not just look at run queue lengths. Instead, each process is assigned a "load weight," which is derived from its priority. When load balancing decisions are made, the scheduler compares total load weights rather than the length of the run queues. If a load weight imbalance is detected, the scheduler will move a process to bring things back into line. If the imbalance is large, high-priority processes will be moved; when the imbalance is small, however, a low-priority process will be moved instead. The basic idea makes sense, but this set of patches has been a long time in development. The scheduling code is full of subtle heuristics which are easily upset. So early versions of the smpnice patches caused benchmark regressions and ran into a number of difficulties. For example, a processor running a very high-priority process will tend to appear to be the most heavily loaded, with the result that load balancing no longer occurs between other processors on the system. This problem was fixed by ignoring processors which have no processes which can be moved. Some load balancing heuristics which would move high-priority processes were broken, resulting in suboptimal scheduling decisions; now, if a process would have the highest priority on the new CPU, it is considered first for moving. Various stability problems, where processes would oscillate between processors, have also been ironed out. With all of these fixes applied, the smpnice code appears to be stabilizing, with the result that it might just make it into the 2.6.18 kernel. That should improve life for people running multiple-priority workloads on SMP systems.
Patches and updates Kernel trees
Core kernel code
Development tools
Device drivers
Documentation
Filesystems and block I/O
Memory management
Networking
Architecture-specific
Security-related
Miscellaneous
Page editor: Jonathan Corbet Distributions News and Editorials The ROCK Linux Mission StatementThe ROCK Linux distribution has new Mission Statement, even more recently revised. "After 10 years of ROCK, we felt it's about time ;)." There is a new roadmap too.ROCK Linux is one of the oldest projects that provides a Linux Distribution Build Kit. That is, ROCK Linux provides the tools you need to create a customized distribution from source packages. The Crystal ROCK target ISO image is available for those who want a quick start and it is used as a test case for ROCK Linux. One part of the mission statement is to test and guarantee functionality of the basic packages, including Crystal ROCK. This includes issuing security advisories and maintaining errata documents. The ROCK Linux Build System uses shell scripts to keep it easy to modify the build to your requirements. Support is provided for Alpha AXP, ARM, HPPA-RISC, IA-64, MIPS, PowerPC, Sparc, x86 and x86_64. According to the roadmap ROCK developers are working on hal/dbus integration, udevtrigger/udevsettle integration into bootdisk and /etc/initscript, hotplug rules for udev, and more for the next release. A new installer will be in the works after that. While there has not been a new release of ROCK Linux for some time, one is planned for the near future. So check out the ROCK Linux Manual and build the distribution that's right for you.
New Releases Xandros Releases 64-bit Xandros ServerXandros has announced that the Xandros Server now supports 64-bit processors from Intel and AMD. Support for Intel® EM64T and AMD64® processors will be provided to Xandros customers at no additional charge.
Ubuntu 6.06 LTS releasedIt's official: Ubuntu 6.06 LTS (once known as "Dapper Drake") has been released. Click below for the full announcement, which includes download information and a summary of new features. Kubuntu 6.06 LTS and Xubuntu 6.06 are also available.
SUSE Linux 10.1 Live DVD availableThe SUSE Linux 10.1 Live DVD is available for download now.
Fedora Core 5 Re-Spin ReleasedThe Fedora project has made new Fedora Core 5 "Re-Spin" disc images available. "The Fedora Unity Project is proud to announce the release of DVD ISO Re-Spins of Fedora Core 5. These ISOs are based upon Fedora Core 5 and all updates released as of May 23rd, 2006. They are available for i386 and x86_64 architectures as of Wednesday, May 31st, 2006 via BitTorrent. The x86_64 Re-Spin is currently available for testing only."
Distribution News Debian 3.0 ("woody") support ends June 30The Debian Project has announced that Debian 3.0, otherwise known as "woody," will be unsupported after June 30. Any remaining woody users probably want to make the jump to "sarge" by then.
Debian IRC Network moves to OFTCIt is official. "Starting with today the Debian IRC host alias irc.debian.org directs to irc.oftc.net maintained by the Open and Free Technology Community (OFTC). An increasing number of online discussions has been taken place in this network already despite irc.debian.org pointing to a different network. In recognition of that, Debian has decided to move the irc.debian.org alias over."
Creation of the debian-publicity listThe debian-publicity team has been created to help create a better public image for the Debian Project. "We held a BoF at DebConf6 about "Representing Debian". We discussed many topics and this mail is not intended as an exhaustive summary (you will have to wait for the video recording to watch the discussion). Instead it's just a notice that things are changing and that you're invited to help us improve Debian's image."
Summary of Debconf i18n/l10n activitiesChristian Perrier presents a summary of the i18n/l10n activities at DebConf. "The work on internationalisation (i18n) and localisation (l10n) at Debconf6 has been particularly interesting and productive. The main topic has been the discussion on l10n infrastructure, both summarizing existing features and services (most of them being summarized in the paper I published along with Javier Fernandez Sanguino) and future features."
GCC 4.1 now the default GCC version for Debian etchThe compilers from GCC 4.1 provide now the default compiler for etch for Ada, C, C++, Objc, ObjC++, Fortran95 and for the Java language. The packages should be in the archive now.
Ubuntu begins Edgy developmentThe initial timeline for Edgy development has been posted. Much of the planning for Edgy will take place at the Paris summit so proposals need to be submitted before then. The deadline for proposing specifications is June 12, 2006.The Ubuntu Hardened team is setting goals for proactive security in Edgy. "There is already a Proactive Security Roadmap, created originally as a Breezy specification but never brought to fruition. The specification for this details several steps that can be taken to reduce the risk of exploitation of existing vulnerabilities. This e-mail contains my suggestions for first steps that should be taken to give Ubuntu users the benefit of largely increased security."
The problem of Firefox in Ubuntu BreezyFor those of you running Ubuntu 5.10 ("breezy"), the following message on security support for Firefox in that release is worth reading. Essentially, the Ubuntu developers are in a bind because the current round of Firefox security fixes is impossible to backport to the 1.0.8 release shipped in breezy, and, in any case, they suspect that security fixes beyond those which have been officially acknowledged are present in 1.5.0.4. So the chances are that breezy users will need to upgrade Firefox to 1.5.0.4. This situation is likely to repeat itself over the lifetime of the current "dapper" release, which will have support (for desktop components) for three years.
Fedora Project Board UpdateA summary of the June 6 Fedora Project Board meeting is available. Among the topics discussed were version control, infrastructure, possibilities for the next FUDCon, Fedora Legacy, the testing project announced at the Red Hat Summit, and more.
rPath releases alpha version of rMakerpath Linux has announced an alpha version of rMake. "rMake is a new tool for building software using Conary in a simple, controlled way. Before rMake, you had to install the right software on your system in order to use "cvc cook" to build a package. With rMake, a fresh clean build chroot is created automatically with everything a package needs to build--and only those items."
New Distributions Report from the "Dzongkha Linux launch"Christian Perrier reports on the "Dzongkha Linux launch". Dzongkha is the national language of Bhutan, a country located between India and China. The Bhutan Department of Information Technology (DIT) has built a complete system with complete support for the Dzongkha language. "The system is based on Linux and more specifically on Debian. It consists of one CD which can be either installed or used as a live CD (the installation system is using Morphix, not D-I which was not ready at that moment)."
Distribution Newsletters Debian Weekly NewsThe Debian Weekly News for June 6, 2006 covers the increased the performance of debtags, the trustability of the web of trust, the end of support for Woody, improving Debian's publicity, Debian Conference 6: hot, spicy and working hard, Debian IRC moves to OFTC, and several other topics.
Fedora Weekly News Issue 49This week the Fedora Weekly News covers Fedora Core 5 Re-Spin 20060523 released, the Fedora Interview Program, Fedora People at Red Hat Summit 2006, news coverage on Red Hat Summit 2006, adding new RPM packages to a fedora DVD, 45 Minutes to a Moodle Education Server, Red Hat Turns Over Testing Tools To Fedora, and several other topics.
Ubuntu Weekly Newsletter - Issue #1The first issue of the Ubuntu Weekly Newsletter looks at a new look for www.ubuntu.com, Dapper release parties, Java in Multiverse, VMware Player in Multiverse, Ubuntu 6.06 LTS released, Kubuntu 6.06 LTS released, Edubuntu 6.06 LTS released, Xubuntu 6.06 released, the Paris Developers Summit, Edgy Eft Ideas and more.
DistroWatch Weekly, Issue 154The DistroWatch Weekly for June 6, 2006 is out. "The long-awaited version 6.06 of the Ubuntu family of Linux distributions dominated the headlines of many open source news sites last week; we'll comment on the release and share our first impressions of the new product. In other news, the second Red Hat Summit, concluded last week, was characterised by the launch of several new initiatives, while the Debian release team has been busy finalising the feature set for the December release of Debian "etch". Also, don't miss our opinion piece about the changing landscape of Linux users prompted by the recent release of the binary-only Picasa photo management software for Linux. Finally, we are pleased to announce that the May 2006 DistroWatch donation has been awarded to LilyPond and Lua."
Minor distribution updates Ark Linux 2006.1-rc2 and Ark Linux Live 2006.1-rc2 releasedThe Ark Linux team has announced the immediate availability of Ark Linux 2006.1-rc2 and Ark Linux Live 2006.1-rc2. "This is the last release candidate of Ark Linux 2006.1, which will be released as soon as OpenOffice.org 2.0.3 and kernel 2.6.17 are released and integrated. The current release candidate includes prerelease versions of those."
dyne:bolic 2.0 codename DHORUBAdyne:bolic has announced the release of dyne:bolic 2.0 codename DHORUBA. "The brand new 2.0 "DHORUBA" release comes out after two years of development and it's a complete rebuild and rewrite of the whole system, it brings new possibilities in customizing the running system and makes it modular and very easy to include new software, much more usable and mantainable than before."
Package updates Fedora updatesUpdates for Fedora Core 5: eclipse (bump for FC5), perl-String-CRC32 (upgrade to upstream version 1.4), texinfo (bug fix), alsa-lib (bug fix), procps (bug fix), policycoreutils (bump for FC5), gnome-media (upgrade to stable upstream version), yelp (upgrade to stable upstream version), hal (patched), gnome-applets (upgrade to stable upstream version), file-roller (upgrade to stable upstream version), pam (upgrade to latest upstream version), sound-juicer (upgrade to latest upstream version), vte (upgrade to latest upstream version), nautilus-cd-burner (upgrade to stable upstream version), gnome-desktop (upgrade to stable upstream version), epiphany (update to 2.14.2.1), eog (upgrade to stable upstream version), gtk2 (update to 2.8.18), glib2 (update to 2.10.3), gnome-session (upgrade to stable upstream version), gnome-screensaver (upgrade to stable upstream version), pango (upgrade to stable upstream version), evolution-data-server (update to 1.6.2), libsoup (update to 2.6.2), evolution-connector (update to 2.6.2), evolution (update to 2.6.2), gnome-games (upgrade to stable upstream version), gnome-themes (latest stable upstream release), gedit (latest stable upstream release), gnome-terminal (latest stable upstream release), totem (latest stable upstream release), gthumb (latest stable upstream release), gnome-utils (update zenity to 2.14.2), gnome-vfs2 (latest stable upstream release), libwnck (latest stable upstream release), control-center (latest stable upstream release), gnome-backgrounds (update to 2.14.2.1), module-init-tools (added blacklist-compat), evolution (fix broken dependencies), evolution-webcal (rebuild for new evolution-data-server).Updates for Fedora Core 4: texinfo (bug fix), procps (bug fix), libbtctl (update for FC4), gnome-bluetooth (update for FC4) Updates for Fedora Extras 5: dia (security fix).
Mandriva updatesMandriva has updated xorg-x11 packages to address a bug with keyboard layouts.
rPath updatesrPath Linux has updated conary (maintenance release), cElementTree (add the turbogears suite), conary again (bug fixes), and booty and mkinitrd (better Xen support).
Slackware updatesThis week the Slackware current change log shows that the linux-2.6.16.19 kernel packages that entered testing on May 31 have already been upgraded to linux-2.6.16.20 kernel packages. Other upgrades include subversion, gkrellm, jfsutils, apache, KDE and more.
Trustix Secure Linux updatesTrustix has fixed various bugs in mrtg and ntp.
Newsletters and articles of interest Customizing Dynebolic version 2 (Linux.com)Linux.com covers the creation of a customized live CD using Dynebolic. "Dynebolic is a live CD distro packed with tools for working with sound and video files. Dynebolic uses the Squashfs filesystem to fit a lot of applications into a small space, along with a speed-tweaked kernel and the tools to perform well on low-end equipment. The upcoming Dyne:II release also lets you add and remove tools to create your own custom version of the distro. Here's how."
Multi Distro is Linux times 9 on a single CD-R (Linux.com)Linux.com takes a look at Multi Distro. "Multi Distro includes nine live CD Linux distributions in one ISO file that you can burn to a single disc. It uses the GRUB boot loader to present the user with a main menu from which they can choose which distro they want to run. By showing you how to make your own live CD composed of multiple live CD distros, Multi Distro packs a big punch."
The Perfect Setup - Ubuntu 6.06 LTS Server (HowtoForge)HowtoForge shows how to set up a Ubuntu 6.06 LTS (Dapper Drake) server that offers all services needed by ISPs and hosters.
My desktop OS: Zeta (NewsForge)NewsForge looks at BeOS based Zeta. "Zeta is based on the Be Operating System (BeOS). I have used BeOS since the free BeOS 5 Personal Edition was released in 2000, and its ease of use, quick boots, and minimal hardware requirements allowed BeOS to take full advantage of my computer, which had a 300MHz Celeron CPU, 64MB RAM, and 3dFX Voodoo 3 video adapter. Unfortunately, BeOS developer Be Inc. disbanded by the end of 2001, leaving an operating system that was unable to have more than 1GB of RAM, couldn't support up-to-date AMD and Intel CPUs without special boot disks, and lacked support for hard drives with more than 80GB of space and newer video cards."
Distribution reviews Review: CCux Linux (Linux.com)Linux.com has a review of CCux Linux. "CCux Linux is a performance-oriented distribution whose main idea is to remove everything that is not i686-related, such as old compatibility packages, and to have everything from the kernel up compiled in the i686 flavor. Last month's release of CCux version 0.9.8 is also an up-to-date distro, having kernel 2.6.16, KDE 3.5.2, and Firefox 1.5.0.2. I found it to be a damn good distro."
Damn Small Linux sneaks up on v3.0 (DesktopLinux)DesktopLinux looks at the first release candidate of Damn Small Linux (DSL) 3.0. "The Damn Small Linux (DSL) project shipped the first release candidate of version 3.0 of its 49.5 MB bootable live CD distribution May 29. The changelog notes nine key feature updates in the new edition, including new sample unc extensions, abiword, cups, and opera852."
Puppy Linux arrives at v2.0 (DesktopLinux)DesktopLinux covers the 2.0 release of Puppy Linux. ""This is a major upgrade from the 1.xx series," the project team said in the release announcement. "How to summarize five months' work? The graphical user interface is much the same, as most work has been on the underlying architecture. In a nutshell, the fundamental architecture and boot-up/shutdown scripts are a total rewrite, from scratch, no relationship to any other distro.""
STX Linux: A second life for older hardware (Linux.com)Linux.com looks at STX Linux on older hardware. "Creator Michael "STIBS" Stibane calls STX Linux "a desktop Linux distribution especially targeted to older hardware." I tested version 1.0 of the Slackware 10.2-based distro on an old laptop with a 300MHz Celeron processor, 80MB of RAM, and a 4GB hard disk. I found this young distro for old hardware has promise."
Ubuntu's Dapper Drake is one impressive Linux distro (Linux-Watch)Linux-Watch reviews Ubuntu 6.06 LTS. "I took the slowest and oldest of my regular test systems, a 120MHz Pentium with a 10GB hard-drive and 64MB of RAM. This system normally runs NT 4.0 for testing older Windows networking. I was able to quickly and easily install Ubuntu Server."
Page editor: Rebecca Sobol Development The current state of the BusyBox projectMy name is Rob Landley, and I'm the new maintainer of BusyBox. BusyBox is a small and simple implementation of a set of standard Linux command line utilities. A minimal system built from BusyBox, the uClibc C library for embedded Linux and a stripped down version of the 2.6 Linux kernel known as Linux-Tiny provides a complete Linux command line environment that can boot in 4 megabytes of ram from less than 2 megabytes of disk space. This makes BusyBox very popular for use in embedded Linux systems. A Linux system built from just six packages (BusyBox, uClibc, Linux, GCC, binutils, and make) provides a build environment that can recompile itself from source code. In its default configuration, the 1.2.x versions of BusyBox will provide at least minimal replacements for twenty-one standard packages: bzip2, coreutils, dhcp, diffutils, e2fsprogs, file, findutils, gawk, grep, inetutils, less, modutils, net-tools, procps, sed, shadow, sysklogd, sysvinit, tar, util-linux, and vim. All of these utilities are provided by a single executable that is less than 1 megabyte in size. BusyBox's "swiss army knife" design is one of its most noticeable space-saving features. One binary file has many symbolic links pointing to it, named for the commands that Busybox replaces. Busybox determines which applet to behave as by examining argv[0] to see which name it was called under. A lot of BusyBox's appeal beyond the embedded world is simplicity. For example, the gnu coreutils version of cat.c is currently 772 lines of C code, while the busybox version is 40 lines of C code. Which one would you rather try to read through and understand, port to a new environment or audit for security holes? BusyBox applets are smaller than other implementations because code size is the primary design goal. Many BusyBox applets are fresh implementations starting from the SingleUnix Specification version 3, with various GNU-compatible extensions added from the man pages as desired. Other applets have been derived from NetBSD or elsewhere, but we constantly rewrite and re-implement everything we feel we can make smaller, simpler, or less memory intensive. This means that existing applets can actually shrink over time. The project has also adopted the rule that any new feature that adds size has a configuration option to remove it at compile time. Building BusyBox is fairly straightforward, the process has been modeled after the Linux kernel build method. The build process involves extracting the source, configuring with a linux-style "make menuconfig" command, then running make and make install. Other make options include: "make defconfig" to enable all standard features, "make allnoconfig" to start with everything disabled, and "make oldconfig" for dealing with previously used .config files. From menuconfig, each applet is independently selectable. Many applets have sub-features that can be disabled to save space. Cross-compiling is regularly tested with targets set to popular embedded processors and the x86-64 platform. Project HistoryBusyBox was started in 1996 by Debian's then-maintainer Bruce Perens, as part of the Debian boot/rescue floppy disk project. In 1999, Erik Andersen saw potential for BusyBox beyond the Debian boot disk, rewrote the project extensively, and over the next few years built an active development community around it. During this time Erik similarly rewrote and built a development community around uClibc. As embedded Linux grew in importance, both projects became more time consuming. After the BusyBox 1.00 release, Erik focused on uClibc (which is still pre-1.0) and handed off BusyBox maintainership to me, I am currently trying to take over the world with it. Taking over the world involves making BusyBox a good choice for use in general purpose Linux servers and workstations as well as its traditional role in embedded systems. For example, our completely rewritten bunzip2 code is not only 1/10th the size of the standard implementation, but also 10% faster. Our udev replacement (mdev) is much easier to configure, and in some cases can be used without any configuration file at all. Our mount command was the first to autodetect attempts to mount image files, so specifying "-o loop" became optional. Space-constrained environments like bootable CDs, or the One Laptop Per Child project could especially benefit from BusyBox. The future goals of BusyBox include making the code even smaller, improving support for systems with no memory management unit, adding a test suite and adding the ability to make standalone versions of individual applets.
System Applications Database Software SQLite 3.3.6 releasedVersion 3.3.6 of SQLite, a C library that implements an SQL database engine, is out. "Changes include improved tolerance for windows virus scanners and faster :memory: databases. There are also fixes for several obscure bugs. Upgrade if you are having problems."
LDAP Software LAT 1.1.3 announcedVersion 1.1.3 of LAT, the LDAP Administration Tool, is out. "This release is the 4th of the 1.1.x development cycle which will eventually become v1.2. If you need a stable release stick with the 1.0 branch."
Mail Software Apache SpamAssassin 3.0.6 is outVersion 3.0.6 of Apache SpamAssassin is available. "3.0.6 fixes a remote code execution vulnerability if spamd is run with the "--vpopmail" and "-P" options. If either/both of those options are not used, there is no vulnerability."
Apache SpamAssassin 3.1.3 is outVersion 3.1.3 of Apache SpamAssassin has been announced. "3.1.3 fixes a remote code execution vulnerability if spamd is run with the "--vpopmail" and "-P" options. If either/both of those options are not used, there is no vulnerability. There was also a fix for the userstate directory and prefs file not being created."
Printing Debugging SNMP Printer Detection Problems (CUPS)The folks at the CUPS printing project have published a tutorial on debugging SNMP-related printing problems. "The new SNMP network printer detection functionality in CUPS 1.2 sometimes exposes problems in vendor SNMP or IPP implementations. If you are experiencing long delays in loading the CUPS web interface administration page, or if you don't see your printer listed, the following instructions will help you to diagnose those problems and/or provide important feedback to the CUPS developers so that we can correct problems and improve the SNMP backend in future releases."
Web Site Development mnoGoSearch 3.2.39 announcedVersion 3.2.39 of mnoGoSearch, a web site search engine, is out. See the change history document for details.
Plone 2.1.3 releasedVersion 2.1.3 of the Plone web development platform has been released. "Although they didn't manage to quite time to sync up with the Ubuntu Dapper Drake release ;-), it's very exciting to report the release of Plone 2.1.3, which bundles up four months of bug fixes, usability enhancements and performance tweaks."
Desktop Applications Audio Applications Instability of Ardour 2.0 solved, 6 weeks of effort pays off!A tough bug has been fixed in Ardour, a multi-track audio recording application. See the problem report for details. "Sometimes when you write a complex piece of software like Ardour you are faced with a series of high level, interesting and complex design questions. Unfortunately, its also true that at other times you will be faced with problems that exist at the deepest levels of the software and are often trivial in their extent yet major in their impact. Such has recently been the case with Ardour 2.0, which would not run with any reasonable stability when built with recent versions of the GTK+ GUI toolkit. One Ardour developer (and user), Sampo Savolainen, spent more than 6 weeks debugging this, and just recently got to the bottom of the problem. The error was a single line of code in GTK itself, and manifested in Ardour only because we made a call to a function that was never actually needed."
Data Visualization Grace 5.1.20 releasedVersion 5.1.20 of Grace, a WYSIWYG 2D plotting tool for X11 and Motif, has been announced. Changes include a new SGN() function, changes to the tick spacing, and bug fixes.
Desktop Environments GNOME 2.14.2 Released (GnomeDesktop)GNOME 2.14.2 has been announced. "This is the second release in a series of point releases for the 2.14 branch. Come and see all the bug fixing, all the new translations and all the updated documentation brought to you by the wonderful team of GNOME contributors! While development has started on the Gnome 2.15/2.16 road, work on the stable branch continues to make it even more solid."
GARNOME 2.14.2 is outRelease 2.14.2 of GARNOME, the bleeding edge GNOME distribution, is out. "This release incorporates the GNOME 2.14.2 Desktop and Developer Platform, fine-tuned and updated with love by the GARNOME Team."
GNOME Software AnnouncementsThe following new GNOME software has been announced this week:
KDE 3.5.3 Released (KDE.News)Version 3.5.3 of the K Desktop Environment (KDE) has been announced. "The KDE Project today announced the immediate availability of KDE 3.5.3, a maintenance release for the latest generation of the most advanced and powerful free desktop for GNU/Linux and other UNIXes. Unusually for a maintenance release, new features were implemented due to the long release cycle of the eagerly-awaited KDE 4. Stability and speed were also improved, along with increasingly complete translations in 65 languages." See the release announcement for more information.
KDE Commit-Digest (KDE.News)The June 4, 2006 edition of the KDE Commit-Digest has been announced. The content summary says: "Kopete 0.12 is released after 10 months of development. Usability fixes in RSIBreak and experiments in amaroK. Common KOffice color management initiative - "pigment" - started. User interface optimisations in Adept package manager. KDE 4 changes: DCOP is finally removed from trunk/. The KDE 4 icon theme, Oxygen, is imported into KDE SVN."
KDE Software AnnouncementsThe following new KDE software has been announced this week:
Electronics Covered 20060530 is outRelease 20060530 of Covered, a Verilog code coverage analysis utility, has been announced. Here are the changes: "Contains FSM state/arc coverage info in GUI. Contains assertion coverage info in GUI and ASCII output files. Contains GUI syntax highlighter. Allows multiple files to be merged with a single call to the merge command. Lots of bug fixes/enhancements/documentation updates."
XCircuit 3.4.24 releasedStable version 3.4.24 of XCircuit, an electronic circuit drawing program, is available with build improvements.
GUI Packages OpenExposition 0.2.0 releasedVersion 0.2.0 of OpenExposition has been announced. "OpenExposition is a library aimed at automatic generation of user interfaces. The programmer only needs to specify what parts of the code need to be exposed to the user, and OpenExposition does the rest. Currenly, OpenExposition allows access to variables (either directly or through a pair of set/get methods), and class methods. It can construct the user interface graphically (using either the multi-platform FLTK library or Cocoa on Mac OS X), programatically (through Python), and aurally (using the speech synthesis and recognition capabilities on Mac Os X). The 0.2.0 release introduces a separation of C++ and Objective C files, so that C++ only environments don't have to deal with Objective-C++ .mm files. Also, the automatic GUI construction has been slightly improved."
Imaging Applications GIMP 2.3.9 Development Release (GnomeDesktop)Development Release 2.3.9 of the GIMP has been announced. "GIMP 2.3.9 is the latest and hopefully one of the last development snapshots on the way to version 2.4 of the GNU Image Manipulation Program. The source code can be downloaded from ftp.gimp.org. There are quite a number of changes, all listed at developer.gimp.org."
Interoperability Wine 0.9.14 releasedVersion 0.9.14 of Wine has been announced. The list of changes includes: Better MS/RPC compatibility, Many fixes to Direct3D shaders, Several improvements to the header control and Lots of bug fixes.
Wine Weekly NewsletterIssue #315 of the Wine Weekly Newsletter has been published. Topics include: Summer of Code, Picasa, MacOS X Audio & Video Drivers, 1.0 Tasks, How Are We Doing?, WoW - Breakage, Updated Fedora Packages, and Shell Integration and RSS Feed.
Office Suites KOffice 2.0, The Vision (KDE.News)KDE.News looks ahead to KOffice 2.0. "KOffice is working on its future, one based on KDE4. KOffice is starting new initiatives with libraries like Flake and Pigment that are going to be used for all KOffice applications. For the users of KOffice those changes are invisible until the 2.0 previews actually start to appear some months from now. Therefore the KOffice crew wants to show you their goals of what KOffice 2 is going to look like."
OpenOffice.org NewsletterThe May, 2006 edition of the OpenOffice.org Newsletter is online with the latest OO.o office suite articles and events.
Miscellaneous SeaMonkey 1.0.2, Firefox 1.5.0.4 and Thunderbird 1.5.0.4New versions of SeaMonkey, Mozilla Firefox and Mozilla Thunderbird have been released with security and stability fixes. Here's the SeaMonkey announcment and release notes. Here's a look at the security issues fixed in Mozilla Firefox 1.5.0.4 and the release notes. Here is the security summary and release notes for Mozilla Thunderbird 1.5.0.4.
Languages and Tools Caml Caml Weekly NewsThe June 6, 2006 edition of the Caml Weekly News is out with new Caml language articles.
JSP Working with the Google Web Toolkit (O'ReillyNet)Robert Cooper looks at the Google Web Toolkit in an O'Reilly article. "GWT is, in essence, a JavaScript generator. The interesting thing is what this JavaScript is generated from: Java. GWT takes Java code written against a special API and converts it into browser-runnable Ajax code. If that weren't enough to make it cool, it also includes a test harness that will execute the Java code inline with a test browser, allowing you to step-through debug, profile and unit test your Ajax front end in your favorite IDE or at the command line."
Perl FEAR-less Site Scraping (O'Reilly)Yung-chung Lin uses Perl to automate the reading of web pages in an O'Reilly article. "Imagine that you have an assignment that you need to fetch all of the web pages of a given website, scrape data from them, and transfer the data to another place, such as a database or plain files. This is a common scenario for data scraping tasks, and CPAN has plenty of modules for this job. While I was developing site-scraping scripts, retrieving data from some sites of the same type, I realized that I had repeated many identical or very similar code structures..."
PHP PHP OpenID 1.1.0 releasedVersion 1.1.0 of the PHP OpenID library is out with bug fixes.
PHP Standalone OpenID Server 1.0 announcedInitial release version 1.0 of the PHP Standalone OpenID Server is available. "This server uses the JanRain PHP OpenID library (version 1.1.0). The server supports admin-controlled and public account creation, Yadis discovery, and Simple Registration. MySQL is required."
PHP Yadis 1.0.0 releasedVersion 1.0.0 of the PHP Yadis library is out with an XRDS-processing fix.
Python Dr. Dobb's Python-URL!The June 7, 2006 edition of Dr. Dobb's Python-URL! is online with a new collection of Python article links.
Ruby Ruby Weekly NewsThe June 4th, 2006 edition of the Ruby Weekly News looks at the latest discussions on the ruby-talk mailing list.
Tcl/Tk Dr. Dobb's Tcl-URL!The June 5, 2006 edition of Dr. Dobb's Tcl-URL! is online with new Tcl/Tk articles and resources.
XML Converting Between XML and JSON (O'Reilly)Stefan Goessner discusses the conversion between XML and JSON (JavaScript Object Notation) in an O'Reilly article. "More and more web service providers seem to be interested in offering JSON APIs beneath their XML APIs. One considerable advantage of using a JSON API is its ability to provide cross-domain requests while bypassing the restrictive same domain policy of the XmlHttpRequest object. On the client-side, JSON comes with a native language-compliant data structure, with which it performs much better than corresponding DOM calls required for XML processing. Finally, transforming JSON structures to presentational data can be easily achieved with tools such as JSONT."
Page editor: Forrest Cook Linux in the news Recommended Reading OpenOffice.org virus debunked by experts (NewsForge)NewsForge looks at claims that a macro virus could infect OpenOffice.org. "The next day, the OpenOffice.org home page posted an acknowledgement of the story, adding that the project was consulting with Kaspersky Lab about the virus. On June 2, OpenOffice.org issued a press release, downplaying the story. "This is a known risk with any capable macro language," the release explained, adding, "This 'proof of concept' virus is not new information, and does not require a software patch."" Here is the press release from OpenOffice.org.
The State of Linux 2006 (Tom's Hardware)Tom's Hardware has published a "state of Linux" article. It is lengthy, but still on the superficial side. "In days gone by, the personification of Linux might have conjured up the image of a hotshot college kid full of half-baked ideas and sharp edges. But that college kid has now graduated into the business world, and unleashed his furious entrepreneurial spirit. Today, Linux has a sharper, more refined edge than before, and has branched out into private, public, enterprise and governmental sectors. Linux also spans all manner of hardware platforms, and serves an incredibly wide variety of purposes."
Trade Shows and Conferences KDE 4 Multimedia Meeting exceeds expectations (NewsForge)NewsForge covers the KDE 4 Multimedia Meeting. "KDE members associated with the desktop environment's major multimedia components and marketing efforts met last weekend in Achtmaal, The Netherlands, at the KDE 4 Multimedia Meeting (K4M, previously known as K3M). Attendees discussed goals for their projects and wrote a fair amount of code that promises exciting improvements in KDE 4's multimedia components. K4M attendees hailed from 15 countries and four continents. While open source software is often developed by individuals separated by thousands of miles who communicate through email and IRC, airfare and lodging expenses may be justified for short bursts of fantastically productive meetings such as this."
Ploneability 06 Reportby Paul Everitt covers the 2006 Ploneability conference. "Romilly gave the talk of the day. She explained the motivation that led to the DCMS project and the way they approached the RFP and tender process. She then gave an insider's view of how the selection process worked, including a series of graphs showing the actual results of their grading criteria on various vendors and software packages. Romilly explained how open source was added to the list a bit late in the process and how it challenged the traditional ways to do a vendor selection. Romilly also described the features of "Enterprise Plone", the package that resulted from the Oxfam project. (Note: The Oxfam project can take some or all of the credit for CMFEditions, Kupu, LinguaPlone, CompositePack, and more.) This was a remarkable session. Very rarely do you get the honest scoop on the crucial details. The audience, I think, realized that they were getting wildly, wildly valuable information, and engaged in a serious discussion."
Red Hat goes all out for developers (Linux-Watch)Linux-Watch reports on the Red Hat Summit, and looks at the newly launched 108 site. "If you were looking for new products at Red Hat Inc.'s second annual Red Hat Summit, you came to the wrong place. But, if you were interested in bigger and better development tools, you came to the right place. Red Hat CEO Matthew Szulik introduced the company's new open-source developer community Web site, "108," in the show's morning meetings. This new site is intended to help open source developers share resources; build and fetch code; find and meet other developers, interact with them; and collaborate with them."
Day 2 keynotes at the Red Hat Summit (NewsForge)NewsForge covers Eben Moglen's Red Hat Summit keynote address. "He began by bringing up some of the bogeymen falsely associated with free software by those whose business interests are threatened by it: politics and profits. Much of the rest of his talk skewered, refuted, or demolished those mythical memes. He mentioned the decor in the reception area at Red Hat, which he noticed during a visit there in 1999, not long after the company had gone public. He noted a plaque on the wall which read, "Every revolution begins as an idea in one man's mind.""
Red Hat Summit sessions educate, stimulate (NewsForge)Joe Barr reports on the Red Hat Summit. "My only real problem with this year's Red Hat Summit was trying to decide which talks to attend whenever I wasn't writing, eating, or partying. The problem wasn't finding sessions I was interested in, but deciding which one to attend when several appealing talks were happening at the same time. Here's a brief recap of what I learned in three of the 90 break-out sessions available to attendees."
Companies Lenovo backpedals on Linux (Linux-Watch)Lenovo is the company that bought IBM's ThinkPad line. Linux-Watch takes a look at the company's waffling stance on Linux. "Last week, the world's #3 computer vendor, Lenovo, was saying "We will not have models available for Linux, and we do not have custom order, either. What you see is what you get. And at this point, it's Windows." Whoops! Now, Lenovo is going back as fast as it can on its "no Linux here" stance."
Novell shares fall on drop in Linux-products revenue (CentreDaily.com)CentreDaily.com reports on a drop in Novell's stock price. "Novell Inc. stock plunged Thursday after the networking-software maker said second-quarter revenue from Linux products had slipped from the previous quarter. At midday, Novell shares dropped $1.35, or 17.5 percent, to $6.38 on the Nasdaq Stock Market. The amount of the revenue decline was not specified in a conference call held Wednesday after the financial markets closed. ``We're signing a lot of longer-term contracts where the revenue recognition gets pushed out,'' Chairman and Chief Executive Jack Messman said."
SanDisk goes after the iPod iPuppets (CNet)Back in January, LWN predicted that manufacturers of digital audio players would eventually become interested in Rockbox. Now this CNet UK article suggests that the time has come. "SanDisk is reported to have quietly approached the open source developers behind Rockbox, a free operating system for MP3 players. The company is said to be interested in porting the Rockbox software to its e200 player.... Not only would a Rockbox port earn SanDisk credibility with grassroot geeks, but the software offers a number of appealing features, including support for nearly every codec going."
Red Hat completes JBoss acquisition (Linux-Watch)Linux-Watch reports that Red Hat's acquisition of JBoss is final. "Starting immediately, JBoss has become a division of Red Hat. Customers will now have access to a single, "proven" global production support organization that can service both Red Hat and JBoss customers, in addition to procuring JBoss offerings through Red Hat's established global channels, according to Red Hat. [Red Hat Senior VP of Enterprise Solutions Timothy] Yeaton said that "JBoss will be an autonomous division. There will be no office closings and we're keeping the entire core JBoss team.""
Legal Death by DMCA (Spectrum)IEEE Spectrum has an article on the costs of the DMCA and related legislation. There will be few surprises here for most LWN readers, but it is a good, comprehensive summary. "Now, in an even more vexing situation, U.S. entertainment companies are successfully spreading the copyright code changes established by the DMCA around the world. Laws similar to the DMCA now exist in Japan, Australia, and much of Europe. At least nine additional countries, including Chile, Guatemala, and Singapore have also been pressured to enact DMCA-like laws as part of a devil's bargain with U.S. trade negotiators, who say the copyright change is necessary to secure free trade pacts with the United States that would govern all sorts of commerce. And in Europe, the body charged with defining the European digital television standards is mixing in content-protection obligations, responding yet again to pressure from major U.S. movie studios."
Denmark's Resolution on Open Standards (Groklaw)Groklaw looks at Denmark's resolution on open standards. "Groklaw member elhaard sends us a bit more detail about the Danish resolution that passed yesterday. We put the story in News Picks. The motion is called "B 103" and all material about it (even Parliament transcripts) can be found at the Parliament's home page. It's only in Danish, though. So he helps us out again, translating the last publicly shown version of the resolution."
Adobe yet to explain why no PDF in Microsoft Office (ITWire)Here's an ITWire article on the strange removal of PDF support from Microsoft's Office product. "Adobe has reportedly demanded that Microsoft charge users for the PDF facility in Office 2007. Microsoft has refused and intends to offer the PDF facility as a separate free download. Meanwhile the word on the street is that Adobe is preparing to mount an antitrust case against Microsoft in Europe, where the software giant is unpopular with regulators. The whole episode appears to border on the ludicrous, given that Microsoft Office is compatible with the open source look-alike Open Office.org 2.0, which enables documents to be saved as PDF files." That which hits Office today may hit OpenOffice.org tomorrow.
Interviews Gilles Caulier (People Behind KDE)The People Behind KDE talks with Gilles Caulier. "How and when did you get involved in KDE? My first KDE contributions were French GUI translations from 2001 to 2002. I have translated Konqueror, KMail, KDevelop and K3b. KDE was the first graphical environnement that I have used under Linux. Because I'm originally a win32 developer, I was immediately charmed by the KDE project's looks and goals." (Found on KDE.News)
Jon 'maddog' Hall on FOSS in the developing world (NewsForge)NewsForge interviews Jon 'maddog' Hall. "One way of getting the price of the OLPC down is through high-volume manufacturing. This is why Mr. Negroponte wants to have millions of these laptops committed. I would guess that most of these would be manufactured in Taiwan or China, not in South Africa. Therefore, millions of rand (dollars, dinar, yen) will flow into China, not stay in South Africa. On the other hand, there are lots of computers being upgraded by banks and companies. They will be "throwing out" good system boxes that would run Linux perfectly fine, and which could be donated to a local charity. By gathering these boxes up, pulling their components apart, reconfiguring them, installing Linux on them, and selling them for $100 -- or even $50 -- you could give a person a good job. "
Interview: Mark Shuttleworth (451 Group)The 451 Group (an analyst operation) has published part 2 of an interview with Ubuntu founder Mark Shuttleworth. "Ubuntu is in my mind the emergence of a second generation of Linux platform or Linux distribution. [It's] built not on the idea that Linux should look like proprietary software, but that Linux should really deliver what free software can deliver. I should put that slightly differently: Ubuntu aims to deliver the real promise of free software, and that spans a number of different areas. First, we believe that the software should be highly functional and reliable, because we do believe that free software has a potential to be better quality software, that the processes that actually produce the software results in software that is better understood, better scrutinized, better tested, and so on. So we try to integrate all those processes into Ubuntu itself."
Daniel Silverstone (Behind Ubuntu)Behind Ubuntu interviews Canonical programmer Daniel Silverstone. "What are your plans for Edgy? I'll be back on the Launchpad team working on various features for Launchpad to make the developers of Ubuntu have an even better time of it. We have Personal Package Archives in the pipeline -- those will allow people to have their own small apt-get/synaptic compatible archives served by, and built by, Launchpad. And we have many and various other things to work on, including the much vaunted derivative distributions support. Life will be exciting for distro developers in the dapper+1 cycle. With a shortened development cycle the extra tools we can provide for them will be all the more important."
Resources GNU grep's new features (Linux.com)Michael Stutz investigates some new features added to the GNU grep utility. "If you haven't been paying attention to GNU grep recently, you should be happily surprised by some of the new features and options that have come about with the 2.5 series. They bring it functionality you can't get anywhere else -- including the ability to output only matched patterns (not lines), color output, and new file and directory options."
Manage Apache Download Speed And Traffic Limits With mod_cband (HowtoForge)Falko Timme shows how to throttle Apache2 bandwidth with mod_cband in a HowtoForge article. "In this tutorial I will describe how to install and configure mod_cband on an Apache2 web server. mod_cband is an Apache 2 module which provides bandwidth quota and throttling. It solves the problem of limiting users' and virtualhosts' bandwidth usage. The current version can set virtualhosts' and users' bandwidth quotas, maximal download speed, requests-per-second speed and the maximal number of simultanous IP connections."
Management Guidelines on Migrating to Open Source/OpenData Standards Software, by Carlo Daffara (Groklaw)Groklaw presents Guidelines on Migrating to Open Source/Open Data Standards Software by Carlo Daffara. "The main drive for a successful migration to Open Source and Open Data Standards software(OS/ODS) always starts with a clear assessment of the IT landscape, a clear vision of the needs and benefits of the transitions and continual support. The differences of OS development models and support may require a significant change in the way software and services are accounted for and procured, and in general a shift of responsibility from outside contractors to in-house personnel."
How to suspend and hibernate a laptop under Linux (Linux.com)Linux.com looks at suspend and hibernate on a Linux laptop. "Many people prefer working with laptops instead of desktops for the flexibility they offer. Some of them would also like to switch to a free and open source operating system like GNU/Linux and have their laptop do all the things that proprietary OSes offer, such as suspending their laptops. Several distributions try to make this work out of the box, but knowing what's under the hood always comes in handy, particularly when something goes wrong and needs fixing. Let's take a look at how to suspend and hibernate your laptop under Linux."
Reviews GNU Radio Opens an Unseen World (Wired)Wired looks at the GNU Radio project. "Building a general radio that can receive and transmit, and attaching it to a software system that can fill in the gaps of what we normally think of as radio, is kind of like the Enterprise's deflector dish: Give engineering 20 minutes and it can do anything the captain needs to move the plot along. "
Discovering your network with Netdisco (Linux.com)Linux.com takes a look at Netdisco. "Netdisco is built on open source packages such as Perl, various Perl modules, Net-SNMP, PostgreSQL, Mason, Apache, and mod_perl. One of its key components is the SNMP::Info Perl module, which Baker also wrote. See the project's requirements page for other modules Netdisco requires to run properly."
First look: Xara Xtreme LX (Linux.com)Linux.com reviews Xara Xtreme LX. "In short, Xara LX's interface is highly contextual and sometimes unconventional. While few of its interface characteristics are unique, the combination of so many of them is. New users may find themselves scrambling at first, or resorting to the online help or company Web site more often than they are used to. But once they understand the basic logic -- and learn to pay attention to the status bar at the bottom of the window -- they will quickly find Xara LX's editing window both refreshingly uncluttered and outstandingly efficient."
Miscellaneous Consortium brings open source database projects together (NewsForge)NewsForge looks at the Open Source Database Consortium. "The OSDBC was formed at the first Open Source Database Conference (OpenDBCon) last year in Germany. According to Zak Greant, who was the lead organizer of OpenDBCon and who with Arjen Lenz of MySQL helped get the OSDBC off the ground, the idea behind the consortium is to share information between the various open source database projects that can help improve "the entire class of free software/open source database solutions.""
New additions to Jeremy Allison's Low Point ArchiveThree new articles have been added to the Samba project's collection of articles by Jeremy Allison. New titles include: "We are the champions...", "Unintelligent Design" and "Why we fight".
Page editor: Forrest Cook Announcements Non-Commercial announcements Carrier Grade DebianOSDL has sent out a press release stating that the Debian Project has registered its compliance with the Carrier Grade Linux specification. "The Debian CGL implementation is the first step in plans to build a telco-Debian custom distribution that will tout full CGL compliance with all primary requirements and the majority of roadmap items."
EFF: Appeals Court Corrects Dangerous Web Privacy RulingThe Electronic Frontier Foundation has sent out a media release concerning a web privacy ruling. "San Francisco - The 11th Circuit Court of Appeals has corrected a dangerous lower court ruling that threatened Internet privacy. In doing so, it preserved the privacy of password-protected websites as well as the right to read public sites. The decision followed the arguments made in an amicus brief filed by the Electronic Frontier Foundation (EFF)."
LPI Announces Haansoft Corporation as Korean AffiliateThe Linux Professional Institute has announced its new Korean Affiliate, Haansoft Corporation. "This initiative in Korea represents a key component of LPI's Regional Enablement Initiative in North East Asia. We are delighted to welcome Haansoft to our worldwide team of Master Affiliates. They are the final cornerstone in our efforts to promote Linux professionalism within CJK (China, Japan, and Korea).""
Commercial announcements Autodesk announces Web Map Publishing SoftwareAutodesk, Inc. announced its Autodesk MapGuide Enterprise 2007 product. "Following its groundbreaking contribution to the open source community, Autodesk, Inc. today announced the commercial version of its open source web mapping platform, Autodesk MapGuide Enterprise 2007. This certified version features all of the benefits of the open source version, plus additional quality assurance, technical support, connectivity to additional data sources including Oracle and SQL Server, as well as integration of numerous third-party components."
Digium Announces Major Upgrade to Asterisk Business EditionDigium has announced Asterisk Business Edition B.1, the first major upgrade of its Asterisk Business Edition, the professional-grade version of Asterisk. "The upgraded release includes enhanced security and scalability provided by Ranch Network's Asterisk security code, speech recognition capabilities through the LumenVox Speech Engine, text-to-speech applications through the Cepstral Text-to-Speech System and a customized Linux distribution to simplify installation. Asterisk Business Edition B.1 will also feature built-in support for Intel Dialogic Products and Aculab Prosody X cards."
Jive Software Announces Open-Source of Spark IM ClientJive Software, Inc. has announced the release of its Spark IM Client application under the LGPL license. "Spark, based on the open IETF standard XMPP (Jabber) protocol, is a cross-platform, Java-based Client optimized for use with Jive Software's Open-Source XMPP Wildfire Server. With this announcement, all of the applications an organization needs for a complete EIM ("Enterprise Instant Messaging") system are available under Open-Source licensing terms from Jive Software."
NetEqualizer Announces Business Relationship With CompUSAAPConnections, Inc. has announced a partnership with CompUSA, who will be selling their NetEqualizer appliance. "The NetEqualizer is a plug-and-play bandwidth control appliance that is flexible and scalable. NetEqualizer's unique technology differs significantly from other appliances. It uses "behavior shaping" which dynamically and automatically controls network flow for the best WAN Optimization. It is built on Linux and works with all operating systems."
Novell's second quarter resultsNovell has announced its second quarter financial results - a small profit. "During the second fiscal quarter 2006, Novell reported total Open Platform Solutions revenue of $57 million, which was up from $20 million in the year ago period. Total Open Platform Solutions included $46 million from sales of Open Enterprise Server (OES), up $38 million year-over-year, and $10 million of revenue from Linux Platform Products, up 20 percent year-over-year."
Red Hat launches "Mugshot"Red Hat has launched a site called Mugshot; it is the company's attempt to get into the "social networking" sphere. It's invitation-only for now. Mugshot is said to be an entirely open source project, but the "download" link is currently missing. There is a FAQ and a developer site with a bit more information.
Sun Announces JBoss as Newest Member to NetBeans Partner ProgramSun Microsystems, Inc. has announced the latest member of its NetBeans Partner Program, JBoss. ""We are endorsing the NetBeans IDE because of JBoss and Sun's mutual dedication to simplifying development of standards-based Java EE applications. We will work closely with the NetBeans team to develop a plug-in for the NetBeans IDE that provides developers with the tools for doing development with JBoss Application Server. NetBeans has great momentum in the market because it consistently delivers innovative solutions to enhance developer productivity," said Marc Fleury, founder and President of JBoss, Inc."
TI Announces DaVinci(TM) Technology Development KitTexas Instruments Incorporated has announced its new video software development kit. "Continuing to streamline the creation of innovative digital video systems, Texas Instruments (NYSE: TXN) (TI) today announced a new digital video software development kit based on DaVinci technology. The new software development kit incorporates exceptional software integration and system visualization technology with a full Linux operating system to integrate and tune complex systems quickly and efficiently."
Wind River adds support for AMD Opteron-Based Sun Blade ServerWind River Systems, Inc. has announced its plans to support the Sun Microsystems Netra CP3020 Opteron processor ATCA blade server. "For customers who require a commercial-grade CGL solution on the industry's fastest, densest and most reliable blade server, Wind River is working on an optimized port of its Platform for Network Equipment, Linux Edition environment for Sun's Netra ATCA blade server and AMD Opteron processor-based Sun Netra blade systems."
New Books Enterprise JavaBeans 3.0 - New from O'ReillyO'Reilly has published the book Enterprise JavaBeans 3.0, Fifth Edition by Bill Burke and Richard Monson-Haefel.
No Starch Press releases "The Art of RAW Conversion"No Starch Press has published the book The Art of RAW Conversion by Uwe Steinmueller and Jürgen Gulbins.
Resources Bridging the Digital Divide in Health: The Role of FOSS (LinuxMedNews)LinuxMedNews mentions the availability of a presentation on open-source health software. "According to Molly Cheah on the openhealth list Dr. Joan Dzenowagis has a presentation entitled Bridging the Digital Divide in Health The Role of Free and Open Source Software: "Dr. Joan Dzenowagis, is based at the World Health Organization, where she is Project Manager of the United Nations Health InterNetwork, led by WHO. This initiative is one of the four initiatives of the UN Millennium Action Plan launched by Secretary General Kofi Annan in September 2000."
Linux Brochure Project (LBP) version 1.3.0 releasedVersion 1.3.0 of the Linux Brochure Project is available. "LBP is a GPL'd Linux advocacy and publicity project which documents key Linux information in a standard-size brochure (two sides of a single letter- or A4-sized sheet of paper which is Z-folded into the six mini-pages of the brochure)." See the change log for details.
Florian Mueller's software patent battle book downloadableFlorian Mueller has released his book No Lobbyists As Such - The War over Software Patents in the European Union under the Creative Commons noncommercial, no-derivatives license; it is available as a large PDF file. "On 377 pages, Mueller tells the story of the legislative process that ended in July last year with a landslide vote of the European Parliament against a proposal for a software patent directive."
Linux Gazette #127Linux Gazette has released the June 2006 edition of the newsletter, with articles on FVWM, Knoppix, amaroK, and much more.
Event Reports A summary of the LSB meetingKDE hacker Aaron Seigo was at the recent Linux Standard Base meeting in Boston; he has written up and posted a summary of what happened there. "There was discussion of a common packaging API for "installanywhere"/"installshield" type apps to use. At first there was pushback from distros but by the end after open and frank discussion and Ian's graceful handling of things there seemed to be consensus that this was a possibility indeed. Still a long ways to go on it, but something ISVs are pushing for and something that, with enough flexibility, the OSVs agree they can probably provide. This is not to be a replacement for .deb or .rpm or apt-get/yum/etc but a way for OSVs to provide simple hooks to register files with the package management system in an OS-neutral way."
Samba eXPerience 2006 archiveThe materials from the Samba eXPerience 2006 conference are available. "In our archive you will find impressions and information gathered at the samba eXPerience 2006: all talks as OGG audio files, slides from the conference as PDF, pictures in JPG format".
Calls for Presentations Akademy 2006 Call for Participation (KDE.News)KDE.News has published a call for participation for the 2006 KDE World Summit (aKademy). "The aKademy 2006 conference team is calling for contributors to present their work and vision to the KDE community. This years' conference takes place at Trinity College, Dublin, Republic of Ireland, from September 23rd to September 30th. All presentations will be held during the "KDE Contributors Conference" event on September 23rd and 24th." Abstracts are due before Friday, June 30.
The Firebird Conference 2006 CFPA call for papers has gone out for the Firebird Conference 2006, submissions are due by July 31. "The fourth Firebird Worldwide Conference will take place at the Andels Hotel in Prague, Czech Republic from the 12th November 2006 until 14th November 2006. The Andels Hotel is a new 4-star hotel, which is located very close to downtown, just across the river."
Upcoming Events LinuxWorld UK 2006 announcedLinuxWorld 2006 UK will showcase the latest technology, debate the use of Open Source in business, touch on virtualisation and give advice on Linux-based mobile phones. LinuxWorld Conference & Expo will take place at Olympia 2, 25-26th October 2006.
Events: June 8 - August 3, 2006
Miscellaneous Sun updates the DLJ FAQIn response to questions which have come up, Sun has written a new version of the FAQ for the Distributor's License for Java. "Of course, if Sun clearly says in an FAQ that it's okay to do something (and we haven't made a blatant typographical error), we're not going to sue you -- even if one could make a clever legal argument that the license doesn't permit it. We believe in simplicity and transparency, and pledge to work diligently with the community to achieve those objectives." The language on shipping alternative Java implementations has been clarified as well.
Page editor: Forrest Cook
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||