In case anyone's interested, here are some notes on the ASUS Eee Box, more specifically the b202 model, Linux edition:

• I use the box as a media center, so I initially wanted to connect it to my 720p HDTV using a DVI/HDMI cable. Unfortunately it's apparently impossible to use the TV's native screen resolution (1360x768) via HDMI, the best you can get is 1280x720, which results in a somewhat blurry image. Worst yet, the HDMI input has an overscan problem, approximately 50 pixels on each side are missing... which means that your GNOME panels will be invisible. I'm not sure if this is caused by the Eee Box or by my TV set but if you absolutely want HDMI, waiting for the b204/b206 model with its built-in HDMI might be a good idea. (In the end, I used my TV's VGA input.)
• It's more powerful than I thought. The Linux version ships with a 160GB SATA hard drive and 2GB of RAM (instead of 1GB for the Windows version) and the Atom N270 CPU is pretty fast. It plays 720p MPEG4 video (such as this file) with lots of CPU to spare, and the quality is really great.
• The optical S/PDIF audio output doesn't work under Linux, as far as I can tell.
• It's extremely silent despite the fan and hard drive.
• The Gigabit Ethernet controller is a nice touch, netperf reports a speed of 611 MBits/s. In practice the drive's speed will be the bottleneck, of course.
• To avoid tearing issues when playing video with Xv, use the Intel Video Overlay adaptor instead of the (default) Textured Video adaptor. (Use xvinfo to get the port number.)
• OpenGL performance isn't great; Compiz with basic effects will run fine, mplayer can play most video files using the gl/gl2 output without frameloss, but games will be slow. (Not that I expected much from the Intel GMA950 anyway...)

All in all I'm pretty happy with the Eee Box. If you have any questions, feel free to email me or leave a comment below.

Yes, it is an empty file! I have just upgraded xorg to the experimental packages. hal does its job, and all devices are automatically detected and configured.
This is actually a great improvement, especially for those who had to fight against the XFree86 configuration file just to get a graphical session working, back in the late 90 s.

The only thing I had to do is creating an /etc/hal/fdi/policy/10-keymap.fdi file with the following contents, so that GDM has a correct keyboard layout (French in my case):

The streams from FOSDEM are live since 2min now, yay!

Updated and more verbose info is available on -project.

To say it mildly, the setup was chaotic, we could only get into the room 30min before our talked started. Which then started 30min late and was recorded at least, as the beginning of Lucas' talk which is still running.

BTW, that we couldn't get into the rooms earlier isn't within the FOSDEM organizers responsibility, but the universities. And, one has to say, the university is also pretty nice providing the venue free of charge.

More later.

I has arrived in Brusselz and had pizza and beer already :-)

In other news, we have a test stream up and the rest of the preparations look good, so I'm confident you can haz streemz from the Debian dev room at FOSDEM! (Times are UTC+1)

Just follow the instructions from Erics mail the debconf-video list.

It's a totally unclear when we will be able to enter the room on Saturday, and it might only possible at 13oo, right when Bens and my talk about our video work is scheduled. That has been done on purpose, so in that case we can use our talk slot for setting things up. I don't hope this will happen, but it's the worst case...

Oh, and if you're at FOSDEM, please help us out, we still have some volunteer slots to fill. And more importantly, have a whole lot of fun!

So I know, I know. There are a lot of annoying memes circulating on the net/facebook/[pick your spot] and well, sometimes the best thing to do is stop the damn thing by ignoring its existence. But I have to say, I have completely, totally and absolutely have loved reading the 25 things notes on facebook. It just provides a window into the extraordinary character that emerges from the collection of mundane events/likes/pleasures that make up people s lives. Reading them took me back to elementary school when and where I was an avid slam-booker. I have very fond of collecting and reading the tidbits of thoughts and information people left behind in my notebook. What also struck me about these recent 25 thingie notes is how odd or not as interesting, I think, it would be to have them recited to you over coffee or at dinner. Now I could be wrong here but I think the list-like quality would just not fly in a conversational context. A few facts with more embellishment would work but a whole string of thoughts would just sound flat and out of place. A reminder that format does matter for engendering certain types of knowledge. So here is my list.. 1. I looked like a boy for the first three years of my life (but a cute one, I think).
2. I love dogs so much that I often think that if I had a criminal streak, I would be a dog nabber.
3. I would routinely bring home dogs from the street when I was a kid. Many of them ended up dead after being hit by cars (they liked to return to the street and this only happened to 2 of them).
4. My favorite concert was Jimmy Cliff in a parking lot. There was lots of rain and lots of weed.
5. I like have a penchant for tall men. My mom claims it was because I lacked a strong father figure in my early childhood years. Who knows if that is the case.
6. I knew the instant that I took an anthropology class I wanted to be an anthropologist. I guess I made it happen (and it was one of the few moments of clarity in life).
7. I started the first environmental club in my high school and my car was called the recycle-mobile because there were always cans in the back seat.
8. I love the ocean; swimming, snorkeling, diving, sailing, and just watching it, though the cold ocean is not always by cup of tea.
9. I had terrible insomnia for a year and slept for a good chunk of it on a couch. I like the snuggle feeling I got from sleeping against a back.
10. I am very indecisive person. It is annoying as i tend to worry a lot about whether I made the right decision.
11. I was a shy kid and barely talked until meeting my best friend in kindergarten, Yael
12. I also failed the psychological test to get into school but my mom managed to get me in anyway.
13. I often wonder if I would have been a nun if I had lived prior to 1900s to escape various domestic obligations. I think it might have been fun to be a nun.. Fun to be a nun also has a nice ring to it.

14. I am currently struggling with an Etsy addiction and the UPS delivery guy asked if delivering packages would be a daily occurrence.. I just find all the stuff amazing and it brings me back to my artist days when I used to paint and spend a heck of a lot of time in the darkroom.
15. I have recurrent issues with nausea and have been hospitalized for it a few times. It is gut wrenching and really uncomfortable when it happens.
16. When I left NYC in 1997 I thought i would never come back. I am here now and quite happy.
17. I was obsessed with Ultimate Frisbee for many man years. I played more than I studied and finally gave up as it was ruining (or perhaps ruined?) my neck. I still miss it.
18. I LOVE tostones and would eat them everyday if they were not, you know, so bad for you.
19. I have been using IRC for 7 years and consider some of my best friends to come from there.
20. Some folks have asked how I became interested in politics and I am pretty sure it was Doonesbury.
21. When I was like 4 we went to some fair and I swore that I almost got flung off some rickety ride but this could be totally wrong. It was really frightening.
22. The coldest night of my life was spent in Los Nevados, Venezuela and the scariest car ride I ever took was leaving Los Nevados in a jeep and something that resembled a road.
23. A few sucker fish once tried to stick on me while I was doing a decompression stop after a dive. My dive buddy smacked the fish, which had devil faces, with the regulator, saving me from what would have been a really sort of sucky situation.
24. I am trying to learn how to surf and am really sorry that I did not do so when a teenager since I don t exactly have the time to really learn.
25. Since I am not sure how to end, I will do so with a

So I know, I know. There are a lot of annoying memes circulating on the net/facebook/[pick your spot] and well, sometimes the best thing to do is stop the damn thing by ignoring its existence. But I have to say, I have completely, totally and absolutely have loved reading the 25 things notes on facebook. It just provides a window into the extraordinary character that emerges from the collection of mundane events/likes/pleasures that make up people s lives. Reading them took me back to elementary school when and where I was an avid slam-booker. I have very fond of collecting and reading the tidbits of thoughts and information people left behind in my notebook. What also struck me about these recent 25 thingie notes is how odd or not as interesting, I think, it would be to have them recited to you over coffee or at dinner. Now I could be wrong here but I think the list-like quality would just not fly in a conversational context. A few facts with more embellishment would work but a whole string of thoughts would just sound flat and out of place. A reminder that format does matter for engendering certain types of knowledge. So here is my list.. 1. I looked like a boy for the first three years of my life (but a cute one, I think).
2. I love dogs so much that I often think that if I had a criminal streak, I would be a dog nabber.
3. I would routinely bring home dogs from the street when I was a kid. Many of them ended up dead after being hit by cars (they liked to return to the street and this only happened to 2 of them).
4. My favorite concert was Jimmy Cliff in a parking lot. There was lots of rain and lots of weed.
5. I like have a penchant for tall men. My mom claims it was because I lacked a strong father figure in my early childhood years. Who knows if that is the case.
6. I knew the instant that I took an anthropology class I wanted to be an anthropologist. I guess I made it happen (and it was one of the few moments of clarity in life).
7. I started the first environmental club in my high school and my car was called the recycle-mobile because there were always cans in the back seat.
8. I love the ocean; swimming, snorkeling, diving, sailing, and just watching it, though the cold ocean is not always by cup of tea.
9. I had terrible insomnia for a year and slept for a good chunk of it on a couch. I like the snuggle feeling I got from sleeping against a back.
10. I am very indecisive person. It is annoying as i tend to worry a lot about whether I made the right decision.
11. I was a shy kid and barely talked until meeting my best friend in kindergarten, Yael
12. I also failed the psychological test to get into school but my mom managed to get me in anyway.
13. I often wonder if I would have been a nun if I had lived prior to 1900s to escape various domestic obligations. I think it might have been fun to be a nun.. Fun to be a nun also has a nice ring to it.

14. I am currently struggling with an Etsy addiction and the UPS delivery guy asked if delivering packages would be a daily occurrence.. I just find all the stuff amazing and it brings me back to my artist days when I used to paint and spend a heck of a lot of time in the darkroom.
15. I have recurrent issues with nausea and have been hospitalized for it a few times. It is gut wrenching and really uncomfortable when it happens.
16. When I left NYC in 1997 I thought i would never come back. I am here now and quite happy.
17. I was obsessed with Ultimate Frisbee for many man years. I played more than I studied and finally gave up as it was ruining (or perhaps ruined?) my neck. I still miss it.
18. I LOVE tostones and would eat them everyday if they were not, you know, so bad for you.
19. I have been using IRC for 7 years and consider some of my best friends to come from there.
20. Some folks have asked how I became interested in politics and I am pretty sure it was Doonesbury.
21. When I was like 4 we went to some fair and I swore that I almost got flung off some rickety ride but this could be totally wrong. It was really frightening.
22. The coldest night of my life was spent in Los Nevados, Venezuela and the scariest car ride I ever took was leaving Los Nevados in a jeep and something that resembled a road.
23. A few sucker fish once tried to stick on me while I was doing a decompression stop after a dive. My dive buddy smacked the fish, which had devil faces, with the regulator, saving me from what would have been a really sort of sucky situation.
24. I am trying to learn how to surf and am really sorry that I did not do so when a teenager since I don t exactly have the time to really learn.
25. Since I am not sure how to end, I will do so with a

So I know, I know. There are a lot of annoying memes circulating on the net/facebook/[pick your spot] and well, sometimes the best thing to do is stop the damn thing by ignoring its existence. But I have to say, I have completely, totally and absolutely have loved reading the 25 things notes on facebook. It just provides a window into the extraordinary character that emerges from the collection of mundane events/likes/pleasures that make up people s lives. Reading them took me back to elementary school when and where I was an avid slam-booker. I have very fond of collecting and reading the tidbits of thoughts and information people left behind in my notebook. What also struck me about these recent 25 thingie notes is how odd or not as interesting, I think, it would be to have them recited to you over coffee or at dinner. Now I could be wrong here but I think the list-like quality would just not fly in a conversational context. A few facts with more embellishment would work but a whole string of thoughts would just sound flat and out of place. A reminder that format does matter for engendering certain types of knowledge. So here is my list.. 1. I looked like a boy for the first three years of my life (but a cute one, I think).
2. I love dogs so much that I often think that if I had a criminal streak, I would be a dog nabber.
3. I would routinely bring home dogs from the street when I was a kid. Many of them ended up dead after being hit by cars (they liked to return to the street and this only happened to 2 of them).
4. My favorite concert was Jimmy Cliff in a parking lot. There was lots of rain and lots of weed.
5. I like have a penchant for tall men. My mom claims it was because I lacked a strong father figure in my early childhood years. Who knows if that is the case.
6. I knew the instant that I took an anthropology class I wanted to be an anthropologist. I guess I made it happen (and it was one of the few moments of clarity in life).
7. I started the first environmental club in my high school and my car was called the recycle-mobile because there were always cans in the back seat.
8. I love the ocean; swimming, snorkeling, diving, sailing, and just watching it, though the cold ocean is not always by cup of tea.
9. I had terrible insomnia for a year and slept for a good chunk of it on a couch. I like the snuggle feeling I got from sleeping against a back.
10. I am very indecisive person. It is annoying as i tend to worry a lot about whether I made the right decision.
11. I was a shy kid and barely talked until meeting my best friend in kindergarten, Yael
12. I also failed the psychological test to get into school but my mom managed to get me in anyway.
13. I often wonder if I would have been a nun if I had lived prior to 1900s to escape various domestic obligations. I think it might have been fun to be a nun.. Fun to be a nun also has a nice ring to it.

14. I am currently struggling with an Etsy addiction and the UPS delivery guy asked if delivering packages would be a daily occurrence.. I just find all the stuff amazing and it brings me back to my artist days when I used to paint and spend a heck of a lot of time in the darkroom.
15. I have recurrent issues with nausea and have been hospitalized for it a few times. It is gut wrenching and really uncomfortable when it happens.
16. When I left NYC in 1997 I thought i would never come back. I am here now and quite happy.
17. I was obsessed with Ultimate Frisbee for many man years. I played more than I studied and finally gave up as it was ruining (or perhaps ruined?) my neck. I still miss it.
18. I LOVE tostones and would eat them everyday if they were not, you know, so bad for you.
19. I have been using IRC for 7 years and consider some of my best friends to come from there.
20. Some folks have asked how I became interested in politics and I am pretty sure it was Doonesbury.
21. When I was like 4 we went to some fair and I swore that I almost got flung off some rickety ride but this could be totally wrong. It was really frightening.
22. The coldest night of my life was spent in Los Nevados, Venezuela and the scariest car ride I ever took was leaving Los Nevados in a jeep and something that resembled a road.
23. A few sucker fish once tried to stick on me while I was doing a decompression stop after a dive. My dive buddy smacked the fish, which had devil faces, with the regulator, saving me from what would have been a really sort of sucky situation.
24. I am trying to learn how to surf and am really sorry that I did not do so when a teenager since I don t exactly have the time to really learn.
25. Since I am not sure how to end, I will do so with a

Since late 2008 WebKit/GTK+ has been advancing in a better pace than earlier that year. Patches are being reviewed and committed actively, mostly by Holger Freyther (zecke). This last month, among other goodies such as better keyword searching for the WooHoo bar in Epiphany and enabling WebKit s Soup backend to upload files, I have been working on getting download support into WebKit/GTK+ so that we can use that API in Epiphany. Most of the heavy work was done by Marco Barisione and Pierre-Luc Beaudoin early last year. I brought the patch up-to-date and modified it with input from various people into something simpler and handling some more use cases. Tonight I finally reached a milestone, being able to download a Debian ISO with Epiphany/WebKit:

This is work in progress. There are many rough edges to sharpen, still, but this work should be ready for merging very soon. If you want to help take a look at the WebKit bug report we are using to track this work, and the corresponding Epiphany bug report. Anyway, I ve been using both Epiphany and WebKit/GTK+ from trunk for about a month now, and the number of things I am missing is going down quickly. Come help us test and get a regressionless Epiphany with WebKit/GTK+ for GNOME 2.28!

initramfs-tools design principle is to ship a generic initramfs. The design explicitly allows lots of customization through hook and boot scripts. A previous post focused on the history of initramfs-tools. Several contributors enhanced initramfs-tools since the Debian Etch release so the non exclusive new feature list:

• The initramfs contains all drivers/ ata,block,ide,mmc,scsi modules instead of a stupid hard coded list. This gives bonus points for getting more future proof.
• Configurable small initramfs: The MODULES=dep mode walks /sys/ for the needed drivers of the specific box. This was the most wanted feature and is the new default for some Debian-Installer embedded architectures. The code seems in between well tested even if some corner cases might still emerge. The smaller initramfs is needed for specific bootloaders and helps on slow target boxes.
  For a even smaller initramfs you can kick busybox if you don't have an lvm2 root or don't need it's debugging tools.
• Quicker initramfs build: The update-initramfs command uses dpkg trigger and thus not every postinst update-initramfs(8) call leads to a new initramfs build. Also the build time got improved.
• Improved panic message (yes users need to be handhold at this point :).
• Potential debug log is visible after call to init(8) inside /dev/.initramfs/.
• update-initramfs got hardened against failure on update or ro partitons.
• The klibc utilities got worked on: chroot, fstype, ipconfig, mount, nfsmount sync.
• Fixed various bugs in NFS and networking setup due to incorrect option parsing.
• Allow to blacklist modules on boot by cmdline bootarg blacklist=modulename.
• Allow non root usage of mkinitramfs.

As bonus to some cleanup and docs update we have also seen a Ubuntu sync and are not too diverged.

Bruce Schneier is very sceptical about the new hard drive encryption standards released by a group composed of virtually all major storage vendors. He points out that the established software solutions have worked just fine, while this new standards adds complexity (and probably flaws, too) at the hardware level. I'm not so sure myself in which direction the balance goes:

• Encryption (without the key management, which I do not suppose the standard covers) is not that complex to get right and it can easily take advantage of hardware acceleration. (Yes, I don't quote numbers here. Schneier claims he hasn't had problems with encryption speed, but doesn't have numbers either ...)
• It should be a lot easier to subvert a software component than it is to subvert a hardware component.
• It is a lot harder to correct errors in hardware / firmware than in software and get users to apply the updates.
• In many cases the key management is the weak point, not the encryption itself. And key management is hard to get right regardless of where the encryption sits.
• I'm sure the abysmal track record of encrypted drives affects only the cheap USB drives and not the type of hardware we're talking about here. But, can I really be sure? (Serious) software solutions come from companies where security is the main business, whereas the hardware encryption will be implemented by storage companies which so far haven't had to care much about these issues.
• Finally: This standard should replace a number of proprietary solutions since some vendors already do offer encrypted drives anyway. Assuming the standard is sane, this should certainly be a Good Thing in any case.

My home file server, Asterisk PBX, firewall and general router is apparently dying. I am looking forward to replacing it, because it s old and eats too much power anyway. Now I just need to figure out what to put in its place. Basically I need a low-power machine that ll be always on, with at least two LAN ports (three would be better, but I can also connect the cable modem with USB), and a means to connect at least two harddrives with at least 1Tb capacity. I d rather use SATA for the drives than USB, but I would be willing to investigate eSATA and external drives too. However, I want to have direct access to the drives and not be forced to use some sort of proprietary RAID. At the moment, I am investigating the Thecus N3200PRO, which has quite a reasonable hardware selection. The device has a low-power AMD Geode processor, but for some reason I have it stuck in my head that the ARM would be a better choice. Does anyone have experience with this device? Or maybe someone would like to make a different suggestion? Mail me! I d prefer a device that I can get working without too much learning or frickling. The less I have to learn/know about and touch hardware, the better. It would help if the machine booted off the harddisk, for then I could install Linux elsewhere and move the disks. Alternatively, network booting and a serial console would work, although I hear that USB makes that unnecessarily painful. I d like to avoid flashing ROMs or other black magic just to get it working. NP: AC/DC: Powerage Update: The folks at EXSYS kindly replied and filled me in with some information regarding the N3200PRO. Thanks! First of all, Thecus officially claims that it is not possible to install Linux on the device (although the device is running Linux, according to the hardware list). Second, the machine boots off a Flash-ROM, which makes the installation more difficult than I d like it, and apparently also one-way: once the Thecus firmware has been overwritten, there seems to be no way to get it back. I am looking elsewhere now, because even though the hardware is exactly what I want, I won t give money to a company who impose shackles on their customers and force them to use software that may not be up-to-date, and which is probably castrated I d be surprised if the N3200PRO spoke IPv6, for instance. Nevertheless, I ve asked about installing Debian in the Thecus User Group forum and I also dropped a message to Thecus itself. I ll keep this post up-to-date, so come back for more.

Theodore wonders about LUG activity - well, I have been very active over the years in the Devon and Cornwall GNU/Linux User Group but the problem is that Debian (and more specifically Emdebian) is taking up the time that I used to put into the LUG. The LUG itself has remained very active, although geography means that meetings are actually difficult. The LUG continues to attract new members, existing members continue to contribute and learn new stuff themselves and a number of the long-standing members have joined free software organisations in their own right - including Debian. If there is going to be another DD in Devon or Cornwall besides myself, I'm pretty sure that the person will have been part of the DCGLUG before considering joining Debian.

I'm still webmaster for my local LUG, I get to some meetings although some do conflict with existing Emdebian meetings.

What do I get out of it? Local friendships and exposure to GNU/Linux issues outside Debian.

Debian can be a very insular world - we care about Debian, we talk about Debian, we get together as Debian but sometimes we lack comparative input. We don't really know how we compare with other operating systems and other distributions at a user level. Debian Developers, in particular, can easily lose touch with ordinary users of other systems. Debian, for me, is also a distant world geographically. I live a long way from other DD's in the UK who gravitate towards Cambridge, 300 miles away. It's just nice to have people within 10-50 miles, people I can contact about hardware issues and who have just the part I need because they kept it "just in case".

I still contribute on the LUG mailing list, although my contributions are generally related to licences, avoiding non-free rubbish and issues around embedded devices. I'm not as active as I'd like to be or as I have been in the past but I still want to be part of the LUG.

At the Linux Foundation, I recently had been brainstorming with some my colleagues about ways in which we might be able to reach out to the various local Linux User s Group (LUGS). So I was quite surprised when I saw a blog posting from Lenovo s Connections blog asking the question: Local User Groups - gone the way of the dinosaur? and even more provocatively, Has the web now relegated the user group to history, along with dot matrix printers, cassette tapes for mass storage, and dial up modems with acoustic couplers? I checked on the web for a number of LUG s, such as the Boston Linux and Unix User Group (BLU) and the Silicon Valley LUG (SVLUG), and they appeared to be active, at least in terms of mailing list activity and event calanedars. But of course that doesn t indicate how many people are actually attending the face-to-face meetings, and how strong the LUG s are in general. So let me ask here do you attend or participate in a LUG? How active is it? What do you get out of participating in a LUG?

In order to have pretty highlighted oz code in HTML and TeX, I defined a simple language definition "oz.lang"

keyword = "andthen at attr case catch choice class cond",
          "declare define dis div do else elsecase ",
          "elseif elseof end fail false feat finally for",
          "from fun functor if import in local lock meth",
          "mod not of or orelse prepare proc prop raise",
          "require self skip then thread true try unit"
meta delim "<" ">"
cbracket = " "
comment start "%"
symbol = "~","*","(",")","-","+","=","[","]","#",":",
       ",",".","/","?","&","<",">","\ "
atom delim "'" "'"  escape "\\"
atom = '[a-z][[:alpha:][:digit:]]*'
variable delim " " " "  escape "\\"
variable = '[A-Z][[:alpha:][:digit:]]*'
string delim "\"" "\"" escape "\\"

The meta tags are so I can intersperse EBNF notation in with oz code. Unfortunately source-highlight seems a little braindead about e.g. environment variables, so I had to wrap the invocation in a script

#!/bin/sh
HLDIR=$HOME/config/source-highlight
source-highlight --style-file=$HLDIR/default.style --lang-map=$HLDIR/lang.map $*

The final pieces of the puzzle is a customized lang.map file that tells source-highlight to use "oz.lang" for "foo.oz" and a default.style file that defines highlighting for "meta" text.

Emacs 23.0.90 was released yesterday, it's the first pretest for the upcoming 23.1 version. Debian packages for etch and lenny/sid are here; Ubuntu packages for hardy, intrepid and jaunty are here. If you find any bugs please use M-x report-emacs-bug (unless it's a packaging issue, in which case feel free to email me directly).

Here I ll try to present you some tips on how one could easily make a playground become a paid fun. And no, I won t be teaching you how to become rich, although I would like if you would teach me how that could be accomplished as I m trying to come up with a way to do just that for a couple of years now and failed miserably. Recently, I ve been setting up KVM virtual machines in order to do a lot of testing for a project I m involved with. Letting boring details aside, one could say that a very long, boring and error prone setup was finished after a lot of work and it worked like a charm in the end, as a KVM machine. As always, laziness is a given and when you are into it you empower yourself to come up with some nice hacks and goes that extra mile to find out how one could not to have to do boring and repetitive things again and again, in the best spirit of let s have some work now and save me ten times more work later . As I m becoming more and more into that spirit of laziness, there I went looking for a way which would let me transform my beloved and nice working KVM machine into a fully featured real physical server. After some tips from microblogosphere friends (thanks fike), I had some ideas on how that could be accomplished. Turned out my ideas weren t really all that right so there I went again looking for a way to do what I wanted. After some research I found out that the KVM guys already gave some thought about it and even had a ready solution to my problem : it s called qemu-nbd. Yes, by now everyone should know that KVM builds on top of the excelent (just not so snappy) QEMU. However, as I m a Debian user, here I should say that in Debian, most notably Debian sid/unstable, the qemu-nbd binary was renamed to kvm-nbd, just as the KVM binary is called only kvm and not qemu-system-x86_64 or whatever else is called these days upstream. NBD (short for Network Block Device) is a nice thing. I hadn t tried it before (I certainly used and am still using in some projects of mine the not-upstreamed-yet-but-so-nice-that-I-couldnt-resist DRBD, which seems to share some ideas which NBD). In short (read NBD link for more info on that), NBD allows the Linux kernel to use a remote server as a block device. Also, its upstream is a fellow Debian developer (hello Wouter). How nice s it ? As NBD is an upstreamed kernel feature, you don t need to go to the external-module-route-hell. You only need the userland tools, which are nicely packaged and integrated into Debian as well. They re only one aptitude away, so you could use this command to bring it to your KVM host :

aptitude install nbd-client

After that, you will want to export your image file (the file which represents the disk of you virtual machine) as a NBD block device, so you will be able to mount it under your KVM host and do whatever you want to do with it. Here s how one would do it :

kmv-nbd conect=/dev/nbd0 myimagefile.img

I tested it using both qcow2 and raw disk images and both worked like a charm so I don t think you will have any problems here. Next, you need to create a directory structure under your KVM host which temporarily will be used to mount the partitions inside the virtual block device of your KVM machine. You could do this like this :

mkdir /newserver mkdir /newserver/usr mkdir /newserver/var mkdir /newserver/home

In the example above, I ve created these directories because I want my new server to have separated root, /usr, /var and /home partitions and mount points. Feel free to adapt to any kind of partitioning layout you please. Next, you will mount yout virtual machine filesystem under a temporary location, so you will be able to copy all of its content later to your final desired destination, i.e. the real partitions inside the real disk you are going to use in your future real server (not a virtual machine anymore). I did it using :

mkdir -p /mnt/temp mount /dev/nbd0p1 /mnt/temp

Notice that the /dev/nb0p1 above is my root partition inside my KVM machine, only that it s represented now in my KVM host in NBD s device node notation here. I ve only one partition inside this particular virtual machine (aside from the swap partition). Next, you want to mount the partitions on the real disk you want to be used in your new real server under the directories created earlier so you will be able to chroot to then later and do any tweaks you may want to, like fixing /etc/fstab, /boot/grub/device.map, /boot/grub/menu.lst and all these places we know makes references to block devices which may differ from the situation you had in your virtual machine running under the KVM. Here s what I used :

mount /dev/sdb1 /newserver mount /dev/sdb3 /newserver/usr mount /dev/sdb5 /newserver/var mount /dev/sdb6 /newserver/home

The device nodes above are from your real disk s partitions, not from any virtualized device block access method like NBD. Also, take care not to mount your primary disk s partitions (the ones you are using under in your KVM host) as you could destroy them easily. As you can see above, I m using /dev/sdbX as /dev/sda is my primary disk, the one under which my KVM host is running. Again, adapt to your scenario. Next, you just copy everything from your virtual machine filesystem (which is now accessible from within your NBD block device) to your real disk. I did it using :

cp -a /mnt/temp/* /newserver/

After that, you can disconnect your KVM virtual machine image file from the exported NDB device block using :

kvm-nbd -d /dev/ndb0

And then chroot to your real disk layout yout just copied to /newserver in order to fix anything which would make reference to block devices while running as a virtual machine under KVM but which now will be a completely different thing as a real server, like your /etc/fstab, /boot/grub/device.map, /boot/grub/menu.lst and so on. In order to chroot to your new soon-to-be-real filesystem you could use :

chroot /newserver

Then go nuts and start fixing everything you may think needs to be fixed so this filesystem could be used in a real server to boot it up. Im my case, I needed to fix /etc/fstab in order to mount my additional partitions (as under KVM I was using only a root and a swap partition and now, under the real server, I ll be using separated root, swap, /usr, /var and /home). Before I went changing more things, I fixed my /boot/grub/device.map and my /boot/grub/menu.lst files to point to /dev/sdb and /dev/sdb[1], respectively, so I could run grub-install from inside the chroot in order to install GRUB into the real new disk s MBR (master boot record), using :

grub-install /dev/sdb

Then, finally, I fixed /boot/grub/device.map and /boot/grub/menu.lst again so they would point to /dev/sda and /dev/sda[1], as /dev/sda will be the device node for this new disk when it wil be running under the new real server and not as a disk inside the KVM host machine. Next, I exited the chroot using :

exit

And umounted the new real disk s partitions, using (now already out of the chroot) :

umount /newserver/home umount /newserver/var umount /newserver/usr umount /newserver

Now you can take this new disk out of your KVM host machine, put it inside your new real server, physically install it there, turn on your new real server and everything installed while the filesystem in it was being used under the KVM virtual machine will be there, running nicely. And you re done. That s it. Also, it s important to point out that it s much easier being done than being said (or written, in this case) so, if it looks scary because of the size of this post, don t let it disincourage you as this whole thing is a pretty straightforward procedure, much easier than it seems. And as I know that I will receive lost of complaints from people which will tell me how inefficient this whole thing is and how I could have accomplished the exact same thing in a much easier and faster way (perhaps even with a already existing tool which would automate almost entirely the whole proccess), I would say to these people to please exercise their right to share ideas using the comments. Just be nice on me, please. After all, it was fun and I learned new things while doing it all, as well as I tried to share what I learned from this experience with my peers. That s what matters. Peace, love and geekness to all of you

I ve so far been going through the list of projects that were done last year (part 1, part 2) in a somewhat dry fashion so I m going to make a little pause here and tell where I m going from with these posts. As I went through the 2008 Summer of Code at Debian, I moved from being a nearly total outsider student to something more of a developer. I ve been contributing to Aptitude since the end of the Summer of Code (well, trying to find time to contribute more, as with many people..) and will be going to FOSDEM. I can t say I m an insider yet: I haven t met a lot of people, most people have no idea who I am, I ve been active here for, like 9 months and I m not even in new-maintainer yet (though I plan to apply when I feel I ll have contributed significantly to Debian). The Student point of view See, I m a student in Computer Science. I use free software, I d like to participate but it s intimidating and you never know where to start. You know the drill. Then comes the Google Summer of Code. Let s review its stated goals, as per its FAQ:

Google Summer of Code has several goals:

• Get more open source code created and released for the benefit of all;
• Inspire young developers to begin participating in open source development;
• Help open source projects identify and bring in new developers and committers;
• Provide students in Computer Science and related fields the opportunity to do work related to their academic pursuits (think flip bits, not burgers );
• Give students more exposure to real-world software development scenarios (e.g., distributed development, software licensing questions, mailing-list etiquette).

I m going to start with these goals and provide some of my opinions in something of a candid way. Inspire young developers to begin participating in open source development I have been playing with the idea of making a GUI for Aptitude ever since I dropped Synaptic, about 2 months into its use. It felt like when I bought a high-school required Texas Instruments TI-83+, that I dropped for a TI-89 within a month. Since back in 2005, every time I would see someone using Synaptic, I would pitch Aptitude as a better tool. The main reason for not doing so was that Aptitude was scary-looking. See, it s a lot of blocky text and wacky colors. With life and cool stuff like CPGE, I never had time to really code so I left it at that. In 2008, for the first time I was free the whole summer and so, I tried to get into the Summer of Code program and into Debian. Actually, it wasn t the first try. One popular way to get acquainted with Debian is to go to wnpp, adopt a package (new or orphaned) and find a mentor to upload it. In January 2008, I did try to package a set of geocaching tools I used at that time. But I didn t find a mentor to upload it. I didn t try very hard though and the package had some minor issues anyway. I reckon that Debian-mentor is a good idea to bring in new Debian Maintainers but the whole process is still quite technical. It is true that the minimal technical level for good packaging is not trivial in itself and the process should filter out unserious people, but the technicality curve could be adjusted to be more welcoming. I think the Debian website could be improved in this area (ok, it s a quite long-standing bug). Holger Levsen mentioned the way Fedora and Sugar presented avenues of collaboration to prospective developers. The crux here is that it should feel much easier to identify areas to get involved into and who to contact if needed. Help open source projects identify and bring in new developers and committers Actually, it would rather be the other way around: help students identify and integrate into open source projects. For the Summer of Code, I only postulated at two organizations, Debian and Freenet (the ones working on an anonymous darknet, remember ?). I got accepted at both and ultimately chose Debian (was my first choice from the beginning). The Debian developers community is quite unique in the way it is very decentralized, independent and fluid. There are teams in some areas (Kernel, KDE, Translation, Edu, Publicity, whatever) but much of what makes up Debian is done by individual developers working on their own. The downside of this is that for a newcomer, it s a little off-putting. Organized teams are not the way all things are done within Debian so there are often no smaller circle of people one gets to know. Going to Debian meetings and not knowing most of the people is a little intimidating. Keeping up with all the faces is a little hard too :). Many other organizations participated into the Summer of Code and many would feel arguably different. Many may be more corporate-like, more hierarchical, more centralized. I preferred Debian because it was less formal in its structure. I felt that I didn t want to get into something that looked too much like work with supervisors and the like. It is indeed how it felt, there were no one up there to decide what we had to do. We were quite independent. I can say that the Summer of Code is quite a good way to get a feeling of how a particular organization works in the inside. Give students more exposure to real-world software development scenarios As said earlier, many parts of Debian are independent, which is a result of the work separation through packages. In my work on Aptitude, it is a pity that I didn t have to interact a lot with other members of the Debian community. Aptitude talks with the rest of the Debian packaging ecosystem through mature library interfaces so there s not much need to ask questions beyond them, and even more so because my Daniel Burrows, my mentor and developer of Aptitude participated in their development. Also, I was working on bringing a graphical interface to it, so I didn t have to modify a lot of core code that interacted with the outside world. Despite this, I still met a few people interested with future developments in the area of package managers. One example is Enrico Zini who pushed his work with Xapian APT Index. Over the summer, my mentor integrated packages search through Xapian which was interesting with the expanded possibilities of a graphical interface such as search as you type, drop down suggestions and so on. Because of the short duration of the Summer of Code, most projects can t complete a full development cycle. The proposed work in my proposal was quite imposing. In the end, I managed to produce an (probably not even) alpha quality version of a graphical interface. My branch (if I remember correctly) was merged into the main trunk at the end of the summer and a version landed in Experimental at the end of the year. One aspect that I missed was beta-testing feedback. During summer, only a handful people popped up on the mailing-list giving feedback on the GUI I was writing, although I knew through stats on my mercurial repository that dozens of people cloned it and followed it. Debian has no testing team , or any kind of semi-organized group of people who try stuff, which would be very useful to have an idea of how well I was doing. So, did the Summer of Code at Debian give me real-world software development scenarios ? Not really in my case but by staying longer into Debian, I think caught up a little with that. Here is some advice for the future Summer of Code student at Debian:

• the work of a Linux distribution might look a little nebulous and mysterious but the reality is that Debian does a very large range of development work: web development (debexpo), user application development (aptitude-gtk), hardware interaction (Debian NAS), developer infrastructure (lintian) or even quite theoretical stuff (debgraph) there is really a lot to choose from.
• Debian is not a nanny-project: you will not be managed, you re free, but you re on your own, be prepared
• don t hesitate to contact anybody working in areas you re interested in: look for packages maintainers, search mailing lists and wiki, look for debconf/fosdem/wherever talks by Debian developers. Developers will be happy to redirect you to the right people.
• choose something that can be reasonably finished by summer s end. Also take into account release freezes.
• be sure to contact anyone involved into the area you re working on: they will try to make it easier to merge your work in
• be sure to contact anyone involved into the area you re working on: it s ok to ask for help
• publicize your work: the Debian Project News will be happy to take your press releases , write a blog and get included on the planet, go on #debian-devel and #debian-soc, go to conferences and meetings
• you re not alone, interact with the other Summer of Code students, try out their code, give them feedback
• Communicate, nobody will kill you if you say something stupid
• Communicate, don t be afraid if you run into problems
• Communicate, clear enough ?

To conclude, despite all the difficulties, I would say that the Summer of Code at Debian was awesome. Although Debian is quite different from many other organizations, it was a very fruitful experience. And that s why I m still here. Coming next is the rest of the projects reviews and a more concise and substantive list of recommendations for the handling of the next Summer of Code at Debian. And of course, see you at FOSDEM.

Another Saturday, another Lintian release. As has frequently been the case lately, much of the work was done by Raphael Geissert, who provided several more patch sets fixing new problems and old ones. I also finally got a chance to dig into the code that generates the long tag descriptions and ended up rewriting it entirely, which will remove some minor annoyances in the setup of Lintian on lintian.debian.org. I was expecting to have a chance to write a pile of pedantic checks, since several of the old bug reports are easy checks to write and were just waiting for the new tag status. I ended up working on other things and merging patches instead, though. Maybe the next release. One amusing note: the compressed Lintian changelog is 112KB (365KB uncompressed). The tar.gz file for the entire Lintian release is 589KB. So the changelog for Lintian is nearly 20% of the entire distribution. Admittedly, we have a fairly verbose changelog style, but most Lintian work involves large numbers of small tweaks and small patches. I think most of the changelog size is unavoidable. I don't think this is a problem Lintian is not the sort of thing that one runs in an embedded environment and within reason it doesn't matter how large the installed size is but it is rather funny. I stopped the last archive-wide run because gluck was being rebooted with a new kernel that didn't cause Perl to close huge numbers of file descriptors on popen, and then due to other things going on my life, didn't get a chance to restart the archive run until yesterday. It's on binary packages starting with "p" now, so hopefully sometime tomorrow there will be fresh Lintian results with 2.2.0 and I can post a bits from the Lintian maintainers message.

Paul Wayper has said that he only wants to work for companies that will send him too LCA [1]. While that criteria is quite reasonable it seems overly specific. Among other things the varying location of LCA will result in the expense for the employer varying slightly year by year - which employers generally don t like. I believe that a better option is to have an employment package that specifies a certain amount of money (related to the gross income of the employee) should be set aside for training, hardware, or other expenses that help the employee (or their colleagues) do their job. Such an option would probably only be available to senior employees who are most able to determine the most effective way of spending the money. For example an employee who earns $100,000 per annum might be permitted to assign 10% of their income ($10,000) to training or hardware that assists their job. Modern PCs are so cheap that any reasonable hardware requirements could fit within that budget with ease. There are several benefits to such a scheme. On many occasions I have had colleagues who had inadequate hardware to do their work, slow PCs with small screens really impacted their productivity, in such situations buying a $400 PC and a $400 monitor for each person in the team could make a significant direct improvement to productivity before the impact on moralle kicked in! Some years ago Lenovo ran some adverts for Thinkpads which said demand one at the interview . That made sense when a Thinkpad was an expensive piece of hardware. While there are still some expensive Thinkpads, there is a good range of cheap models, two which cost less than $1200AU and another eight which cost between $1200 and $1800. Now it makes more sense to allow each employee to choose their own hardware (both desktop and portable) and not even bother about issues such as whether the IT department blesses them. As Tom Limoncelli suggested in his LCA keynote, users are going to take more control over their environment whether the IT department like it or not, so it s best to work with them rather than fighting them. For training a common problem is that management can t correctly determine which conferences are worthy of the expense of sending their technical staff. Then when a conference is selected they send everyone. It seems to me that when there are a number of conferences in a region (EG AUUG, LCA, OSDC, and SAGE-AU in Australia) there is a benefit in having someone from your team attend each one. Planning at the start of the year which conferences will be attended by each team member is something that appears to be beyond the ability of most managers as it requires knowing the technical interests and skill areas of most staff. If each employee was granted one week of paid time per year to attend conferences and they could determine their own budget allocation then they would be able to work it out themselves in a more effective manner.

• [1] http://www.mabula.net/tbfw/blosxom.cgi/2009/01/23

Stewart has made some predictions for the future of computing [1]. He predicts that within 2 years the majority of consumer machines will be laptops and have SSD (not rotational media). I predict that by the end of next year more than half of all new consumer machines that are being sold will be laptops (defined as being portable machines with the display and keyboard forming part of a single unit), and that more than half of such machines will have SSD as the primary storage (IE used for booting and for most common file access). I predict that by the end of 2010 the majority of all computers shipped (in all form factors including games consoles and servers) will have SSD as their primary storage. I predict that in late 2010 rotational media will start to go away for most tasks, but for at least the next year the model will be SSD for small/light/fast operations and rotational media for large capacity. I m not disagreeing with Stewart, just being more precise. Also while Val made some good points about the reliability of SSD [2] I don t think that this will be an obstacle in the low-end of the market. There is no little evidence of computers failing in the consumer market due to being unreliable - it seems that Microsoft has conditioned people to expect unreliability. I predict that Sun will not release ZFS under the GPL in time for anyone to care. The release of OpenSolaris was way behind schedule and I don t expect anything different this time around. Stewart predicts that in five years Linux will have significantly more desktop market share than Apple. I agree and also predict that Apple will convert to the Linux kernel. I predict that Apple will become the first Linux distributor to make any significant hardware sales for the mainstream computer market (Linux bundled with hardware has already done well for mobile phones, routers, Tivo, and similar devices where the user doesn t know what OS is running). I predict the death of Windows mobile. I predict that in five years the mobile phone/PDA market will be dominated by Android with a variety of other Linux based phones. I predict that some time after five years the iPhone will go away. Chris Samuel has made some predictions too [3]. He predicts that within two years The distinction between laptops, netbooks and mobile phones will get even more blurred with consumers demanding mobiles with more power and lighter and lighter laptops/netbooks . I believe that the difference between laptops, netbooks, and mobile phones is primarily one of IO (size of keyboard, sockets for peripherals, and size of screen). For desktop use the only application I use which requires more RAM or CPU power than my EeePC 701 can provide is Firefox. A combination of more efficient javascript interpretation and better coding practices by web designers would solve that problem. A significant portion of the mass of a laptop is dedicated to suppporting IO ports and maintaining the structural integrity of the device. A common feature in science fiction is lapotops that can be rolled up, stretched to size, etc (the Thinkpad Butterfly keyboard was an attempt at a first step towards this which failed due to issues of mechanical strength). As some Netbook class systems already have 3G networking built in it seems a logical extension to have telephony functions built in to a laptop. I predict that laptops with full telephony support will go on sale in 2010. One promising feature in regard to laptop IO is the new Display Port [4] video port. It will only be an incremental improvement to the space taken for IO capacity, but I am not expecting anything revolutionary in the near future. I predict that HDMI will be a failure in the market and DVI will never gain critical market share, it will be VGA and Display Port on most systems by 2012. Predicting that technological developments won t happen is always risky, but I predict that the mechanical issues which separate the heavier laptops and desktop-replacements from netbooks (in terms of making a large display and keyboard that won t break frequently) won t be solved within five years. In the same note, I don t expect anyone to try building a mobile phone which can have a full-size screen and keyboard connected to it (although it would be possible to do so). So I expect that the phone/PDA, Netbook, and laptop distinction will remain for at least the next 5 years. One thing that would make sense is to have a small device (PDA or mobile phone) store data that is security relevant and connect it to full-size machines for serious work. So for example you could use a desktop machine for Internet banking (maybe in an Internet cafe) and have your mobile phone ask you to confirm the transaction and then authenticate you to the bank server. I predict a larger role for PDAs and mobile phones as computers as soon as people start to take security seriously. I won t try and guess when that might be, but I predict that it won t be for at least five years. I predict that increasing oil prices will significantly make a significant impact on the price of computers before the end of 2010. Not that I expect the prices to suddenly jump upwards, it s more likely that prices will steadily increase while at the same time new technology to reduce production expenses in other areas is introduced. I also predict that increasing oil prices will increase the desire to maintain systems for longer periods of time without maintenance. For example my Thinkpad T41p has had a few significant part replacements (a couple of motherboards, half the case, and a few keyboard replacements). This is OK while plastic costs almost nothing and the manufacturing expenses are also very low. But in future I expect that people will want laptops that can run for years without needing part replacments and which have a service life of 10 years or more. This requirement for strength will counteract the demand for laptops that are as light as netbooks.

• [1] http://www.flamingspork.com/blog/2008/11/09/technology-predictions/


• [2] http://valhenson.livejournal.com/25228.html


• [3] http://www.csamuel.org/2008/11/09/technology-predictions


• [4] http://en.wikipedia.org/wiki/Displayport