I’m just in the process of converting a multi-user system to a Xen DomU. It was running on a stand-alone Fedora Core 5 i386 system and I want to run it on a Fedora 7 DomU under a CentOS 5 Dom0 on an Opteron system. The first stage of the conversion was to copy an image of the Fedora Core 5 system and make it a DomU under CentOS. I had some problems getting a Fedora Core 5 Xen kernel to boot so I installed a 64bit CentOS 5 kernel with the Fedora Core 5 user-space and surprisingly everything worked. I had expected to have problems with kernel modules, but everything just worked! I had expected that the 32bit modutils would be unable to load 64bit modules, but things just worked. The first stage was to have the old server NFS export /home and have it mounted by the Xen DomU, this worked well for about a week. The next step was to move the data on to the new server. My first attempt was to have the Dom0 running the filesystems and NFS exporting them to the DomU but this caused an OpenOffice error “Error saving the document Name: General Error. General input/output error.“. So having 32bit Fedora Core 5 with a 64bit Cent OS 5 kernel NFS mounting from a 32bit Fedora Core 5 system works well, while mounting from a 64bit Cent OS 5 system fails. If anything I would have expected better results from having the same version of the kernel on NFS client and server. The next issue is whether a 64bit Fedora 7 system in a DomU can NFS mount the data from the Cent OS 5 kernel with Fedora Core 5 user-space. If not it’ll make testing the Fedora 7 upgrade significantly more painful than it might otherwise be. If only we had a network filesystem for Unix that supported POSIX semantics.

Share This

I'm happy to admit it -- I have a fear of flying. Strangely enough, though, my anxiety levels peak somewhere between 3 hours and 30 minutes before the plane takes off. Once we depart the terminal building, I'm fine -- the takeoff, cruise, and landing hold no fear for me, in fact I rather enjoy it. When I have the money and time, I plan on learning to do it for myself. The thing that does freak me out, though, is aptly described in this article. The idea that I could possibly suffer a similar fate, or worse, concerns me. The arbitrary nature of security screenings, and the fact that I cannot, through my own actions, ensure that I will not suffer at the hands of a security service when I have done nothing wrong really scares me.

Over the last few months I've been hacking on (yet another) image viewer for GTK+, using the hot new GVFS library (go Alex!) for asynchronous file handling and GtkImageView because I'm lazy. It's got a pretty lean interface at the moment and is fairly fast in use. My goal is to use it on my Zaurus for reviewing images from a CF card in the field, so performance is quite important to me. As the primary users are photographers, filenames are not shown in the interface (just thumbnails). There is a lot of work left to do, but I've used 0.1 for some time now. The source is being developed in a Bazaar branch at http://burtonini.com/bzr/katachi. I've just tagged a 0.1 release, a tarball of which is here. You'll need to build GVFS from git, and GtkImageView from svn, sorry. :) NP: Closes Volume 1, Boards of Canada

Some prominent debian-legal posters frequently make use of disclaimers like IANAL (I Am Not A Lawyer), TINLA (This Is Not Legal Advice), IANADD (I Am Not A Debian Developer). While this helps to avoid misunderstanding about the value of their opinions, I propose that a new disclaimer is used where appropriate: IAAM (I Am A Moron).

Dear Lazyweb, does anyone know a small web calendar which has a web frontend and does not rely on a database server? It should save it’s data directly into .ical (or .ics) files so I can fetch and alter them with a desktop calendar application too. I don’t need fancy features like multi user support or the ability to publish calendars, I just want do see and edit my calendar/todo stuff when I’m not at home and have the .ical saved on a centralized (my) server to make it available for desktop calendar software. For privacy reasons it has to run on my own server.

I won’t re-explain in great length why I think it’s good to endorse the concept of Debian Maintainers. I have been enough involved in the debian-vote discussions (and the previous debian-project discussions). I would just like to remind everybody that we elected sam to see changes and progress on many areas. We haven’t seen many results yet, but I know that sam has been working hard and I’ve been helping him as much as I can on the problem of our DSA team (one day I might blog about it or even start a GR if the situation continues to not improve despite the numerous efforts that we’ve put into it). Here we have a concrete proposal for a change, and I believe a change for the better. But just like for every change, people have fears: they fear people who only care about technical excellence and not too much about philosophy, they fear that the quality level will drop, they fear that nobody will care about NM afterwards, etc. It’s legitimate to have concerns, to express them and to discuss them. But we should not let them take us over or we’ll end up abandoning all initiatives that are required to evolve and adjust to our moving environment. We need to encourage people who are ready to try out new things. In cases where it’s not entirely clear how the situation will evolve, it’s better to try out and react accordingly instead of doing nothing and hoping that people will wait us. When we do things while hoping for the best, the worst won’t come up true so easily. Have faith in our future.

What’s the single biggest advancement Linux has brought to the industry? It’s an interesting question, and one that in my opinion has a very simple answer: Package management—or, more specifically, the ability to install and upgrade software over the network in a seamlessly integrated fashion—along with the distributed development model package management enabled. It used to be that operating systems were big, monolithic products, and applications were big, monolithic products you put on top of them. If you wanted to deploy, say, a web application, you sourced the middleware stack (which itself was probably several big products too), you sourced the operating system, and you (often painfully) had to integrate the two yourself (or pay a big company lots of money to do it for you). These days, you increasingly just “apt-get install whatever“. In this world, where does the operating system end and the application begin? The line is increasingly blurred—for when applications are deployed using an OS facility, seamlessly integrated with the OS itself, is the result an application or a feature of the operating system? In fact, in a very real way, all software looks to become part of the operating system—or, at least, this has certainly been the trend in the Linux world. What does this shift mean to the industry? For one thing, those of us that build operating systems as monolithic products have to change—it’s what users expect, and with a componentized operating system rather than a wad of stuff, it becomes far easier to push new innovations out into the marketplace and generally evolve the OS over time. Indeed, refashioning Solaris as a “distro” is the essence of Project Indiana—and package management is the key technology that will hold it all together. So, the next time you read about how Project Indiana aims to make Solaris more “Linux-like”, keep in mind that what we’re actually “copying” is the distro model, not Linux itself—which, after all, is a kernel, and has nothing to do with the package management and so forth the distros (you know, like Debian) built above it. This, better than anything else, highlights the opportunity for Solaris: What people really know when they say they know “Linux” is the environment that exists around the Linux kernel—the distro—all of which Solaris can deliver, and more.

It's our second wedding anniversary on Monday, and because Sarah's not been to Napa Valley yet, and because this is probably the last opportunity to spend a bit of quality time away together before the pitter-patter of little feet, we've lashed out for a nice weekend away. We're staying two nights at the Gaia Napa Valley "hotel". It's really nice, but a lot more like a motel in most respects. I really like the environmentally-conscious initiatives they've taken though. I can highly recommend it, and the day spa attached is also excellent. Oh, and they have free wireless, which whilst surprising given how much they charge for things like in-house movies, is also a bonus. It was good enough to make laptop-based VoIP calls with. Today, we drove around aimlessly after our massages, in search of wine tastings (it was handy having a a ready-made designated driver). It seems the wineries here are all into charging for tastings, which in my opinion is a bit of a deterrent (in some cases) to purchasing. The charge varies between $5 and $15. Some wineries seem to refund the cost of the tasting if you make a purchase (which seems like the way to go in my opinion). We stopped for a late lunch at the Rutherford Grill, where I think I've had the most awesomely delicious rack of barbecue pork ribs I've ever had in this country. I cannot recommend that place enough. Apparently their rotisserie chicken is also to die for. We picked up thirteen bottles of wine in our travels this afternoon, so for the first time in ages, we'll actually have something in the wine rack at home. Tomorrow we're going on the Napa Valley Wine Train, which looks like it'll be fun. So now Sarah can say she's seen Napa.

I have just been reading the LinuxWorld Community blog which seems to be mostly Don Marti’s personal blog (currently there seems to be no-one else blogging on that site). One thing that disappointed me is that the theme designer made it look good at a width of 1000 pixels and no other size. At a smaller width the adverts on the right are cut off (more of a problem for the site owner than for the readers) and at a larger width you have a thin column of text in the middle of the screen. A quick test revealed that while my own blog looks good in wide windows it doesn’t work too well in 800 pixel width and gets very bad at lower widths - my blog would be essentially unusable at 640×480 resolution as the text column in the middle (the most important column) is the one that reduces in size. The LinuxWorld blog has a minimum size of 1000 pixels for the scaling so it allows horizontal scrolling in 640 pixel width and remains quite readable. The top entry in a google search for web size stats is Browser News which claims that 12% of web browsers are on 800 pixel wide screens. The next link I found claims that as of January 2007 there are 26% of web users with screens that have higher than 1024×768 resolution and 14% with 800×600. Apart from the first couple of months of blogging my blog has always looked good in screens greater than 1000 pixels wide, but not having it work at 800×600 is a problem. The first thing I did was alter the style.css file for the Blueline theme for Wordpress to use 100% of the display width (not 86%). Wasting 14% of the screen width is not a good thing when using a width-intensive three-column theme. This change made my blog work well in 800 pixel width and be bearable in 640 pixel width. The other change was to use min-width: 700px; in the style.css sections blogtitle, container, and navigation. This means that at 640 pixel width the text column will take more than 1/3 of the screen and should be quite readable (unless the reader has an unusually large font setting). The down-side to this is that if your window width is less than 700 pixels then you will have some horizontal scrolling, but I think that this is an acceptable trade-off. I was forced to confront this issue when talking to a prospective client about the potential for blogs to be used in his business, he loaded up my blog on an ancient windows machine and it didn’t look very good at all, this coincidentally happened a few hours after I had been reading the LinuxWorld blog on a big screen.

Share This

I read with interest Erik Moeller's note about sources on Wikipedia: Wikipedia s core problem is not expertise, it s self-selection. He quotes the following paragraph from the article about Mitt Romney: Romney was sworn in as the 70th governor of Massachusetts on January 2, 2003, along with Lieutenant Governor Kerry Healey. Within one year of taking office, Romney eliminated a 3 billion dollar budget deficit. During this time he did not raise taxes or debt. He also proceeded to end his term with a 1 billion dollar surplus as well as lower taxes and a lower unemployment rate. Erik pointed out that the cited source was the Mitt Romney for president campaign, and then worried about the self-selection of Wikipedia contributors. I think he's on the wrong track. I don't think the sources of Wikipedia articles matter that much, if the text is readable, true, neutral and verifiable. The part that really made me cringe, in the above paragraph, was the awkward construction He also proceeded to end his term... Awful. I've streamlined the sentence to He ended his term with a 1 billion dollar surplus, lower taxes and a lower unemployment rate. As I tried to explained in my unfinished essay on Readers and writers on Wikipedia, I think that as Wikipedians we concentrate far too much on the agenda and rights of contributors, and far too little on the readability and usefulness of the articles themselves. I think WP is going to become more professional when more Wikipedians practice their writing skills than their rule-making skills. We should concentrate on the quality of the output, not on the source of the input. tags: wiki wikipedia erikmoeller mittromney writing

A politician named Ron Paul is running for the Republican party nomination for president. Tech Crunch has an article about his Web 2.0 based campaign which also includes a link to a google interview with him. Here’s the good things about him:

• He strongly defends the constitution and the rule of law, so he’s not a totally bad guy (unlike many of the current politicians who believe that the US president should be able to do whatever he wishes).

He wants to refrain from “helping” other countries with their “defense” - such help from the US has caused most of the wars and terrorism around the world since WW2.

He wants to reduce military spending to 1/3 current levels (he could reduce it to 1/10 current levels and still be able to prevent a combined attack by Russia and China).

He wants to restore liberty.

He seems to be in support of repealing most drug laws - but his statements weren’t clear.

Here’s the bad:

• He wants to remove income tax and give the smallest possible government - no consumer protection laws among other things.

He thinks that hospitals should be run by churches and have no government funded medical system.

He doesn’t want restrictions on pharmacists who refuse to sell certain drugs (IE the contraceptive pill) - but with no restrictions on who can be a pharmacist such things could be bought without prescription even…

Here’s the ugly:

• He claims that guns on planes might have prevented 9-11.

Still, he’s a lot better than any other Republican who seems to be in the running.

Share This

Yes and really proud of it.. David did an awesome work fixing the tons of bugs I have been reporting in past couple of weeks with my super stress testing of the implementation. I have to admit that he was also > this close to scramble the "black choppers" towards my house but that's usually a good sign when I can piss him off this much :) ..because we did beat Xen ;) David implementation of LDOM was merged upstream in about 2 months development. Xen took only 3/4 years? :P Anyway just kidding.. don't take it personal. Xen is a full mature implementation and LDOM still lack functionalities and features but we are getting there very very quickly. For now I am going in vacation for a few weeks with my son and plan to stay away as far as possible from any form of electronic equipment and give David some slack to relax too. Once back I plan to hack my LDOM workarounds to handle better some "features" of the vds partiton checker and complete the tests with exporting single partitions. Thanks to Barton for shipping me a couple of extra disks for my Niagara, I will also be able to test other combos with Nevada and different guest setups. Stay tuned!

Yesterday, a Spanish court decided to ban a sex cartoon of Spanish Royal Family. It was published by a satirical magazine, called El Jueves, which publishes every week cartoons of Spanish Royal Family, among political cartoons, or others talking about different issues. I am not going to argue here if this is censorship or not. I think that freedom has some limits, and if they have been surpassed, people doing that has to be judged. What I want to write about is more related to information and how it flows nowadays. As we have seen here, it is completely impossible to stop some document from spreading around the world in some hours, with hundreds of websites talking or showing it. Call it globalization or Internet. The effect is the same, information flows more quickly than what can be controlled. The measure taken by the court was the seizure of all copies of that magazine. Of course, reaction from other media was to publish the news including the banned cartoon. Also, tens of blogs show it, both in Spanish and in English, which has made that international media and news agencies also got the news, contributing to its spread even more. Soon, a local cartoon, that usually would be only knew by usual readers of El Jueves, has become a worldwide news item, with millions of people looking at it, commenting, republishing. And everything came from a bad choice: the court tried to set fences to information. This issue reminded me what also happened last two days, when waiting for the last Harry Potter's book to be published, it was known that it was yet available in every P2P netwok, and that some people had yet received it at home. Even, today, some newspapers published plot details of the book.

Since quite a while gettext has support for a feature which I was waiting for since ages: --previous. It means that when a string gets marked fuzzy it adds the previous original string as a comment so one is able to see the difference which led to the fuzzy marking. This makes translation of po files much much more comfortable because one can easily find out now what has changed. Let me give you a reallife example:

#: data/core/help.cfg:331
#, fuzzy
#  msgid "race^Mechanical"
msgid "trait^Mechanical"
msgstr "Kriegsgerät"

With out the previous string (in the "# " line) you would propably be puzzled about what has changed because the string gets stripped off the everything before the ^ for displaying it in this case. Though, not all translation tools behave correctly. One of them is unfortunately poedit. It moves the previous string to a wrong place and thus breaks the parsing of the file. A bugreport has been filed about it—but unfortunately it also means that upstream projects that already support (like Wesnoth) it are considering disabling it again because of this. So I wrote quickly a perl script that is able to fix that for you: pofix.pl. It's quite simple, reads from stdin and writes to stdout.
Go and support --previous before your competitors do it and hijack all your translators! ;)

For part of Stage 11, I watched the new Tour live coverage on Sat.1 who bought the German rights. When Sat.1 is busy, Pro7 will cover it. The two stations are owned by the same company, along with Kabel1, N24 and 9Live. The coverage was OK - the same French pictures as everyone else, but fewer extra features than ARD/ZDF. Commentary was a bit pedestrian, but that's like ZDF. I like Eurosport's commentary much more. International Herald Tribune reports that Eurosport's ratings tripled for stage 10 which is unsurprising. Eurosport and Sat.1 both seem to be on the same ~30% of German DVB-T as well as DVB-S. In comments on my last post about this, Thomas asked:

"You don't read German papers, do you?"

No. I've not even tried to buy one since moving to this village.

"I do, and I'm neither outraged nor surprised. It is a fairly logical step in light of the debate and the public reception of the tour, cycling pros, and Team T-Mobile in particular."

Is it public reception? Around 50% of those polled by ZDF disagreed with the decision (according to the IHT link above). Given all the ZDF spin on this, that's shockingly low. Is this driven by the silly debate of Bundestag members, rather than public opinion? (I've still not forgiven them for booting Eurosport off of ZDFvision. CDU seem to like messing ARD/ZDF about.) Are German papers in a feeding frenzy? In some days, they'll move onto football or boxing or something else. Get this in context: it's not like the old scandals where we had pro teams or wives being caught with car boots full of drug kits.

"I'd also bet that T-Mobile will quit as a sponsor."

It didn't seem like that from TV interviews, but I guess they wouldn't say yet. I think if they were going to jump ship, they would have done it after last year's worse problems. AIUI, their contract expires 2010 anyway and I wonder whether all the good publicity from their tour outing in England will help them stay until then.

"Some things belong in pharmacology textbooks and not on TV screens."

Does this mean drugs or incomplete drug tests? ;-)

"If I paid German TV fees, I'd be outraged that this comes that late. But then, I know better and don't have a TV in the first place."

Oh, well! Then I guess nothing would convince you to watch the tour! Philipp Kern commented:

"they did not threaten for a year actually. After the big doping scandal some months ago they explicitly announced that they will drop the Tour de France if a new doping case pops up. Granted, the person in question did dope before the Tour."

We don't know that yet - only one sample has been tested so far and even then, this test is controversial and has been successfully appealed against before. It's only a case. Also, maybe it wasn't the TdF, but here's a comment about ARD in 2006 threatening to drop cycling (scroll to 25.10.).

"The argumentation is that the Tour should not be a contest of the best doping substances like it could have been the last years. But I am probably biased because I don't watch the Tour, or sports in general."

No more biased than ARD/ZDF's producers, it seems. In an interview on itv4, a ZDF producer said they would drop any sporting event with a doping problem like cycling. So, if ZDF have dropped cycling for 1 in 189 participants being accused of doping, then if any footballer is accused of drugs offences, they cannot show any matches involving them. If you want to take football off ZDF, you know what to do... Thijs Kinkhorst reports in "Too much testosterone" that NOS also continues coverage, like our itv. Good on them. Let's applaud any drug cheats getting caught and punished, after we're reasonably sure.

It seems that moving a cat is *really* expensive! We're not willing to consider sending her to a shelter just to be killed, but we're hoping to find someone in Montreal, Kingston or Toronto who can take her and love her.

She's 13 years old, declawed, likes to cuddle up. She can be a bit tempermental, but can be pet with a bit of practice. She's been feeling a bit put-out lately since Leif has been born, so someone willing to love her alot would be really appreciated. She's in good health and doesn't need any special pills or food beyond the usual "older cat" food.

Comments here or jbailey@raspberryginger.com if you're interested or know someone.

Being a good Debian user

Notes: the bulk of this article was written on the 17th; updates were added in later; this article is really long, you might want to read it in more sessions

Debian's arm port uses hardfloat. This means that apps like rrdtool (graph function) take ages to run because there is no floating point unit. In order to make this faster you'll want to use soft-float emulation. But this support needs to be present in all depended upon libs, including libc, which is an ABI incompatible change which would break all binaries. I can't use the yet-in-development-and-unofficial armel port since the machine has to be up and running almost 24/7 and I can't afford downtime.

So what to do?

Well, obviously use another soft-float enable libc, like uclibc, in parallel withe the hrad-float enabled libc. Debian Sid contains uclibc development libs, but building the whole toolchain is a pain. There is no real support in the distro itself and building on the arm machine is kind of out of the question. I tried a little in a debootstrapped chroot on the native machine, but this was a pain and I was stuck tring to figure out how to disable whitles and bells for rrdtool since I didn't needed any of the perl, tcl or python support. So I stopped, went to bed and decided I'll continue the next day (the day I wrote the biggest part of this article). The future looked dark, trying to build a softfloat uclibc rrdtool on a system that wasn't prepared for that and from which softfloat was pulled away somewhere during etch's development stage....

Deciding to go with the competition - native building

From link to link I found out that gentoo has arm-softfloat-linux-uclibc port, among others, so I decided to use that on the target machine (a NSLU2) in a chroot. Well I stumbled on the low computing power, when I tryed to emerge sync the tree. I gave up un that and tried to use emerge-websync. It looked better, but I didn't got too far with this either since the machine ended up being overloaded, with figures varying from 3 to 8 for the load average (all of them).

Deciding to go with the competition - cross building

It was time to bring in the big guns and I decided I was going to crossbuild those binaries, probably statically since it meant lower risk for things to break on the target machine.


Since I observed that gentoo has a nice tool called crossdev which actually uses emerge (the equivalent of dpkg+apt in Debian world) to make the cross chain tool and saw that they have some really good documentation and a development version of an arm-softfloat-linux-uclibc, I decided I could .

So I went on and downloaded the latest stage3 tarball for x86 (so I can have a gentoo system to start with), made all the necessary things and created a gentoo chroot. I emerge sync-ed, updated portage, installed crossdev (following the nice instructions on the gentoo embedded site about the subject). This took a while, but it went like a breeze. I made the necessary arangements to be able to cross build packages (setting SYSROOT, making that nice xmerge script).

As my goal was to make an arm-softfloat-linux-uclibc binary for rrdtool I tried directly to xmerge rrdtool (of course, first just pretended -p).

Finding bugs in the packages

First bug

All went fine until I found freetype which for some weird reason detected the i486-pc-linux-gnu-gcc compiler as i486-pc-linux-gnu (observe the missing trailing -gcc). I looked over the logs and determined that the CC_BUILD environment variable was not set. So exported CC_BUILD=i486-pc-linux-gnu-gcc and xmerged the library.

(While trying to fix this issue I entered #gentoo-embedded on freenode and actually met Yuri Vasilev, whom I had met in Edinburgh, at DebConf. Look for the video about Ligusk if you are interested about his project to make a Debian like distribution based on Gentoo. It was nice to meet a friendly "face" - as much you can say that online.)


I reported the bug (already there is a patch, I haven't tested, but looks ok) and the workaround in the gentoo bugzilla... after creating an account, since I never used that BTS before.

Second bug

Next pain was libart_lgpl whose upstream, for some comfortability reason chose to detect the target type sizes (and basically ignoring inttypes.h) with a small program which was built with the cross compiler which later was supposed to be ran on the host. I don't think is necessary to say that i failed, of course, since the binary was an ARM binary, while the host was an x86 machine. Yupee! not.

Ok, two bugs, no softfloat rrdtool yet. I reported this second bug and tried to work around the issue. Since I didn't really used too much a gentoo system, I wanted to know details and what possibilities I had. I got some really nice tips from "solar" (aka Ned Ludd) on #gentoo-embedded. He pointed out that while building a package one can press CTRL+z, do some stuff, like altering the Makefile.in file in the build directory and then fg back. Ok, cool.

All I need now is somebody with direct access to an arm machine that can compile and run for me the program in question. seanius on #debian-devel was kind enough to do this for me and, to my surprize, I got the same output header file as I got in the host x86 chroot. But that detail is not important, let's just compile that rrdtool. Well, first libart_lgpl...

Ok, I CTRL+Z-ed the build process just after the configure stage ended, cd-ed into the build directory, I tampered with the Makefile.in file and changed that line from

./gen_art_config > gen_art_config.h

into

cp /gen_art_config.h.arm gen_art_config.h

Haha! In your face! Ok, nasty did was done so I fg-ed and went on confident that I will get my hands on that rrdtool very soon. The package build ended succesfully, without any other suprizes, so I went for the graal!


xmerging rrdtool, the bugs don't stop

xmerge -v rrdtool

Bla, bla, bla.... bla, bla, bla, what do you know, there are a few IEEE math function tests in the configuration script of rrdtool. They failed. I don't know why, but I have a feeling that this should be happening on softfloat or even maybe the rrdtool source is not that cross compile aware. I didn't care that much, so I did what I knew best, tampering with an ongoing build.

This time is was a little bit harder to catch since I had to wait for the source to unpack (well, there is a larger frame, but that is the rough timing) and at that moment CTRL+Z the build.

I didn't had much time to waste, so after looking shortly over the tests I realized I should just ignore the error and look for the "failing command" that was interrupting my beloved build. Muhahah!

Thank God for verbose error messages, I could find the place fast and chaged the two "exit 1" statements into two harmless 'echo "Ignoring IEEE math errors"', sic. I had to do this a few times since I got the timping wrong, at some point I got the syntax wrong (at which point I remembered the cp trick I did earlier and saved the modified file in /configure.rrdtool )...

xmerging rrdtool and the 4th bug

After passing past this stage, I got a compilation error which, judging from the command, meant that the linker tried to link the target (arm) binary against the host (x86) libraries.

Oooook, this is not going to stop me! I look at the Makefile.in to try understand why this happened and then realized it wasn't worth it for me to try to fix it the right way. So I cheated once again! Muhaha, I just ran some useful commands which I'll let you feast your eyes to:

ln -sf /usr/arm-softfloat-linux-uclibc/usr/lib/libart_lgpl_2.so /usr/lib/
ln -sf /usr/arm-softfloat-linux-uclibc/usr/lib/libpng12.a /usr/lib/
ln -sf /usr/arm-softfloat-linux-uclibc/usr/lib/libfreetype.so /usr/lib/

Ok, good to go. Of course, I had to stop again the build to copy the "fixed" configure script that ignored IEEE math errors, but that is already history.

And, believe it or not, actually the build succeded. I had a cross built rrdtool using shared libraries built against softfloat ucllibc. No guarantees about its correctness, but it built!

This is when I decided to start writing this article.

Still there are things to do

I will have to do a few things before being happy about the victory:

• check that all the resulted binaries are indeed ARM ELF files, and not Intel x86. It appears the shared libs are already.
• done, they are (checked the next day)
• figure out qpkg (is a utility from portage-utils which seems to be a way to make binary packages) to package somehow the result of this work or maybe just ignore it and use plain cp
• see how I can fit together both the softfloat uclibc binaries and the native debian binaries on the same filesystem, including ld.so configuration...
• but I fear this will be a nightmare, so I might decide to go with static compilation of rrdtool, which I don't think it will be quite straight forward given the experiences describe above; there could be also the size issue to take into account, and since the NSLU2 has only 32MB of RAM, this could be problematic
• I think I'll have to use a statically linked binary after all (note added late, the second day)
  
• see if the rrdtool binary really works and if all the work payed off, performance wise - it should, taking into account what I have heard from wookey during the debconf7 talk about the armel (warning, 73MB ogg file) port
• be happy with the solution I got or wait for the Debian armel port to catch up and switch to that asap
• if I'll have to do the switch I'll probably think of ways of migrating the whole system from arm to armel, and not to reinstall everything; this might prove useful for the whole debian armel port, when people are working on migration plans, since arm will be deprecated in favour of armel

Metro, the free newspaper distributed at train stations, has published an article about the Korenslag television show last Thursday. To my great surprise, they used two photo's to illustrate the article - photo's taken directly from my web site. This without any contact, or without any credit. I've sent them an email expressing my dissent with this and I've asked them to come up with a solution for this situation. If they'd asked beforehand I'm certain that they would have gotten my permission if they'd put a photocredit as they do with nearly every other photo in their newspaper. I'm curious what their response is going to be. Here's a scan of the article, the original photos are here: 1, 2.

Patrick Sinkewitz has tested positive for testosterone, and German public broadcasters ARD and ZDF have instantly canceled reporting on the tour except for more doping "news". The Germans broadcasters are going out of their mind in their witchhunt. Luckily the rest of the world seems more sensible. A.S.O. asks whether they're supposed to stop doing tests if apparently one positive is enough for ARD and ZDF to cancel everything. Manager Luuc Eisenga of the T-Mobile team asserts that newspapers will keep on reporting about business news even if one company is accused of fraud. Dutch public broadcaster NOS says: "We're here to report on what happens in the tour, not to exercise moral judgement over it." I'm happy that I can just continue to watch the tour even if one cyclist crosses the line.