If you read the literature on tricksters, you will confront a string of words that capture the moral quality and sensibilities of these figures, figures scattered across time and place and largely enshrined in myths and stories:

Cunning, deceit, lying, provocateur, mischief, audacious, thief, play, shrewdness, audacity, grotesque, over the top, appetite, shocking, fun, delight, wit, trap, subversive, ability, wanderer.

These figures, which include Coyote, Loki, Hermes, and Eshu, among many more, push the envelope of what is morally acceptable and in so doing, argues Lewis Hyde (in his tome on the subject), renew and revitalize culture, especially the moral stuff of culture. They are not only boundary crossers, they are boundary makers. As the title of his book so succinctly and masterfully broadcasts Trickster Makes this World. Or as he suggests with a bit more elaboration:

I want to argue a paradox that the myth asserts: that the origins, liveliness, and durability of cultures require that there be a space for figures whose function is to uncover and disrupt the very things that cultures are based on p. 9

At the opening of the book, Hyde asks whether there are tricksters in modern industrial societies. His answer is a plain no. The con man who might share some similarities does not qualify. For in fact what is needed is either a polytheistic system or lacking that, he needs at least a relationship to other powers, to people, to instructions, and traditions that can manage the odd double attitude of both insisting that boundaries be respected and recognizing that in the long run their liveliness depends on having those boundaries regularly distributed p.13 He does locate the spirit of the trickster in spirited individuals: in Picasso, in Frederick Douglass, in laudable figures who push certain boundaries and renew our world for the better but nonetheless fall short of the archetypal trickster. I bet it is pretty obvious where I am going with all of this given my object of study: phreakers, hackers, and trollers. The trickster does exist across America, across Europe, really across the world and it is not in myth but in embodied in group and living practice: in that of the prankster, hacker, the phreaker, the troller (all of whom, have their own unique elements of course, but so does each trickster). Their relationship to other powers are many and can be located in terms of information, intellectual property, the government, language itself, institutions of power like the FBI and AT&T. The list is not short. For a few years now I have been thinking about the linkages between the trickster and hackers as well as the troller but it was only in the fall when I found myself trapped in a hospital for a week that I finally cracked open the book by Hyde and devoured it. Within a the first few pages, it was undeniable: there are many links to be made between the trickster and hacking. Many of these figures, push boundaries of all sorts: they upset ideas of propriety and property; they use their sharpened wits sometimes for play, sometimes for political ends; they get trapped by their cunning (which happens ALL the time with tricksters! That is how they learn); and they remake the world, technically, socially, and legally and includes software, licensing and even forms of literature (think textfile, the Jargon File or most dramatically, ED). But if the trickster generally resides in myth, and the trickster of the information age resides in practice, myth matters everywhere because there is a mythos created around these figures. Sometimes the mythos is propagated these groups (take a look of ED for example or Phrack in the past) and of course the media has played an undeniable role. And yet, unlike what is represented in the pages of Hyde, there are living, actual bodies in motion, in conversation, in transformation, a group that goes far beyond the other more controlled and bounded tricksters we might be able to locate in society, such as artistic/political groups like the Yes Men. But the most shocking (or hard to think through) element lies less in the many associations one can make, but in the following curious fact. For the most part the trickster is enshrined in myth and stories but the tricksters I am referring to are in fact full-bodied, full-blooded groups of people who are actually engaging in all sorts of acts of trickery. This is culture not in the sense of art and myth but people and practice and this of course makes an (ethical) difference. What happens when you are the recipient not of a story offered an elder, but the recipient of trickery, an act of pranking or trolling, for example? What happens when you can trace all sorts of instances of boundary re-shifting and remaking, as with the GPL? I think this, even more than the linkages, is what makes this connection so remarkable and I trying to think through what it means to have a figure that we can find and talk to, as opposed to one embodied in myth and story. For now I am going to leave this post short and in the next installment, will start raising some of the connections between trickery and variants of hacking and trolling.

If you read the literature on tricksters, you will confront a string of words that capture the moral quality and sensibilities of these figures, figures scattered across time and place and largely enshrined in myths and stories:

Cunning, deceit, lying, provocateur, mischief, audacious, thief, play, shrewdness, audacity, grotesque, over the top, appetite, shocking, fun, delight, wit, trap, subversive, ability, wanderer.

These figures, which include Coyote, Loki, Hermes, and Eshu, among many more, push the envelope of what is morally acceptable and in so doing, argues Lewis Hyde (in his tome on the subject), renew and revitalize culture, especially the moral stuff of culture. They are not only boundary crossers, they are boundary makers. As the title of his book so succinctly and masterfully broadcasts Trickster Makes this World. Or as he suggests with a bit more elaboration:

I want to argue a paradox that the myth asserts: that the origins, liveliness, and durability of cultures require that there be a space for figures whose function is to uncover and disrupt the very things that cultures are based on p. 9

At the opening of the book, Hyde asks whether there are tricksters in modern industrial societies. His answer is a plain no. The con man who might share some similarities does not qualify. For in fact what is needed is either a polytheistic system or lacking that, he needs at least a relationship to other powers, to people, to instructions, and traditions that can manage the odd double attitude of both insisting that boundaries be respected and recognizing that in the long run their liveliness depends on having those boundaries regularly distributed p.13 He does locate the spirit of the trickster in spirited individuals: in Picasso, in Frederick Douglass, in laudable figures who push certain boundaries and renew our world for the better but nonetheless fall short of the archetypal trickster. I bet it is pretty obvious where I am going with all of this given my object of study: phreakers, hackers, and trollers. The trickster does exist across America, across Europe, really across the world and it is not in myth but in embodied in group and living practice: in that of the prankster, hacker, the phreaker, the troller (all of whom, have their own unique elements of course, but so does each trickster). Their relationship to other powers are many and can be located in terms of information, intellectual property, the government, language itself, institutions of power like the FBI and AT&T. The list is not short. For a few years now I have been thinking about the linkages between the trickster and hackers as well as the troller but it was only in the fall when I found myself trapped in a hospital for a week that I finally cracked open the book by Hyde and devoured it. Within a the first few pages, it was undeniable: there are many links to be made between the trickster and hacking. Many of these figures, push boundaries of all sorts: they upset ideas of propriety and property; they use their sharpened wits sometimes for play, sometimes for political ends; they get trapped by their cunning (which happens ALL the time with tricksters! That is how they learn); and they remake the world, technically, socially, and legally and includes software, licensing and even forms of literature (think textfile, the Jargon File or most dramatically, ED). But if the trickster generally resides in myth, and the trickster of the information age resides in practice, myth matters everywhere because there is a mythos created around these figures. Sometimes the mythos is propagated these groups (take a look of ED for example or Phrack in the past) and of course the media has played an undeniable role. And yet, unlike what is represented in the pages of Hyde, there are living, actual bodies in motion, in conversation, in transformation, a group that goes far beyond the other more controlled and bounded tricksters we might be able to locate in society, such as artistic/political groups like the Yes Men. But the most shocking (or hard to think through) element lies less in the many associations one can make, but in the following curious fact. For the most part the trickster is enshrined in myth and stories but the tricksters I am referring to are in fact full-bodied, full-blooded groups of people who are actually engaging in all sorts of acts of trickery. This is culture not in the sense of art and myth but people and practice and this of course makes an (ethical) difference. What happens when you are the recipient not of a story offered an elder, but the recipient of trickery, an act of pranking or trolling, for example? What happens when you can trace all sorts of instances of boundary re-shifting and remaking, as with the GPL? I think this, even more than the linkages, is what makes this connection so remarkable and I trying to think through what it means to have a figure that we can find and talk to, as opposed to one embodied in myth and story. For now I am going to leave this post short and in the next installment, will start raising some of the connections between trickery and variants of hacking and trolling.

Two weeks ago I got myself a nokia n900 phone which is running maemo 5. So far I am quite happy with it, given that my previous phone was a sony erricsson p1i which is pretty crappy.
I've taken some notes about my experiences:

• under normal use the battery lasts for ~ 2 days, if I'm using 3G the whole day I need to recharge it daily though


• the terminal has a bug which results in the enter key not working under some conditions, ctrl-m works as a workaround though


• playing normal dvdrips in mplayer is absolutely no problem without downscaling, 720p doesn't perform though


• I somehow managed that my screen flipped and I wasn't able to flip it back, only a reboot solved that


• It is not clear to me which tools you will find in the list of installable packages and which are only visible with apt-cache search. I also managed to end up with a doubled launch icon in my application list for some application


• the termininal is not usable anymore after an ncurses program crashed, "reset" doesnt help either


• wireless uses less battery than umts, way less


• the back button in the browser is per default opening a fancy eyecandy browse history which is slow, so I mostly use backspace to browse back


• there is lots of useful tools in the extras-devel repository, e.g. I can control my mpd via mmpc from the phone which is great



• importing contacts works flawlessly, also merging existing contacts works as expected


• jabber (including xmpp calls) are integrated in the contacts information (you can merge a jabber uid into an existing contact)


• i've no idea yet what the internal video player is, but i wasn't able to play a non downscaled XviD file with it, mplayer does play it fine


• freely placeable widgets are awesome


• it's is really userfriendly and no geeky linux user phone


• i would prefer not having busybox per default, i can install bash but the libc is still from busybox which implies world readable password hashes in /etc/passwd, so no other user accounts on my mobile


• is there disk encryption available?


• n900fly can't cause any good


• gps with nokia maps is ok and I find it pretty usable even if a google maps client would be nice as well


• the mp3 mplayer sucks unless you have tagged your music properly, you can't just play some folder without having a playlist for it


• mplayer as an alternative from the console is no real alternative either, if you don't redirect its output to /dev/null it gets stuck in a loop when the display blanks,


• app manager locks dpkg lock even if you just list available programs, no idea why this is needed and no idea how aptitude and synaptic are doing this


• is there a good todo manager which comes with a widget listing todos?


• is it possible to install armel debian packages without having a debian chroot?


• sms are nicely organized per contact in an instant messaging fashion


• the builtin accelerator works nice and you can automatically flip the screen when you want to dial a number, sometimes happens by accident though


• the multiuser support works awesome and you get a nice overview of open applications in a compos fashion, it may be wise to have not 40 applications open though


• the list of processes is already huge (like 160 processes running in the background)


• i haven't checked out the sdk yet but I will do that soon as I need e.g. newsbeuter for RSS


• hardware feels robust, arm cortex a8 is imho a very good processor, RAM could be more (the phone is heavily swapping)


• you can not yet use the phone as a wireless access point without building your own kernel images, some people seem to be working on this


• you can manipulate all kinds of stuff through the sysfs, including the phone led and the vibration


• wireless certificates are sometimes shown to be invalid but there there is no details button, you can click only "done"

Those are the things I came up with while using the phone. The calling functionality and everything which is only phone related really works fine and the sound quality while talking to someone on the phone is also really good. So far I am really happy with the phone and I can only recommend it. I hope I'll have some time to port some applications to maemo soon.

You work on developing a software forge, you re an admin for a software forge, or a project administrator. Join us and discuss (in english) forge matters on discussions@planetforge.org, to try and improve communication, sharing, reuse and interoperability among various hosting platforms, and collaborative development tools. You may prefer joining the PlanetForge RSS aggregator if you blog about forges (feel free to add it to your preferred RSS reader).

As part of COCLICO, we re working on an exchange format for forges, that should help dump, restore, export and import from different software forges. There are various use cases for this, like moving a project from one forge to another, but also as backup/restore feature for forge admins. More about the rationale here. We d like this format to be a standard some day, so it should have good properties so that it s generic enough and at the same time easy to adopt. Thus it would be relatively easy to contribute new exporters or importers to an framework (for which we ll implement basic core tools), while having a long-lasting format that can still be used in the future. A lot of work ahead of us, and this is just a short notice in case you re interested and you d like to know more Stay tuned, and if interested, join discussions@planetforge.org to discuss this topic. P.S.: yes, it s a rebirth of CoopX, somehow (see the coopx tag in my blog for more details)

The main sources of information used when hiring someone are their CV, the interview, and references. CV The CV is written by the applicant or sometimes for the applicant. Naturally it says only good things, if a CV notes no skill in a particular area then it may be used to exclude an employee from consideration. But the trend is towards including a reference to anything that you touch, so someone who lists DBA experience may merely have done a couple of CREATE TABLE operations. Interview The interview is a good test of people skills but is often of little value in assessing technical skills. The interviewer asks questions such as do you know technology X and the applicant says I know that really well . If the company is hiring another person with similar skills to current employees then they can have their current employees sit in on the interview and ask difficult technical questions, but for unknown reasons managers often don t take that option and get no advice from their technical people. Also if the company is hiring someone with specialised skills (EG they are about to implement a new application and want to hire their first employee to work on it) then it may be impossible for them to assess the technical merit of answers. Probably the best use of the interview is to match answers with the CV, if the applicant doesn t appear to know the contents of their own CV then they should be rejected. The biggest problem with interviews is when the questions are all of the form do you know X . Someone who really knows it will say yes as will someone who doesn t know enough to realise the limits of their knowledge and such ignorant people vastly outnumber the skillful people. The real problem is that the people who are moderately skillful will lose out. If someone asks me about my MySQL skills I will tell them that I m not really good at it. Sure I ve run replicated servers with tens of thousands of users running 24*7, but that doesn t mean I m really good at it probably most people who will claim to be great at MySQL without qualification would have less experience than me. References Reference checks rely on an unknown person saying good things about the applicant. For starters there is the issue of the number of references which may not be representative of their employment history EG the applicant could use as a reference the one manager who didn t sack them. The next issue is that there is little incentive for the referee to be honest, most people are aware of instances where someone once worked for a friend and can rely on good references for the rest of their career. If a reference is inaccurate then there is no realistic opportunity for redress. Finally every reference check that I am aware of (checks where I have been the referee or the applicant) has involved the applicant giving the phone number of the referee to the hiring manager! The phone could be owned by a friend or relative of the applicant, so logically a good reference that is based on trusting the applicant to supply the phone number only proves that the applicant is either good or really bad. To make a reference check prove something the recruiter would at a minimum have to phone the number listed in the white-pages for the corporation that used to employ the applicant, asks to speak to the manager of the relevant department, and then gets a reference. Calling a mobile phone number that is supplied by the applicant (which seems to be the standard practice) is essentially trusting the applicant and trust is the root cause of most security problems! Really most of this ends up as trusting the applicant to provide honest evidence that they are trustworthy and believing that the applicant s technical knowledge is good enough to be correct when they say that their technical knowledge is good. It can fail spectacularly when someone isn t trustworthy enough to provide honest evidence of their integrity or when someone doesn t have the skills needed to know that their skills are lacking. As an aside, even if the reference is given accurately and in good faith it may still be misinterpreted. The fact that telephone references are exclusively relied on exacerbates this problem. Ideally references would be in writing with some way of proving their authenticity (maybe using phone verification of the accuracy of the written document). Solutions So how can we solve this? Some people believe that career based social networking software will solve the problems, but as usual I think that software doesn t magically solve human problems. The first challenge when trying to use social networking to solve the problem is to find someone on your friends list who has relevant knowledge, this may be viable in a small industry (EG when someone from bank A applies for work as bank B in the same city). The next issue is that of false friends . I m sure that I m not the only person who has been pressured to add people as friends on social networking sites, the non-computer social interactions really don t prepare people for saying no you are not my friend (apart from high-school I guess). With professional social networking sites there are further issues, if you are working on a client site and a manager demands that they be listed as one of your friends then what are you going to do? So it seems to me that the social networking sites are at best a helper for the gossip network. If you think that a friend of a friend from a social networking site might be able to help you then you first ask your friend if the person in question is really a friend, and if so are they one of the shifty pseudo-friends you only hang out with because their company pays good money. But the problem with the gossip network is that it s mostly secret and is therefore subject to settling vendettas, I ve heard of senior managers going out of their way to spread false stories about former employees to settle scores. The best solution I can think of is for someone who has a reputation to publicly stake it on the accuracy of their references. If I m going to give a reference then I would be happy to do so via a GPG signed email or a blog post. This doesn t mean that my references will always be correct, but it would show that I try to give good references.

I had previously sought alternative, innovative search engines, but none of the proposed options made me particularly happy. About a year ago, I came across DuckDuckGo, and today, I ve been using DDG as my primary search provider for exactly 10 months. The reasons why I switched included

• my dislike of the Google information monopoly and the potential that a single, corporate entity with financial interests, gets to censor the information I see. I am sceptical of their Do-no-evil promise because there s nothing binding about it, and if it gets in the way of money-making, I am sure it ll be discarded at a whim if it even still exists.
• the awareness that my usage augments their database (although I am probably too far away from mainstream to provide useful data), which translates into more funds available to them to further strengthen their market position.
• my belief that the days of index-based searches are over, given how 95% (or more) of user-generated content is bogus. Google undoubtedly optimises the results with obscure, secret algorithms, but that s just not enough for me.
• Of course the name DuckDuckGo was perhaps the strongest reason to switch. :)

I am aware that DuckDuckGo is index-based itself, using the Yahoo API, which, in turns means that DuckDuckGo may already be using Bing data. Sounds a bit like out of the frying pan into the fire, unfortunately. I am still investigating better search solutions, sticking with DuckDuckGo meanwhile. Unfortunately, DuckDuckGo doesn t quite cut the mustard at all times, forcing me to go to Google instead. For this reason I am glad to find that the CustomizeGoogle Firefox extension has not been discontinued, but simply renamed to OptimizeGoogle. This extension allows me to anonymise my identity towards Google, remove click tracking (which Google doesn t want you to know about and hence hide with JavaScript), hide ads, and customise a slew of other aspects of the giant s search engine. It alleviates some of the aforementioned concerns, but not all. Maybe it s time to rethink the way I use the web and lower my search needs. If you are using Firefox, try it out! If you re still using Internet Exploder, you should not, and instead upgrade to Firefox. Users of other browsers might find similar functionality for their application, or might want to switch as well. NP: Tunng: Comments from the Inner Chorus

I d draw a caricature involving a Toyota car, representing capitalism, with a stuck gas petal and Barack Obama trying to fix it. But as I cannot draw very well, especially recognizable people, I created this collage: The photo of Obama was created by Beth Rankin.

So far the networking of virtual machines has usually been managed by configuring a Virtual Ethernet Bridge (VEB) in the host, i.e. the good old implementation of 802.1D in the Linux Kernel:

A Virtual Ethernet Bridge (VEB) is a capability within a physical end station that supports local bridging between multiple virtual end stations and (optionally) the external bridging environment.

While this works well and in some cases is the best solution, in other setups performances or policy needs dictate that the traffic between virtual machines is forwarded to an external bridge (the Ethernet switch connected to the host) and back without having in the host a real bridge learning MAC addresses from its ports and implementing the STP. Enters the VEPA:

A Virtual Ethernet Port Aggregator (VEPA) is a capability within a physical end station that collaborates with an adjacent, external bridge to provide bridging support between multiple virtual end stations and external networks. The VEPA collaborates by forwarding all station-originated frames to the adjacent bridge for frame processing and frame relay (including "hairpin" forwarding) and by steering and replicating frames received from the VEPA uplink to the appropriate destinations.

Support for VEPAs has been added to Linux 2.6.33 with a simple change to the macvlan driver. The next step will be to use the macvtap driver (available in 2.6.34), which exposes a tap character device usable by kvm-qemu and "connected" to a macvlan-like interface.

In November 2007, we bought two of the first Eee PC netbooks available in North America: the model 4G in pearl white, one for me, and one for my wife. My plan was to start the Debian Eee PC project and get Debian working on them both which, thanks to the work of everyone on the team, has been a great success. Fast forward to February 2010, and they are still serving us well. Here is a list of hardware enhancements and issues over the past two years of continuous use: Battery life Asus claims 3.5hrs for the model 4G, though I don t think we ever experienced anything better than 2.5 hrs with wifi in operation. Today, I m down to something short of 2 hrs. If you consider the Lithium ion battery article on Wikipedia to be accurate, it is typical to permanently lose 20% capacity per year, so this sounds about right for the age of the battery. Touchpad The touchpad itself is fine. The buttons are not. They are hard to push and prone to become less responsive after a while, or to fail entirely. I now really have to bear down hard on my left button to make it work. Because the buttons are soldered to the motherboard, they would be hard to replace. Configuring the synaptics driver for tap-to-click is an acceptable workaround. Also, one of the first purchases we made was the Logitech VX Nano, one for each Eee, so most of the time now, we use our mice, falling back to the touchpad only when using a mouse is inconvenient due to space constraints (e.g. on the bus). Keyboard After two years of continuous use, both of our keyboards needed replacing. Some of the keys had been pounded flat and needed surgery (rubber springs sliced out of a scavenged Acer netbook keyboard and grafted on) to make them usable again. And aesthetically, the keyboards have really suffered, with a good percentage of the markings on the keycaps partially or completely eroded off. Fortunately, for $3 plus $10 shipping each, new keyboards can be ordered from a Chinese e-Bay seller. But with the new keyboards, there is still the problem with excessive flex in the keyboard making some keys less responsive than others. I m considering trying this hack to solve the problem. Display I have no complaints about the matte finish displays of either Eee. Both have stood up well. People tell me they don t care for a 7 display, but I find it bright, crisp and easy to get along with, so long as you maximize windows and increase font size as needed (e.g. for reading PDF books and magazines). When I really need the extra real estate, I just hook up an external monitor. Fan Some people complain about the noise of the fan, from the otherwise silent 4G (due to the lack of a hard drive) and seek ways to limit the amount of time the fan runs. We ve never had that problem. However, if any plastic bits break off inside the Eee, they will eventually find their way to your fan and get wedged. This has happened twice: once in my wife s Eee, and once in mine. Disassembly of the Eee to clear the blockage and get the fan running again was relatively painless both times. Plastic bits About those plastic bits: In my wife s case, I think the bit was some extruded plastic from the molding that had broken off. In my case, it was a deteriorating plastic post which was holding the hinge in place. More about this later. Sound Unfortunately, the integrated sound seems to be particularly sensitive to heat. During both fan failures, sound cut out. On my wife s system, it never fully recovered, and now only works on alternate Tuesdays, whereas on mine, after I unwedged the fan and brought the heat down, sound has functioned properly ever since. (Update: see my comments below on power adapters for an alternate theory about what killed sound.) We are waiting now for the delivery of a cheap ($1.42 including shipping, again from China) 3D Sound USB device which is reported to work on Linux. While some users complain about hum with this device, we re cautiously optimistic that on the Eee it won t be an issue. If it is, oh well, a buck and a half is a small gamble. Display hinge The plastic posts that hold the anchors for the machine screws for the hinge are fragile. Three out of four of these posts in my Eee have shattered, leaving the left hinge to float freely. For the past two days I was distressed about how I could fix this. Based on some helpful suggestions from #eeepc @ irc.freenode.net, I had worked out a plan to rebuild one of the posts with two-part epoxy, sand it and the fractured stub of the post, and use cyanoacrylate glue to affix it to the case. It sounded like fiddly work for which I didn t hold much hope of success. But this morning, I realized that the plastic in the bottom of the case was still sound, and that I could drop a screw into that hole, and with pliers, line up the anchor on the other side. This appears to work! I ll handle that hinge with care, but it should do me until I eventually repurpose the machine to some daily use that is less stressful on the hinge than daily travel on the bus. SSD and SDHC Some people were initially worried that the limited write life an SSD meant that you needed to take special measures to avoid its premature death, which I have always regarded as a myth. Our 4G SSDs each have no swap space, and ext3 filesystems. At the two year point, there are no problems. I expect our SSDs to outlast the other components. We did, however, eventually find the 4G to be a bit on the small side. We now each have Kingston 4G micro-SDHC cards for a bit of extra capacity for large media files and for some extra space for the apt cache. I recently priced the Lexan version of this card at $19 for a two-pack at Wal-mart, and these seem to work in the model 4G just as well (which seems to be an issue with this model not all SDHC cards work). Memory We found the 512M that came with the 4G somewhat constraining. Without any swap space (so we could maximize the space available on the small SSD) we decided our systems really needed a memory upgrade. At the time, 2G didn t seem overly expensive (though I no longer remember the exact price) so we splurged on 2G for each system, even though that was probably more than we needed. Power adapter When I first wrote this article, I forgot to mention the power adapter. The model 4G uses an unusual 9.5V power adapter for which it is hard to find a generic replacement. This unit is prone to fail in two places: in rare cases, (one out of 6 units that I have in some way assisted with: 3 of them mine, 3 belonging to others,) it will break at the wall plug end. The plug swivels into the unit for easy storage, but this adds a point of failure. More commonly, (in 3 out of six of the units,) the wires at the netbook plug end will fray due to stress on the non-angled cord, leading either to no connect, or to a short. In fact, since in the case of my wife s adapter, the netbook end of the cable shorted, making the cable heat up and the system spontaneously shut down after a little while, we can t say for sure whether the overheating of the Eee took out integrated sound, or whether this short did. On the one hand, I know for certain my own system, which never suffered a short, has responded to overheating by making the sound flaky, but it has never taken out sound completely. On the other hand, shorting the power cable can t be very good for the Eee, so who knows, maybe that s what ultimately killed my wife s Eee s sound. This is where it helps to have soldering skills, or a friend who can do the repair for you. In my case, it was the latter. While I was waiting for a replacement adapter I had ordered, we also found on eeeuser.com part#s for replacement plugs and sleeves from Digikey, total cost $20 including shipping, 10 pieces each. Cutting off the bad plugs on three units and attaching the new was a quick, straightforward operation, and succeeded in two out of three cases. Having carefully checked the failed repair, we deduced that the failure in that unit was at the wall end, and we judged there was nothing further we could do to try to save it. Even the unit that had previously shorted was returned to perfect health and has been in operation trouble-free ever since. Conclusion After over two years of continuous use, the model 4G has held up well for a $400 system. We definitely feel we have received our money s worth of value over that time. All of the problems we ve experienced so far have been fixable at very little expense, and we expect them to last at least another year before we seriously consider replacing them. In the next several months, I plan to order a high capacity 8-cell 10400mAh battery for my own system so that I can enjoy a 5-6 hr run time. The purchase will be roughly $55 including shipping, the most expensive purchase for my system to date, but still well worth it to extend the 4G s lifespan for another year or more.

Ed Mayo talking to the Phone Co-op meeting Yesterday I had the pleasure to be at the Phone Co-ops annual meeting, as those of you who follow me on identi.ca or elsewhere will already know. The proceedings included a speech from Cooperatives-UK Chief Exec Ed Mayo that included the co-op pub in Salford, spurning David Beckham s gift and this summer s Co-operatives Fortnight. As ever, the bits I liked best were the lively question-and-answer sessions, both on Ed s speech and the annual report. I took notes and reproduce them below, but I didn t capture every question, or every answer and none of this is verbatim. Questions to Ed about UK cooperation included:

• Can people in the co-op pub smoke? No, there s a bit of drinking in meetings, but not smoking. Some heated debates in meetings are defused by a break to go refill the glasses.
• Gordon Brown and Labour are starting to talk about cooperatives more. What should we do? We need to stand on our own two feet, but expect to be treated equally. A Mutuals Manifesto will be out online next month. In regulation, having the telecoms networks opened up to co-ops and not be so limited would help. One interesting possibility is with football co-ops / supporters trusts: it s been suggested that a fan co-op should have the right to buy a club if supported by 75% of season ticket holders.
• With all the business collapses and Cadburys being bought, what is the temperature of interest in mutuals outside the movement? Good. The only AAA-rated bank in the world is the Rabobank co-op, but remember that co-ops are not immune to failure. Cadburys is not a co-op and was always vulnerable to the current investor-led rules changing its ownership. People are not necessarily thinking of co-ops, so we need to reach out. It s a cynical, apocalyptic age, so we need to prove what we re doing. coops14 is an opportunity. The co-op bank saw a surge in new accounts after it was highlighted in one newspaper as an alternative to excessive banker bonuses. We need to encourage people to act. Reminded of a quote that the trouble with the rat race is that even if you win, you re still a rat . Research shows that Britain today is a brutal and competitive place to grow up in, with only 45% of children trusting their friends. People have heard of cooperatives. We should try to build a more cooperative nation.
• Comment from the floor that the private sector won t take substantial cooperative competition lightly. We must look behind us and never give them a chance.
• Could the BBC become a co-op? Yes.

Questions about the annual report asked about:

• What is our target profit %? No hard target. This year s reduction was planned and it is still a profit.
• Why are we using UKMail instead of the Royal Mail? 10k price difference. It was a hard choice, debated by the board, but there is no co-op option and no particular preference for state ownership.
• Why are we considering energy supply? Telecoms is a deflationary market, so diversification is a wise move and energy supply is a top customer request.
• What is our churn rate? 1.5%/year, which is unsatisfactory to us, but still low by industry standards.
• Was the Avoco acquisition price too high? a good price by usual industry measurement (multiple of sales)
• Will we support coops14 Free and Open Source Software events, because there is an overlap? (I didn t catch the answer)
• Can we put leaflets in the shops? Matt Lane is working on this and other opportunities
• Can we encrypt bills and emails if customers want it? exec will take and deliberate on that
• Can we get some sales materials to Scotland? details taken to send them out next week

I propose a new feature for email software: Cosmetic carbon copy. CCC works very similarly to today's carbon copy feature: If you put an address in the CCC: list, when the recipients open the message, they can see the address. The one difference is that with "cosmetic" carbon copy, the CCC:d address never recieves the message. An example might illustrate the situation. Let's say someone (Alice) wants to invite Bob to a movie but doesn't want Charlie to come. She might send this email:

From: alice@example.com
To: bob@example.com
CCC: charlie@example.com
Subject: MOOOVIEEE!

Hey all my friends, join me for a movie tonight!

When Alice sends the email, Bob recives a copy. Bob thinks that Charlie received a copy, as he will be in the CC list. But Alice's mail software never sent Charlie a copy. So Alice can relax, knowing that Bob won't forward a copy to Charlie, since Bob thinks he already received it. Alice and Bob will meet up without Charlie, and Alice will quietly sigh in relief.

How can this work? Cosmetic carbon copy works on the same principle as blind carbon copy: the contents of the message are fundamentally independent from the recipients. Saavy email users have used the "blind carbon copy" feature for years. When you place an address in the BCC list, that address will receive a copy of the email even though other recipients won't see the address listed. This allows for a form of privacy between the sender of the email and that hidden recipient. This works because, like postal mail, email messages are delivered using an "envelope" that contains the actual recipients. When you compose a message in Alpine, Gmail, or Thunderbird, you are writing the contents of the envelope. When you hit send, the mail software looks for email addresses that should receive a copy. It creates one envelope per address, stuffs the letter inside, and sends the whole thing on its way through the Internet using a protocol called SMTP. When the recipient (Bob)'s email system receives it, the letter is pulled out of the envelope and placed in an inbox. Which means the envelope is entirely invisible to Bob, the recipient. Most mail software puts information about the envelope in email headers. Since each email recipient gets a separate envelope, In the case of cosmetic carbon copy, Alice's letter claims that Charlie was on the CC: list. But Bob can never learn that Charlie's copy was never sent. So to implement cosmetic carbon copy, Alice's mail program must understand this rule:

• For each address in the CCC list, copy the message to the CC: list in the email message.
• Create no new envelopes when sending the message.

Because of the last bullet point, this "carbon copying" is purely cosmetic rather than functional.

A possible privacy problem You might wonder, what happens when Bob hits reply-all to say "Yes, I'm coming"? Then (oh no!) Charlie might see the invitation. Not a problem: Most of my friends use Gmail, and Gmail users almost always hit Reply instead of Reply-All. Gmail used to have an experimental option called "Reply All by Default", but thankfully they removed that option. A future version of this specification might suggest mangling the last "." in the BCC:d email addresses with the ONE DOT LEADER character, which looks like "." but isn't one. That way, even if Bob clicks "Reply all," Charlie's email address is subtly incorrect and will bounce.

Future work The story I've told here is marginally simplified so it's understandable to a less-technical audience. Those who want a more technical version can request I submit an RFC. Perhaps in two months? (File under "games to play with email.")

FOSDEM is the usual awesomeness this year, I'm just too tired for too many words, so I'll keep this post very brief.

Once again, the videoteam needs your help. Please consider lending us your helping hands, so that we can record the room 1308 tomorrow/today (sunday) without burning out totally. From 10oo to 17oo there are seven talks scheduled with a total break time of 30min. And we are 3 or 4 people doing this, and have 4 jobs to fullfill: 2 camera operators, video and audio-mixer, not even mentioning handing microphones to the people in the audience. This obviously really cannot work.

So, if you can, please help us. Either just show up or even better, just show up and add yourself at the volunteer wiki page. Doing the latter will help us even more, as we can plan our ad-hoc work better.

Following an idea originated through contributions from Belgian beer, and to motivate zack a bit more to actually go for it, I've setup the alias leader@debian-community.org to point to his email address. Please send motivational emails ;-)

I've been trying to remember to post the pictures I like online for the past few months. So this is a reminder to myself. This image below didn't turn out quite how I wanted it to:

• I was hoping for a nicer sihouet upon the lady's face.
• The tree-branch on the left irritates me.

But that said I keep on coming back to look at it. I like the lighting, and I love the way that the brick wall on the right hand side angles towards the building on the horizon. Enjoy. Or not. A similarly "not perfect" image is this outdoor shot. I have only one irritation with this shot - and that is that the trees are clipped at the top. Meh, such is life. (I have two styles of photography; semi-random where I snap what is in front of me, and staged where I try to construct a particular picture - the two images above? One of each.) ObFilm: Bound

Stowe v Thomas (1853) where the court argued that a German translation of Uncle s Tom s Cabins did not constitute copyright infringement (quoted from Meredith McGill s excellent bookAmerican Literature and the Culture of Reprinting, 1834-1853:

Before publication [the author] has the exclusive possession of his invention. His dominion is perfect. But when he has published his book and given his thoughts, sentiments, knowledge or discoveries to the world, he can have no longer an exclusive possession of them. Such an appropriation becomes impossible, and is inconsistent with the object of publication. The author s conceptions have become common property of his readers, who cannot be deprived of the use of them, or their right to communicate them to others clothed in their own language, by lecture or by treatise

Stowe v Thomas (1853) where the court argued that a German translation of Uncle s Tom s Cabins did not constitute copyright infringement (quoted from Meredith McGill s excellent bookAmerican Literature and the Culture of Reprinting, 1834-1853:

Before publication [the author] has the exclusive possession of his invention. His dominion is perfect. But when he has published his book and given his thoughts, sentiments, knowledge or discoveries to the world, he can have no longer an exclusive possession of them. Such an appropriation becomes impossible, and is inconsistent with the object of publication. The author s conceptions have become common property of his readers, who cannot be deprived of the use of them, or their right to communicate them to others clothed in their own language, by lecture or by treatise

Quick public service announcement (which probably comes a bit too late, sorry): There's a coreboot developer room at this year's FOSDEM (Free and Open-Source Software Developer's European Meeting), which starts roughly... um... today. In 20 minutes, actually. Unfortunately I cannot be there, hopefully there will be video archives of the talks. If you're at FOSDEM already, here's the list of talks:

Sat 13:00-14:00 coreboot introduction (Peter Stuge)
Sat 14:00-15:00 coreboot and PC technical details (Peter Stuge)
Sat 15:00-16:00 ACPI and Suspend/Resume under coreboot (Rudolf Marek)
Sat 16:00-17:00 coreboot board porting (Rudolf Marek)
Sat 17:00-18:00 Flashrom, the universal flash tool (Carl-Daniel Hailfinger)
Sat 18:00-19:00 Flash enable BIOS reverse engineering (Luc Verhaegen)

Highly recommended stuff if you're interested in an open-source BIOS and/or open-source, cross-platform flash EEPROM programmer software.

I recently upgraded a critical file server at work, from etch to lenny. With that upgrade, samba version was bumped from 3.0.24 to 3.2.5. We were then hit by a quite severe bug where files ACLs are messed up on Excel files after saving the files (upstream #4308, fixed upstream in 3.2.8). I will probably consider fixing the official Lenny packages (there is no bug reported about this in Debian, though) along with a few other quite severe ACL-related bugs (Mathieu Parent, who maintains ctdb, pointed me to a few such bugs). However, I couldn't wait for such a long time and backporting the fix for #4308 isn't completely straightforward. So, I decided to upgrade our server to the latest Samba 3.2 version, namely 3.2.15 (upgrading to 3.4 series could bring other kind of regressions and we have no time to properly test everything...users already have their guns handy). This is where the Debian Samba packaging team unofficial repository becomes handy. It is meant as as service to users who want to run the very latest samba code and have the same packaging choices we have in supported Debian releases. We already had 3.2.14 there but I never took time to update to 3.2.15. This is done now. Moreover, as our production server uses the amd64 architecture, these unofficial backports are now available for both i386 (my usual build machine) and amd64. Using this repository is as easy as:

deb http://pkg-samba.alioth.debian.org/packages lenny-backports/
deb-src http://pkg-samba.alioth.debian.org/packages lenny-backports/

Please note that this APT source does not use GPG signing of Packages files. When I am less lazy, I'll try to at least sign it with my GPG key.

I got involved with open-source software before I learnt about software development in a university course. Naturally, when my profs tried to teach the waterfall model to me, I couldn t take them too seriously back then. After all, requirements specification design implementation verification maintenance is not really in line with the principle to release early, release often. Furthermore, since water cannot flow uphill, the waterfall model fails to represent development cycles, as they naturally appear, even in behemoth, ancient software nightmares. And yet, when embarking on a new project, I do tend to find myself first thinking about the big picture, instead of churning out the code. I am certainly not the best coder out there, and it might well be that I could benefit from learning to break down problems to get an earlier start on the implementation of components. However, I maintain that avoiding the waterfalls and engaging directly in extreme programming, agile software development, or pair-based approaches right away is not the answer. Rather, the best approach should probably involve a certain level of conceptualisation before code is produced. I am a big fan of test-driven development, and I like the scrum method for the very reason that it involves talking and challenging ideas (although I wouldn t follow the method down to the book). I like to think about trickles in the mountains where water droplets joyfully jump around. * * * When Glyn Moody spoke in his LCA2010 keynote about challenges we (as in society) face, and how open-source seems to have many answers, he dropped the following gem, which spoke right to my heart:

Twitter is the release early, release often principle applied to thinking.

By this simile, journal articles are produced according to the waterfall model. This may well be why they are usually outdated at the time of publication. Microblogging (like Twitter), on the other hand, is primarily used to publish stuff before it s ready, and which would never be published otherwise. With journals on one end, and microblogging on the other, I think the epiphany is found in between as with software development: web logs web applications that allow for easy publishing by anyone (which is a different problem not to be discussed here). Since articles on those platforms usually have at least a title and a body, they require just a little bit more thought than 140 characters of contracted brain farts, spilled into the world faster than it takes one to stand up, stretch, and sit down again. * * * Microblogging seems to be in line with where we re heading: more information, more self-promotion, more access to more people, and all that with lower barriers of entry. It s hard to argue against a trend, but I think we ve taken a wrong turn somewhere. The one specific instance of content is no longer relevant, and there is no more time in the day to read elaborate treatments of subject matters. Instead, what seems to prevail is a constant flow. This flow threatens to replace actual thinking and discourse, both of which require reflection and time a scarce resource used up by ever new, fast-flowing media. It seems to me that those who immersed in this flow are unable to get out, as if sucked in by a maelstrom. I ve seen people enter serious withdrawal within hours of not knowing what s going on in the world. One could miss out on something. If you re following people on one of those microblogging platforms, I challenge you to spend the weekend offline and when the urge hits, ask yourself what you are actually missing. I mean what you are really missing, and by that I mean anything other than the cozy buzz and hum of entertainment washed upon you, preventing you from having to think about what you could be (actively) doing instead. I hope it s not a lot. For else, I fear that this means that future generations will be stuck with this communication culture, just like water droplets can t ever play in the mountain trickle again. NP: Sola Rosa: Get It Together

A picture is worth a thousand words: A slightly longer story follows, resuming from the previous episode, where Gtk seemed to be working. Making sure Gtk actually works Since the udebs are quite fat already, I decided to put the contents of the gtk2.0-examples package into a new revision of the new libgtk-x11-udeb package. gtk-demo was running fine (if one forgets that this demo application is really easier to deal with if one uses a window manager), although image handling was broken. Julien and I spent quite some time double-checking that the libpixbufloader-png.so plugin was present; that both previous DirectFB-based udeb and new x11-based udeb were very similar; that configuration was generated properly; we went so far as to include strace in the netboot image, and to check the configuration file was open() d, but the plugin was never to be even looked for. All this resulting in a Unrecognized file format message every time. Josselin, our Messiah, enlightened us: although Gtk was previously using some configuration files to determine which pixbufloader plugin to use, it still continues to access those files but relies on a MIME database in the end. Installing the host s /usr/share/mime/mime.cache database did the trick (we have a proper fix pending), and all of a sudden, we got image support (which is needed for the logo_installer.png displayed on top of every screen, as well as for some icons during the installation, like the final one). Tweaking d-i itself Julien took care of rootskel-gtk. It was mostly about:

• Dropping some DirectFB start-up scripts.
• Dropping a related configuration file.
• Adding a start-up script doing trivial things:

  Xorg -retro -noreset &
  export DISPLAY=:0
  

Another easy step was cdebconf. Mostly: search and destroy on the few bits using DirectFB. An interesting issue we had was that even though a proper cursor theme was installed and made the default, we only had a black cross as X pointer. That s where we learnt it s needed to manually set a cursor for the root window, which can be done this way:

GdkCursor *cursor = gdk_cursor_new(GDK_LEFT_PTR);
gdk_window_set_cursor(gdk_get_default_root_window(), cursor);
gdk_cursor_unref(cursor);

Tweaking gtk2-engines was trivial, just a matter of building against the x11 flavour of Gtk instead of the directfb one. Some substitutions in debian/control and debian/rules, and that was done. Julien also took care of tweaking console-setup so that keyboard-configuration s and console-setup-udeb s postinst scripts call setxkbmap when $DISPLAY is set. Meaning we were able to replace kbd-chooser with console-setup-udeb, leading to a correct setting within X right after having selected the layout! Reverting d-i s r61645 (which disabled Gtk-based d-i images) was trivial (although while looking back, it was probably unnecessary), and after having messed around with the packages lists (there s a lot of local udebs at this point), especially to add some fonts, we managed to get an image which seems to work fine (at least in my VirtualBox environment). I tried Chinese, Japanese, Arabic, and French installations, and all of them seem to work fine (installed systems were bootable after an installation in the selected language) while issues were limited to some rendering or translation glitches, which didn t seem critical at all. Next steps Since there were some iterations, and since the trial-and-error approach was chosen, the first goal is to generate clean patches against all modified packages, and make sure a single walk through all packages in a clean chroot is sufficient to generate a working d-i image again. Once that done, which should probably considered (at least, I hope!) quite a good base already, the idea is to look into the various udebs to see whether there are some parts that could be disabled (maybe introducing a trimmed-down flavour especially for the udeb in some non-flavoured-yet libraries), so as to reduce the size of the resulting image. In the meanwhile, one can fetch the current hand-built netboot image by browsing http://people.debian.org/~kibi/di-x11/. It s only available for amd64, and weights 23MB. There s a sha256sum as well as a detached GPG signature in the same directory.