I just uploaded openbox-3.4.7-2 to Debian unstable and wrote a patch that enables to set next or prev to the monitor attribute of the MoveResizeTo action. Without this patch you need to explicitly set a monitor number you want to send a window to but can't just toggle a window from one workspace to the other with one keybinding or to move it to the next/prev if you have 3 or more monitors. So if you use openbox with a xinerama setup it would be nice if you could test that and report bugs in case of errors.

A keybinding for that could like like:

I just uploaded openbox-3.4.7-2 to Debian unstable and wrote a patch that enables to set next or prev to the monitor attribute of the MoveResizeTo action. Without this patch you need to explicitly set a monitor number you want to send a window to but can't just toggle a window from one workspace to the other with one keybinding or to move it to the next/prev if you have 3 or more monitors. So if you use openbox with a xinerama setup it would be nice if you could test that and report bugs in case of errors.

A keybinding for that could like like:

Every now and then, I want to understand a bit better English. Today, when Joeyh mentioned nettle soup, I had to ask Wikipedia what a nettle is. And Joey, no wonder it itches... It refers to around 45 species of genus Urtica in the family Urticaceae - In Spanish, of course, urtica is known as ortiga, or as blind person's herb, as even a blind person will quickly recognize it to touch - Touching it will cause the apt-named urticaria, which Joey seems to have discovered and learnt to fear. At least in Spanish, urticaria is generalized and used to call all kinds of skin diseases.
It happens to be a very common plant in the area I live and dwell in (the ecological reserve REPSA spans a good portion of the University, and limits my neighbourhood), a large extension of Southern Mexico City where the lava of the small Xitle volcano covered everything, rendering a good portion of the Mexico City valley unfertile, known as malpa s (badland, literally).
Anyway... I don't think I'll rush to cut some ortigas and make them into soup, as both Joeyh and Wikipedia (Spanish and English versions) suggest. But it is always an option, having so many fine specimens around.
This posting serves no other purpose than to show my appreciation to the Mexico City Area

Jane St. (OCaml) Core in Debian As recently announced, core has landed. It is an alternative/extended OCaml standard library developed by Jane Street Capital. At first sight it looks like ground breaking: a well-engineered standard library fixing several shortcomings of OCaml legacy standard library, both in terms of missing functionalities and syntactic sugar (e.g. the monadic operators which everybody was basically re-defining from scratch in their own code). After a day-n-half of work I'm proud to announce that core is now available in Debian. It took me a while as we were missing several of core dependencies. Overall, the resulting new 5 source packages are bin-prot, ocaml-res, janest-core, type-conv, sexplib310. All of them as been uploaded to experimental; beside sexplib (which went through NEW in just a few hours!!), the other 4 are sitting in NEW. In the meantime you can take the packages from my people.d.o space. I haven't yet uploaded them to unstable because some more audit is required for dependencies (e.g. I haven't build them in cowbuilder due to some annoyance related to the current Perl 5.10 transition). The only annoying aspect of the whole business is that bin-prot is ATM supported only little endian architectures, and this is inherited by core ...

I did some 'playing' with Hecl the other day, to see what it might look like if implemented in a slightly different way, and I thought I'd share what I was thinking about. Keep in mind that

1. I haven't thought this through completely:-)
2. It's not something I'm going to just rush out and do in the near future. It's definitely a Hecl 2.0 sort of idea.

My notion was to make use of the ClassCommand feature to have at least simple types be hooked directly to the relevant Java types, and dealt with through methods, rather than commands. For instance:

$i + 10

instead of

+ $i 10

Where $i is, in the first case, a Java Integer, rather than a Hecl type. What it would be doing internally is something like this:

1. $i is recognized as the object to act on.
2. It's an Integer, so the corresponding ClassCommand is looked up and executed with + and 10 as arguments.
3. The classcommand for Integer has a + method that accepts an argument, in this case, 10, which is added to the value of $i, and returned as a new Integer.

Without a "real" (where real also means bloated, memory and space hungry) parser, Hecl is never going to have a C-like syntax - you still wouldn't be able to do foo = 1 + 2 + 3 - but this just might make a significant amount of people more comfortable with Hecl, which would be a good thing. You could do something like this:

set i 1
while   $i < 1000000    
    set i [$i + 1]
 

instead of

set i 1
while   < $i 1000000    
    set i [+ $i 1]
 

I actually built a really simple HeclInteger class that implements < and + as methods to Integer ObjectThings, in order to test out this idea, and it seems to run about as fast as the regular Hecl version. I welcome any thoughts or comments on the idea.

For the past couple of days, one of my e-mail addresses has been some spammer's choice for forged From: lines in their spew. So, as invalid addresses aren't high on a spammer's list of priorities, I get all the bounces. The fact that MTAs, in this day and age, don't have SMTP session recipient validation is unpleasant. However, with ISPs requiring all outgoing e-mail to go through their own servers, I can kinda see where that can break down. I still don't like it, but I'll live with it. In amongst all the bounces, though, there's a lot of other, really obnoxious, crap. So far, I've had five "please click this link / reply to this e-mail so it'll go through" (AKA "please filter my spam for me")[1]. I've also had a large number of e-mails saying that my e-mail was blocked or unwanted or whatever, from spam filtering programs themselves. What I haven't got any of, as far as I can determine, is any e-mail from enraged recipients saying "stop sending me this crap!" or anything of that nature. The only conclusion I can reasonably draw from this data is that users know that source addresses are forged and there's no point replying to them, but the people whose job it is to write, maintain, and run spam software don't. That's downright embarrassing. Not a single user was dumb enough to assume that I really sent the e-mail, but IT "professionals" who deal with spam for a living are. If you are in any way involved in the production, sale, or use of an anti-spam product that hasn't realised that the from addresses of spams are universally forged, please shoot yourself in the head. Really. I'm sick to death of people who should know better doing the most stunningly stupid things regardless. If you don't know that your software is spamming the rest of the world, then you're still on the hook. What other dumb shit is your system doing that you know nothing about? On the other hand, if you do know that your spam filter is contributing to the noise, you're even worse -- no spam has a real source address. If your software or system spews crap because some clueless manager told you to do it, then you need to grow some courage and ponder on the words of Napoleon:

A commander-in-chief cannot take as an excuse for his mistakes in warfare an order given by his sovereign or his minister, when the person giving the order is absent from the field of operations and is imperfectly aware or wholly unaware of the latest state of affairs. It follows that any commander-in-chief who undertakes to carry out a plan which he considers defective is at fault; he must put forward his reasons, insist on the plan being changed, and finally tender his resignation rather than be the instrument of his army's downfall.

In other words, if you did it and you know you shouldn't have, it's still your fault, regardless of why you did it. Take some responsibility for your actions, for fucks sake.

---

[1. Every single one of which I was more than happy to confirm -- if you want other people to do a job for you, you have to deal with the fact that some of them might not do it in quite the way you expect. I encourage anyone else who thinks that an anti-spam system that requires the rest of the world to filter your inbox is stupid (even disregarding the likely problems of infinite loops if everyone had a challenge-response inbox) to do the same.

Sune, I have begun to think that it might actually be useful if many people replied to this kind of backscatter and make sure, that the mailsystem works as intended. Mail gets delivered. (Or not, as it's recognized as spam. Something which is possible in 2008.)

I was pleased to learn through Christer Edwards of the existence of a sister project in Ubuntu to our Debian Eee PC project. I followed up on his invitation to drop in on their irc channel and introduce myself. I’ve been looking over the bugs listed on their TODO to see if any are applicable to Debian. Already I have filed #479217 based on the corresponding bug in Ubuntu, and have encouraged them to check out ours as well. I look forward to sharing more with them in the future so we can benefit from each other’s work.

Lets go on your nerves again with a ftpmaster post about work I’ve done in the recent past.

• The already mentioned move of britney. And it seems that this did help, so something that should have been done way earlier already… Oh well.
• Enabled a few triggers for the qa user on merkel. While I already mentioned them in my first post, there is a third one now. The qa user now gets notified at the beginning of the dinstall run, so the pages can show why packages might not be visible in the archive and in incoming right now.
• Split up the insanely huge mbox files we had as the ftpmaster mail archive. They got that big because the monthly cronjob rotating them got disabled when the ftp-master archive went away from raff, and noone bothered to reenable that job. Done now, so we are back to a manageable size. (Even if 90% of the content is spam, no matter how much greylisting and blacklists are activated :( ).
• Just committed a largish change thats nothing more than a cleanup. Someone in the past did love to not care about tab versus spaces for the indentation, so dak code ended up with a mess of tab/space mix for indentation. Which is not nice, one style is way better. Fixed that with the help of reindent.py, which one can find in Pythons examples.
• Got the code on security.debian.org to use the latest dak revision from ftpmaster. It was a few commits behind, but worse - it did have one dak tool changed in a way that it only worked on security, no longer on ftpmaster. Also some files that clearly have been copied by scp -r or rsync, but not using the VCS that should be used for it. Args. Brrrr. The “fix” was a simple check if that value the code wants to use from the config file actually exists, instead of blindly assuming it will always be there.
• Generally looked around on security.debian.org, to get more familiar with the setup there, so I can work on a request I got from some members of the security teams: Run a queue daemon that manages the upload of the packages from the security archive to the normal archive (so they end up in proposed-updates). Currently it is done with some lftp calls within the script that does the security install, and that seems to break every now and then. Which means security uploads to proposed-updates randomly go MIA. Using a queue daemon and then only locally copy files into its dir should make that way more reliable.
• Used a tool from Dato and enabled bzr commit mails for the ftpmaster dak tree, they are now going to the dak list.
• Modified the cronjobs that are expected to have output to log that into files in a new logdir. Also modified the cron.daily AKA dinstall cronjob to be more verbose about the actions done. The directory is synced to merkel too (log/cron in the ftp.debian.org tree), so every DD who wants to can look at them now.
• I also merged a small patch from Thomas, fixing/unifying some wording in reject messages.

Comments: 3

Just up on arxiv.org this week appeared Warming the early Earth - CO2 considered, by von Paris et al. Just a preprint, and i'm working through its 53 pages now, put its likely to put the cat among the pidgeons:

Abstract: Despite a fainter Sun, the surface of the early Earth was mostly ice-free. Proposed solutions to this so-called "faint young Sun problem" have usually involved higher amounts of greenhouse gases than present in the modern-day atmosphere. However, geological evidence seemed to indicate that the atmospheric CO2 concentrations during the Archaean and Proterozoic were far too low to keep the surface from freezing. With a radiative-convective model including new, updated thermal absorption coefficients, we found that the amount of CO2 necessary to obtain 273 K at the surface is reduced up to an order of magnitude compared to previous studies. For the late Archaean and early Proterozoic period of the Earth, we calculate that CO2 partial pressures of only about 2.9 mb are required to keep its surface from freezing which is compatible with the amount inferred from sediment studies. This conclusion was not significantly changed when we varied model parameters such as relative humidity or surface albedo, obtaining CO2 partial pressures for the late Archaean between 1.5 and 5.5 mb. Thus, the contradiction between sediment data and model results disappears.

The suspected composition of the eary Earth (the Archean, when life is believed to have started, 3.8 to 2.5 billion years ago), has alternated between CO2 and other reducing gases, such as methane. Originally CO2 was thought to be the main greenhouse gas, making life possible. However the high CO2 levels required were a problem; high CO2 levels would have created siderite (FeCO3) in the top layers of soil as iron interacted with CO2 in the oxygen-free air. Since then methane has top billing as the greenhouse gas responsible, with significant hydrogen levels a possibility. Over time, methane has come out on top. And thats what I wrote when I did my literature review for my PhD. Now I'm tidying it up a bit, and that section may be in for a rewrite. But what does it mean for our Climate change models of today? Tags climate, co2, thesis

So I wrote an entry on my tumblelog about what s going on with my life currently. Since Tumblr s feed doesn t get pushed immediately, I showed the post to my co-worker and friend Chris, before it hit the planets: - So, yeah I have my blog since it s syndicated on Planet Debian and other small feed aggregators -I said. - But do they really care about your bike, your chess games or you attending that conference? -he asked-, I mean, I do care, but people? - Well -I replied after a quick thought-, I think that s how personal blogs work. After a deeper thought I just realized that indeed no one cares and deleted the entry before it was pushed to the feed, updating it on FeedBurner, etc. It was a nice awakening.

---

But on a bit more interesting (for people) things, The Perl Foundation is currently requesting comments on the projects they received for grant requests. My proposal is there, Solidifying and Extending the Blog Normalize project . I do think there are some other more deeper projects, of course, but I think B::N is also an interesting one and the amount requested is not as big for other projects, so it d be nice to give it a try. I believe B::N is a good idea that could be enhanced nicely. I proposed the idea to the TextMotion developers yesterday on IRC (since that s one of the CMS there would be a connector for -as of the grant proposal-). After deeper discussion, CMSs will not make translators for a lot of projects into theirs, but B::N would, so maybe we could make some sort of webservice that CMSs could call on their installation phases. That, or the user at the end could actually do the conversion himself locally. Having the proper information, one could be able to get from TextMotion to Wordpress, to Blogger, to Joomla, to Tumblr, to MovableType and to TextMotion again, making a transparent circular transformation. Some of this is currently possible with the few code I ve written for it, currently in CPAN (and a bit deeper proof of concept); if you are interested, please leave your comments on the Perl Foundation blog entry. And review others too. At the end, I might end up doing the project myself, but if some money is granted to do so, why not apply to it, that d just speed it up.

I’m currently in Xen hell. My Thinkpad (which I won’t replace any time soon) has a Pentium-M CPU without PAE support. I think that Debian might re-introduce Xen support for CPUs without PAE in Lenny, but at the moment I have the choice of running without Xen or running an ancient kernel on my laptop. Due to this I’ve removed Xen from my laptop (I’m doing most of my development which needs Xen on servers anyway). Now I’ve just replaced my main home server. It was a Pentium-D 2.8GHz machine with 1.5G of RAM and a couple of 300G SATA disks in a RAID-1. Now it’s a Pentium E2160 1.8Ghz machine with 3G of RAM with the same disks. Incidentally Intel suck badly, they are producing CPUs with names that have no meaning, and most of their chipsets don’t support more than 4G of physical address space [1]. I wanted 4G of RAM but the machine I was offered only supported addressing 4G and 700M of that was used for PCI devices. For computation tasks it’s about the same speed as the old Pentium-D, but it has faster RAM access, more RAM, uses less power, and makes less noise. If I was going to a shop to buy something I probably would have chosen something different to get support for more than 4G of RAM, but as I got the replacement machine for free as a favor I’m not complaining! I expected that I could just install the new server and have things just work. There were some minor issues such as configuring X for the different video hardware (and installing the 915resolution package (which is only needed in Etch) to get the desired 1650×1400 resolution. But for the core server tasks I expected that I could just move the hard drives across and have it work. After the initial install the system crashed whenever I did any serious hard drive access from Dom0, the Dom0 kernel Oopsed and network access was cut off from the DomU’s (I’m not sure whether the DomU’s died but without any way of accessing them it doesn’t really matter much). As a test I installed the version of the Xen hypervisor from Unstable and it worked. But the Xen hypervisor from Unstable required the Xen tools from Unstable which also required the latest libc6, and therefore the entire Dom0 had to be upgraded. Then in an unfortunate accident unrelated to Xen (cryptsetup in Debian/Unstable warns you if you try to use a non-LUKS option on a device which has been used for LUKS and would have saved me) I lost the root filesystem before I finished the upgrade. So I did a fresh install of Debian/Unstable, this time it didn’t crash on heavy disk IO, instead it would lock up randomly when under no load. I’ve now booted a non-Xen kernel and it’s working well. But this situation is not acceptable long-term, a large part of the purpose of the machine is to run virtualisation so that I can test various programs under multiple distributions. I think that I will have to try some other virtualisation technologies. The idea of running KVM on real servers (ones that serve data to the Internet) doesn’t thrill me, Tavis Ormandy’s paper about potential ways of exploiting virtual machine technologies [2] is a compelling argument for para-virtualisation. Fortunately however my old Pentium-3 machines running Xen seem quite reliable (replacing both software and hardware is a lot of pain that I don’t want). In the near future I will rename the Xen category on my blog to Virtualisation. For older machines Xen is still working reasonably well, but for all new machines I expect that I will have to use something else - and I’ll be blogging about the new machines not the old. I expect that an increasing number of people will be moving away from Xen in the near future. It doesn’t seem to have the potential to give systems that are reliable when running on common hardware. Ulrich Drepper doesn’t have a high opinion of Xen [3], the more I learn about it the more I agree with Ulrich.

• [1] http://en.wikipedia.org/wiki/List_of_Intel_chipsets


• [2] http://taviso.decsystem.org/virtsec.pdf


• [3] http://udrepper.livejournal.com/tag/virtualization

Share This

Here is a story people are bugging me to tell here: Since 2003, every year in fisl s last day we, Debian Brasil, hold a party to celebrate Debian s anniversary (I know it s on August, but it s probably the only opportunity we ll have to gather all the gang together so we do it in advance anyway). It s always something that draws everybody s attention in the conference I wonder if the pieces of cake we distribute have anything to do with it Anyway, this anecdote happened during fisl9.0 s party. I was there, helping by distributing cake and blowing our whistles when Jon Maddog Hall got there to check what s going on. I met Jon around 2001, in OpenBeach, an event that happens in Florian polis every year (and that Jon likes to attend)... he s the most pleasant guy, with lots of stories to tell. Since this years fisl was so intense, I barely had time to talk to him in fact, that was the first time we saw each other this year. We hug each other and were asking how s each other life s going and so, when Jon got his camera out of his pocket and asked some guy in the crowd to get our picture. I did the same. We exchanged some compliments and he left saying that he still had to work in his talk. Jon is quite a character. In fisl, every time he wanders around his picture is taken over one hundred times (I actually saw some father taking pictures of him holding his child like he were running for Senate or something, one time). So he left with some people around him and I think he d not seen what happened next. I turn towards Debian s booth, to resume the cake delivery when some guy in the crowd asked me to take a picture with him. And then another one and another. I believe my picture was taken another two or three times before I got to the booth. I can t believe! I was about to tell people Hey! I am nobody! Stop taking pictures with me What were they thinking? I imagine something like I don t know who this guy is, but if Maddog took a picture with him, he must be some one! was crossing their minds. When the party was over I went back to the Organization Committee room and told this story LTSP s Jim McQuillan (another good friend) told me I was Important by Association , and everybody just kept laughing at me because of that. I haven t got the time to tell Jon about it I hope he s reading. I think I am going to check what pictures people are uploading about fisl, to see if I can find myself on any ;-)

As I just had the need to split up two huge mbox files by date and did not find a tool that does that easily, I thought I share what I used. Careful, it isn’t very clever, so if you use it: It comes with NO WARRANTY at all. If it eats your mail, you lost. Not my fault, you have been warned. The task it should solve reads

• split files of size 1.8Gb and 3.2Gb, all together nearly a million mails in them,
• do not use lots of memory for this,
• no need to interactively do anything,
• split based on Date: header.

There are various ways to do it, one would be to use mutt, with something similar to the following in a muttrc file somewhere

 unset confirmcreate
 set delete=yes
 set folder=/dev/null

and then a lot of lines looking similar to the following, just replacing the dates;

folder-hook . 'push "T~d01/03/2008-31/03/2008\n;s2008-03.mbox\n$%q"'

If you then start mutt using mutt -F theabovemuttrc -f themboxfiletosplit it will go and split it into the YEAR-MONTH based files. I got this way from Gerfried Fuchs, as I am no mutt user and wouldn’t have found the way to do it with mutt myself. Drawback: Mutt needs exact date entries in the push lines. Means you have to write 29/02 if you mean “last day of Februar”, a plain stupid 31/02 will be converted to 02/03. And I was way too lazy to list all the dates for the timeframe those mboxes cover. So, other solution. Ruby to the rescue! The following code does split the mbox into the files I want, based on the date header:

#!/usr/bin/ruby -w
# Split a mbox file into $year-$month files
# Copyright (C) 2008 Joerg Jaspert 
# BSD style license, on Debian see /usr/share/common-licenses/BSD
require 'pathname'
require 'rmail'
count = 0
File.open(Pathname.new(ARGV[0]), 'r') do  mbox 
  RMail::Mailbox.parse_mbox(mbox) do  raw 
    count += 1
    print "# count  mails\n"
    begin
      File.open(RMail::Parser.read(raw).header.date.strftime("split/mail-%y%m"), 'a') do  out 
        out.print(raw)
      end
    rescue NoMethodError
      print "Couldn't parse date header, ignoring broken spam mail\n"
    end
  end
end

This will go through the whole mbox and store them in split/mail-$year$ month files. It has a few things you should keep in mind, if you really want to use it:

• Spam mails often have a very broken Date header. Sometimes broken enough that it can’t be parsed. I discard the “can’t be parsed” ones, as I havent seen a valid mail with that. You might want to store it in a different file, so change the part within rescue.
• Again, Spam mails often have a very broken Date header. So you will get files for years way in the past or future. In my case I could simply delete all of them, as all of those had been spam, and I knew in which timeframe the good mails got into the mbox.

The above script took, niced down with nice -15 on an otherwise used server, about 25 minutes to split around one million mails from the above mentioned large files, with no noticable memory usage (only one mail at a time in memory). Comments: 5

Meet the Italian income agency The Italian income agency decided to publish online all the income levels for each and every single citizen and company in the country. I did not manage to see the actual data, because the entire income agency website was swamped with request and timing out all the time. You should have heard the comments of my accountant, who every day needs to access other parts of the website for work. That service is supposed to have been taken offline now, after the Italian privacy watchdog issued a polite What The Fuck! Why Didn't You Tell Us Anything About This? sort of note. The minister defended himself by saying "I can't see what is the problem, it's the same in all the world: if you want proof just watch any American TV series". What a wise man. I should watch some of The Greatest American Hero again. Since I could not see the actual data, I could not verify if what people were saying was actually true, that is that income information were published together with the full home address, providing a nice shopping list for house robbers, kidnappers and the other kind of professionals that would politely wait next to your door for you to come home late in the night. But fear not, the website was protected from bots: it used a captcha. Not only that: in order to comply with standard accessibility rules, the website used a perfectly accessible captcha: You can't get more accessible than that: the captcha is displayed in plain text, so any accessibility technology will be able to read it. Plus, anyone can easily copy and paste it into the text box. And if someone needs to do it often, it's even trivial to write a script that does it for you! But it's unfair to say that it was just plain text: it was cleverly encrypted:

<div class="educaptcha"><label for="educaptcha">I<!-- id9113507 -->nser<span>ire </span><span>nel c</span><span>ampo</span> di <!-- id5058508 -->v<span>erific</span><span>a suc</span><!-- id2643358 -->ces<span>sivo i</span><!-- id2500023 -->l valore <span>695</span><span>8571</span>4<!-- id3588853 -->:</label>
<input id="educaptcha" type="text" name="ucaptcha" value="" maxlength="10" size="20" /></div>

For your convenience, here is the version cracked with a malicious :%s/<[^>]\+>//g in vim. If you do not speak Italian, you can still look for this phrase in the screenshot above:

Inserire nel campo di verifica successivo il valore 69585714:

The meaning is of course:

Insert the value 69585714 in the following verification field:

It's been a fun day for Italians online.

So, the solar panels are now installed, and heating. We're getting the water in the tank heated to around 50 C on these grey days; (there is also an electric immersion coil to heat to 60 degC as necessary, at night-rate electricity). They heat a 300L tank in the utility. The panels are grant-aided by Sustainable Energy Ireland, and we reckon they'll pay for themselves in 5-8 years, depending on water usage with three kids. Time now to see what the actual savings are. Tags energy-saving, solar-panels, house, green, power-consumption

These last two weeks most of my time has been sucked into getting Python 2.5 as default into testing. That’s done now. I made use of the block uploads thingie ftpmaster implemented for the release team to use. Basically, if your package could disrupt an “almost there” transition, the upload will be rejected. The blocks were in place for 5 days, which I think it’s acceptable. As long as we don’t end blocking stuff for very long, I think we should be fine. See the end of this post for more about this. Though it was quite a bit of work, I’m very glad I took care it myself, since now I really feel I’m 100% back to Debian, after the time I spent off for health reasons. Update: Oh, and I forgot to say: having control over britney has really really helped. Thanks a lot Joerg for that.

---

Dudesconf Tomorrow I’m leaving to Coru a for Dudesconf, which is a kind of Debconf-ES. I’m giving an introductory talk to Git, a semi-lighting talk about grep-dctrl (30 min.), and (gasp) a talk about Debian packaging with a VCS. We may have a Debian Quiz as well. I’m so looking forward to it, since many people who’ll attend are amongst my most loved ones, and I already missed last year’s since I wasn’t fully recovered yet. See you there!

---

Minirok and Sevilla One of the reasons I wasn’t fully back to release management during the past 5 months or so is because I spent as much time as I had doing development for Minirok. I don’t think I mentioned here before, but I was participating in a Free Software Contest for college students organized by the University of Sevilla, Spain. Such effort finally paid off, since Minirok was elected as one of the finalists. This means next week I’ll go to Sevilla, to make a presentation of the project, and who knows what more. ;-) I’m very excited.

---

Finally, more on blocking uploads This Python 2.5 transition was the first time the block uploads feature was used, and there were a couple bumps along the way. In particular, a couple packages were blocked, when they shouldn’t have been (libqt4-ruby and evolution-sharp), and one needed package was not blocked, though Rene Engelhard thankfully spotted it very quickly (mono). The problem is it’s not completely straightforward to generate a list of all the stuff that could possibly affect the transition. What I did was to make a run of britney on an arch that had all the needed bits in place, and block all the packages that migrated together as a result of the hint. This fails in two ways:

• it can include stuff that is not needed for the transition, namely unrelated packages that happen to become candidates for testing by one of the their dependencies having migrated as part of the hint. This is what happened with libqt4-ruby and evolution-sharp.
• it can miss stuff that is needed, like packages that can migrate by themselves, so the main run prior to the hint migrates them, and hence do not show up as part of the hint, but that some package of the transition depend on. This is what happened with mono.

The second problem, though, can be fixed by parsing the excuses list and blocking stuff that some bits of the transition depends on. Easy enough. Yet, there are more cases when things can go wrong, for example a shlibs-bumping upload of a package (say, sqlite3) linked against by some package still needing a couple of builds (say, qt4-x11). For that, blocking uploads is not an option, since that’d be an insane amounts of packages that, furthermore, can be uploaded if they don’t bump shlibs, so I guess we’ll have to ask in the next release update that shlibs-bumping uploads are coordinated in -release too, at least when close to finishing a transition.

A few weeks ago, NYU hosted an interesting event about the future of the Internet, appropriately tittled The Futures of the Internet, the video of which is now available here. One of the panelists was Jonathan Zittrain (who recently wrote an important new book bearing the same name as the event) and during the talk he provided a few ideas about how geeks and developers can help secure the Future of the Internet. While I agree with a lot in fact most of his assessments about the state and fate of the Internet as he lays out in his book and his talks, his characterization of geek/hacker/developer politics is not one of them. Basically, one of Zittrain’s claims is that developers are not doing enough to save the Future of the Internet and it is their rampant, Atlas-like libertarianism, which is, in part, to blame (first made 37:20 minutes into the video for those who want to listen to the actual comments). They have little-to-no political consciousness, are too cool to care about the fine print and they don’t care about the broader politics of the the Internet because they assume that they can just hack around any sort of barrier and impediment. While we can, without a doubt, identify a strain of libertarianism among hackers, it is by no means representative of all of geekdom and in fact, is becoming more and more a worn out 1990s stereotype/clich as time passes than an accurate representation of what is a far more variegated set of ethics and practices among hackers (and I will soon publish an article on this topic). It also completely fails to capture the ethical spirit as well as sociological, and political workings of one of the most important strains of hacking free and open source software which not only powers most of our (open) Internet but which in fact has provided a pretty hefty ethical backbone by which to conceptualize one of the ways we should think about the fight for the future of the Internet. Ok, time for a rant now Geeks not only designed the Internet, an indisputably revolutionary medium, but also implemented, and continue to maintain it, and then in their copious spare time, also engage in fighting back the political, legal and corporate encroachment which threatens to limit the very revolutionary nature of the Internet (as Chris Kelty’s new book on Free Software argues). If these acts by geeks are not enough political action, then maybe the development of not just one, but multiple entirely open and free alternatives to the only two proprietary operating systems that exist today might be a political act that would satisfy? Many would agree that even simply using a free operating system is a political act. It would be better to claim that individuals, lawyers and other political actors are not doing enough to save the Future of the Internet, rather than imploring the already overtaxed geeks to set aside everything that they are already doing to do something even more. (end rant) It also seems that when it comes to political questions related to the Internet, net neutrality being the hot topic now, or fighting restrictive and problematic laws like the DMCA, one of the only groups of people (outside of lawyers and librarians) to actually understand and dissect the fine print (and geeks actually are pretty attuned to and like to dissect the fine legal print), to protest these unsavory laws, and to support the organizations who are doing something about it (like the EFF), are geeks and hackers. While many geeks are not necessarily keen on conceptualizing their labor in traditional political terms, or aligning their technical projects with a political affiliation, and yes would rather just be writing good code, they do fight for their productive freedom and this productive freedom just happens to relate to most questions and concerns related to an open, accessible, and tweakable Internet, built by the geeks, lest we forget What was perhaps most surprising was that he also seemed to think that geeks and developers have not turned to “apprenticeship,” nor policies and procedure to coordinate their development projects, unlike Wikipedia, which he considers a shining example that geeks should look towards as a beacon of policy that geeks should consider emulating in their projects (comments made answering my question). He clearly has not been hanging out with any Debian developers in the last 10 years nor has he gone through their New Maintainer Process In other words, he seems to think they are allergic to regulation due to their accentuated libertarianism, or are against structure because of their anarchism, neither which is remotely true. I think I found this characterization most ironic and problematic for before Wikipedia was even an entry on a Wiki, projects like Debian (and most other F/OSS projects) were transforming and changing to integrate normative procedures and policies that allowed a group of people to work together, scale, grow and deal with crises’. No, they don’t have the Wikipedia badge system, but that system is emblematic of Wikipedia’s own transformation into integrating its own normative procedures and policies for working together, not an example of an idealized policy system that other projects are too primitive to have evolved into yet. About one hour into the talk when questions opened up, I objected to his characterization, but given his answer back to me, I did not make much of a dent in his thinking. Another lawyer Tim Wu (who also wrote a wonderful book on the Internet) chimed in to give me some props and also made a good point that even if geeks are the only groups of people who would storm AT&T and know intimately about the importance of net neutrality, there is a lot of room for thinking about how to strengthen and improve the tactics and politics among geeks and developers so that we can ensure the type of open and generative Internet and set of technologies we value. As part of thinking and rethinking new strategies, it is as key to acknowledge and honor the past. In this regard, free software development has been pivotal both in terms of providing software (and making it is an important political act as is choosing to use free software over propriety software) and a set of important set of ideas that a lot of lawyers like Yochai Benkler and Lawrence Lessig have run with to make some important political claims of their own. So despite my rant above, which was a rant and thus exaggerates things to some degree, I do think there is much more that geeks and non-geeks can do, such as help translate these uber-geeky issues into less geeky terms (and actually this is already being done by some geeks as the work of Jelena Karanovic has shown, or translate the technical issues into new domains as the uber-geek Karl Fogel is doing with question copyright but first lets give credit where credit it due and recognize that labor is political

I gave Brenda a Palm TX, so she can better organize her life. As a plus, it is wi-fi aware, so all sorts of interesting things can be done. Sadly, though, it doesn t ship with a microphone (I still wonder why it s large enough to hold an embedded mic, just as Palm smartphones have). Lately, Brenda was talking about recording some sessions or holding her thoughts in one of those tiny memo-recorders, and this promptly stroke me as another gadget to stuff her purse ... then I remembered having read that Palm TX have all that is required to hold a microphone, but the microphone I retrieved the Palm Multi-Connector pinout from Wikipedia and realized that all I had to do was attach an electret microphone to 16 and 17 pins and there we go. I ordered a charging cable just for the connector and here are the pictures I took of the building process: The tools and pieces I used: It s easy to disassemble the connector. Take a close look at the attaching plastic hooks there are four of them: two outside, near the pins, and two inside near the cable. Last two are harder to detach, but once you ve detached the first ones, just hold the two pieces of the connector and easily shear them: one side will detach first. The microphone have two terminals that already hold enough soldering tin. Beware to solder the blue cable (the one that goes with pin 16 AGND) to the marked terminal of the microphone, and the red one (the one that goes with pin 17 MIC_IN) to the unmarked one. (In the picture, my cables are all black, but the wires inside are red or blue . I could not get a good picture of the terminal markings). I have dissolded the charging cables from pins 1, 3, 5, and 8, but that is up to you (you can just cut the main cable and leave the pins untouched). Also, while soldering the microphone cables to the connector, beware of using as little tin as possible. It ll be even easier if you remove the pin from the connector it s easy to do if you have small pliers and careful fingers. Try first with one of the other pins that will not be used. Solder the red one to pin 17 and the blue one to pin 16. I cut a piece of an old earphone cushion to close the charging cable hole (and to protect the microphone). Here is the final result: Now, for the recording software, there s a nice free software that does that perfectly for PalmOS: Better Recorder. Now Brenda can record her mind!

Ira Pramanick talks in her weblog about a mentorship program targeted towards middle and high school girls to foster in them a positive attitude towards computing. The program is called MAGIC, which stands for More Active Girls In Computing, and tries to address the issue of the low number of girls entering the computing and high tech world. As they say, it is a serious issue caused not by then lack of talent, but due to a bunch of discouraging factors that exist in our culture and society. Right now, women represent only about 28% of the technology workforce. I don’t know if a mentorship program dedicated to these girls would be enough to increase the number of women participating in the technology workforce, but it will probably help to improve the situation. It would be nice to import the project model into Spanish speaking countries if it’s successful. The Mentor Qualification Process is quite strange anyway. It might be that we europeans have cultural differences, but I find some of the questions there quite disturbing, like “Are you willing to be finger-printed and screened?”. I don’t exactly know what they might want such a sensitive data for.