Riku Voipio: QEMU with OpenGL ES acceleration
In the graphics side, the major differences between ARM and X86 systems is that on ARM 3D acceleration is done with OpenGL ES. It is mostly a subset of modern OpenGL used on X86 desktop machines. From QEMU point of view this could mostly be ignored, as OpenGL was mostly used on games and specialist applications. This has now been changing, as desktops and user interfaces have started OpenGL to render graphics. Without acceleration, these user interfaces become slower than slugs crossing a tarpit.For this reason, MeeGo introduced OpenGL ES acceleration support to QEMU. With the lack of easily available MeeGo QEMU images and test setup, I've created a test setup for Linaro 11.05 image.
I ve gotten fed up with 
One nice (and even priceless) feature of Evolution is the vfolders, that allow me to manage the tons of emails in different contexts, wherever that may be located. AFAIK, Gnus doesn t offer any comparable feature. But it seems that the most interesting way to have it is to integrate Gnus with 
As a Debian/Ubuntu user, you re likely to be exposed at some point to an error reported by dpkg. In a series of articles, I ll explain some of the errors that you might encounter.
Some error messages can be confusing at times. Most of the error strings do not appear very often and developers thus tend to use very terse description of the underlying problem. In other cases the architecture of the software makes it difficult to pin-point the real problem because the part that displays the error is several layers above the one that generated the initial error.
This is for example the case with this error of dpkg:
I sponsored the upload of fonts-anonymous-pro prepared by Rog rio
Brito. This fixed-width font is especially designed for people who
write code, for instance by making clear differences between
characters such as O and 0, or I, l and 1.
I fixed a few glitches in various l10n scripts related to D-I (those
tthigns that run daily, for which I receive a daily mail). They were
the consequence of Alioth migration and I omitted to fix them until
now....mumbling every morning about the scripts' noisy output..:-)
I worked on only one bug for samba (doh). This was #631118 which I
forwarded upstream in order to get it fixed in 3.5 series (even if 3.6
is due out soon and will be what we target for wheezy).
I tried to follow the flow of translations/reviews in DDTP for
French. The activity is high, here, with about 10 packages translated
every day (most often packages I target for the team...by using
high-popcon stats). We even had a big bump during the week-end when
Georges Khaznadar (who is very active when it comes at educative
software) initiated the translation of many edu-related packages (many
of which he maintains himself).
That's about it. Quiet week, indeed with more time invested in paid
work, including during my spare time..:-). And also a week-end in our
country house in Normandy, which usually means more gardening than hacking.
I haven t blogged for a while, because I ve been doing so many things that I scarcely had time nor will for it. Among all those things, and during the weekends of the last few months, we have been 
In case you want to know more about all of this (sorry, links are in Spanish):
In brief:
Just been testing the upcoming lintian 2.5.2 vendor-profile branch for operations with packages processed by 
Last week I tried switching a library to Gtk3. The needed changes to the code are available through --with-gtk3. However this is generally not enough. Even if your symbol list doesn't change, the ABI changes implicitly. The library in question had a .symbols file, but that's not enough because the resulting GUI application will bail out at runtime if symbols of both Gtk2 and Gtk3 are found in the same address space. That's mostly because C symbols don't contain any signatures with return types and parameters.
The goal of this lab is to setup a site-to-site IPsec 
The 
I had cause to try and get a core dump from a segfaulting process at work the
other day, and I wanted to figure out if fiddling with
/etc/security/limits.conf was going to do the trick (I didn't) or if I
had to modify the initscript to include a ulimit -c unlimited call.
Of course, on a modern system (>= 2.6.24), one would just take a look at
/proc/PID/limits and get on with life, but unfortunately the
system in question was running 2.6.18, so more fiddling around was required.
I'd found something once before that told me how to do it with GDB, but all I
could find this time around was a 
Conrad Sanderson released version 1.99.5 of 
Due to 
Sam Hartman is a Debian developer since 2000. He has never taken any sort of official role within Debian (that is besides package maintainer), yet I know him for his very thoughtful contributions to discussions both on mailing lists and IRL during Debconf.
Until I met him at Debconf, I didn t know that he was blind, and the first reaction was to be impressed because it must be some tremendous effort to read the volume of information that Debian generates on mailing lists. In truth he s at ease with his computer much like I am although he uses it in a completely different way. Read on to learn more, my questions are in bold, the rest is by Sam.
Raphael: Who are you?
Sam: I m Sam Hartman. I m a 35-year-old software engineer. I am a principal consultant and co-owner of a small consulting company, called 
