Just some quick superficial observations on the Debian/Ubuntu package distributed by Google:

• Most files are installed in /opt/google/.
• It attempts to patch /usr/share/gnome-control-center/gnome-default-applications.xml on postinst (maybe legacy compatibility? Someone with more gnome-fu than me care to explain?).
• The postinst also automatically adds a souce for updates to /etc/apt/sources.list.d and an archive key (this is IMHO the worst part)
• It includes a daily cronjob that at least at first glance tries to do the same things the postinst did (new apt source, archive key, etc) and some further archive configuration. The cron script is called at the end of postinst.
• A casual look at objdump suggests it s statically linked to libv8
• On a slightly more positive note, it at least seems to successfully undo most of the changes once removed, with the exception of the added archive key and the above mentioned patch to gnome s default apps list (that is: if there s any situation it actually gets applied).

I understand it might be too much hassle doing it the right way (from the corporate POV), but then why not simply cooperate a bit more with the community? Hopefully they ll accept some criticism and suggestions.
Or even better: they could simply reuse all the work being done to officially package Chromium.

The first thing I searched for in Google, back in 1999, was probably "linux", followed by my name. The last thing I searched for in Google, on a snowy day in 2009, was "vdash". With the decade over, and Google rolling out all manner of tracking cookies and javascript, it's time to move on. Just keeping on top of the torrent of privacy-affecting changes Google is making, and trying to parse the real meaning in the chirpy googlespeak announcements has become more work than the value their search engine adds. (This was the last straw.) At least for now, I'll be using Duck Duck Go for search. It's small, quirky, has features the big competition lacks, and works well enough for my mostly moderate and occasionally intense needs. Sorta like Google in 1999.

As an aside to yesterday s Another Network Begins note, I should mention that one of the challenges of running any inter-business project is paying for it. It surprises some people that many great cooperative projects are running on very small budgets, whereas it looks like some Social Enterprise groups are awash with cash. How can this be, when it still looks like cooperatives are stronger financially than social enterprises? A written answer in Parliament on Monday suggests one possible reason: Co-operatives UK and The Plunkett Foundation together get 164k of Cabinet Office funding, while the Social Enterprise Coalition alone gets 488k and there are other SocEnt groups on the pay list. Once again, I m surprised by the way the Labour and Co-operative government is behaving, like I was on the way the real help initiatives exclude cooperative partnerships, while being open to both private sector employers and social enterprises. I m all in favour of intervening in markets, but this doesn t feel like it s making things fairer. Three strikes, funding social enterprise in preference to cooperatives would a Conservative or Liberal Democrat government really be worse?

Lil is white trash. She does not live in a double-wide and make hot dog casserole, and in foreign lands she could easily pass, but she is white trash nonetheless. Lyle is white trash. He does not buy potted meat or have a car up on blocks in his yard, but he is white trash nonetheless. One day Lil and Lyle met, and something drew them together. Perhaps it was a disturbance in the philotic web, or maybe a magical Jungian archetype of a dirty rag as a gas cap that resonated in their minds, but whatever it was, they decided to keep in touch online and get to know each other better, with clear non-platonic overtones. Lyle had a penchant for underdressed girls with a modest amount of tattooes and piercings and a full-on bent for drunken promiscuity. While Lil did not fit this stereotype well, she played up her sexual indiscriminateness and made up a few fetishes to impress him. Lil needed a boy who would not judge her for all her faults and long history of poor decision-making. So Lyle pretended not to judge. One-third deceit, one-third misinterpretation of Internet ambiguities, and one-third imagination led them to develop unrealistic perceptions of each other. Since they also had unrealistic perceptions of themselves, were fairly narcissistic, and were almost totally caught up in their own private melodramas, it took a while for the veil to come down. Come down it did, like an avalanche of Kraft Dinner boxes falling off a Canadian supermarket shelf. Then they were angry. Then they were sad. Then they brushed on fresh new coats of self-delusion and heated up some chicken nuggets.

Once you release something what gets at least a little bit popular, you can expect to receive fixes in various strange forms. Since I started to use Git for Gammu development merging all these crazy things is much more easier. The problem with these changes in past was that they are generally based on some random old versions (for example random daily snapshot). Now I just find the right place in history where to start (ChangeLog usually gives good hint where to search in the history), create branch and start to apply changes I received. I worst case (like it happened today) the "changes" is whole tarball with different changes made to different files. Fortunately I recently found great git add -i, which allows me to pick whatever changes I want from the patch. When all this is done, all I need is to merge changes back to master and Git is usually clever enough to handle it. PS: And yes, I'd really love if people would be able to send me series of patches, but it does not seem to happen in near future.

Linux 2.6.32 was released overnight. This has been a fairly busy release for ASoC, with changes including:

• Redone power sequencing code, giving shorter power sequences which
  should reduce the effect of any artifacts that exist.
• Reporting of power management decisions via debugfs, enabling much
  easier diagnosis of path setup problems.
• Beginning of work to factor out the register access and caching code
  from the individual CODEC drivers into a shared file. This needs to
  be rolled out over more CODEC drivers.
• New CODEC drivers for AD1836, AK4642, MAX9877, WM8523, WM8776, WM8961, WM8974 and WM8993
• New CPU support for multi-channel Blackfin SPORT, DaVinci McASP, i.MX2x SSI, and OMAP 1510 McBSP.

Finally, after more than a year of preparation, and six months of very very hard work, DebConf8 has come and gone. Even if I'm not yet completely recovered from all that stress, I'm good enough to feel really happy about how things turned out. DebConf8 was a great success. We had great talks, many opportunities for developing interesting ideas, a lot of social interaction, an awesome video team that allowed more than 200 people from all around the world to be part of the conference even if they weren't in Argentina, and in general almost everyone had a very good time. It was really nice to have so many people from Debian over here, and it was specially nice to see them working and enjoying themselves so much. This was all possible thanks to our sponsors, thanks to the many hours spent during the previous months both by the DebConf orga-team (the usual suspects) and specially by the local team, which includes Tincho, Dami n, Romanella, Maxy, Sebas, Zero, Mendieta, Dererk, Melisa, Angasule, Lisandro, Nueces, and also thanks to the all help of the volunteers that came to work with us during DebCamp and DebConf, which include Tom s, Tinchito, M nica, Lucas, Germ n, Diego, Fefu, Nicol s, Mart n, Marcos, Hern n, Alejandro, Mat as, Rodrigo, Alberto and Joaqu n, and finally, DebConf wouldn't have been the great event it was without all the people that managed to travel thousands of kilometers to get here. To all of them, thanks, for making DebConf8 such a great conference Now, at last, DebConf8 is over (although there is some stuff that we still need to do before we can really forget all about it), and life goes on. Today, I did my first NMU after a long time. I'm particularly glad to have time for fixing bugs again, but I won't lie, I'm also extremely satisfied with how DebConf8 turned out. See you in Extremadura!

Caution: Latin American rant ahead. With my Latin American Spanish keyboard (xkb code "la") I can type in:

• English: abcdefghijklmnopqrstuvwxyz
• Spanish, Galician, Basque, Quechua:
• Catalan/Valencian and Occitan: l l
• French:
• Italian:
• Dutch:
• German:
• Swedish:
• Danish and Norwegian:
• Icelandic:
• Finnish: (apparently, the untypable are only used in loan words)

But not in:

• Portuguese: I can't type or (no dead_tilde)
• Guaran : I can't type g (no dead_tilde).

It turns out that for some people it's more important to have 3 (yes THREE) asciitilde (~) in the Latin American Spanish keyboard, than to allow people to write in the language spoken by 51% of South American people, or the second official language in Paraguay (spoken by 94% of the population). The same thing happens with the Traditional Spanish keyboard (code "es"), which was initially thought only for Spain, but is now widely sold all over Latin America. It includes 2 asciitilde, but no dead_tilde. I think this is outrageous and I'm very very pissed about this. As can be seen in the posts I've made to the bugs in Debian and in FreeDesktop. However, it looks like we Latin Americans are overwhelmed by the amount of Spanish people in Free Software (particularly in Debian) who don't care that Brazil is the biggest economy in the region nor that other native american languages can't be written without a dead_tilde. For the record, there are some other European languages, that can't be written with the Latin American keyboard, such as:

• Polish: I can't type , only
• Czech: I can't type , only
• Romanian: I can't type , only

But in this case, it makes much more sense to not be able to write those than not being able to write Portuguese or Guaran , and it's not like there are 3 macrons and no dead_macrons, there are no macrons at all (same for all others).

Last year, after many years of peacefully living the whole year in GMT-3, our government decided that Argentina should use DST again. This was done in a rush, but patches were written and applied everywhere to have a correct timezone. Fixing the problem was not enough, tzdata's upstream decided to predict the future:

# From Paul Eggert (2007-12-22):
# For dates after mid-2008, the following rules are my guesses and
# are quite possibly wrong, but are more likely than no DST at all.
Rule    Arg 2007    only    -   Dec 30  0:00    1:00    S
Rule    Arg 2008    max -   Mar Sun>=15 0:00    0   -
Rule    Arg 2008    max -   Oct Sun>=1  0:00    1:00    S

Well, back in December 2007, October 2008 might have seemed like a long time in the future, and they assumed that sometime in the middle the correct date would be announced... But, predictably (knowing Argentina's current government), no DST has yet been announced. However, Paul Eggert's guesses had propagated to almost all UNIX distributions, so that at 0:00 Sunday Oct 5th, all our computers were suddenly one hour ahead of time. Affected systems: Debian, Ubuntu, Gentoo, Red Hat, OpenBSD, FreeBSD, Mac OS. Devices: ipod, maemo, Nokia N95. Websites: Clarin (a major newspaper - still broken 36 hours later), Gmail. And probably many others that I don't know of. I even read that Windows was affected, although I don't know how that might be possible, since as far as I know they don't use tzdata. Anyway, not satisfied with how they mistakenly predicted the future before, a few weeks ago (not enough time in advance to fix almost any systems, only sid had this release), they added this change:

# From Alexander Krivenyshev (2008-09-05):
# As per message from Carlos Alberto Fonseca Arauz (Nicaragua),
# Argentina will start DST on Sunday October 19, 2008.
#
# http://www.worldtimezone.com/dst_news/dst_news_argentina03.html
# http://www.impulsobaires.com.ar/nota.php?id=57832 (in spanish)
Rule    Arg 2007    only    -   Dec 30  0:00    1:00    S
Rule    Arg 2008    max -   Mar Sun>=15 0:00    0   -
Rule    Arg 2008    max -   Oct Sun>=15 0:00    1:00    S

So, they decided to take the word of a guy from Nicaragua (no bad feelings against Nicaragua, but I think that this kind of stuff should be informed by people from the affected country), and from a couple of articles that say that "According to some sources, we might have to change our clocks on the third Sunday of October". Would you change tzdata sources with such information? I definitely wouldn't. Anyway, Aurelien Jarno has already uploaded fixed packages, with no assumption regarding when the DST will happen, which is the sensible thing to do in a case like this. Thanks Aurel!

Reality needs fantasy to render it desirable, just as fantasy needs reality to make it believable. Stephen Duncombe

This fall I have been awash in a few obsessions including book piracy and spam. I recently got to talk about one of these obsessions when I was interviewed about book piracy by Nora Young for her weekly CBC radio and podcast show Spark. I mostly gave a lay of the land panorama with a nod toward some of the conditions, technological and social, that can help us grasp the contemporary explosion of book piracy and also raised some thoughts about what might change the future landscape. What I don t raise is whether a politics built around an explicit embrace of piracy is regressive, progressive, or something else but these ethical questions were posed in the comments left for the full interview. Some of the comments pointed to the pitfalls and shortcoming that can follow the terminology of piracy many of which I share. But what keeps me interested in the politics of piracy is how it can speak the language of spectacle, which can be a powerful tactic and technique for broadcasting a political message. Here I just paraphrasing and cribbing the work of Stephen Duncombe, who has argued, I think quite persuasively, that we cannot rely solely on reasoned debate for building political programs. Duncombe does not argue that we must toss out rationality and truth seeking (these are absolutely necessary) but notes how on their own or if not clothed in some other cloak, they may not be enough to convey and compel, especially in this day of total media saturation. Or to put a but more poetically by him Reality needs fantasy to render it desirable, just as fantasy needs reality to make it believable. Much (though not all) of contemporary digital piracy follows the logic of spectacle. It builds and conveys a fantastical drama of right and wrong, of new possibilities, of freedom from the noose of the law; it signals and speaks to the thrill and fun in twisting, even breaking, existing structures and constraints; and provides a window into another way of acting/behaving. In many cases what it provides is a commons (and I will be exploring it in depth in my class next semester on the commons) and many folks, I imagine, turn to piracy simply for the free stuff, and a number of them come out of the other side transformed into copy fighters willing to engage in a politics beyond sharing stuff and waving the pirate flag. For those of us who believe in greater access and different ways of imagining structures and strategies of re-compensation, piracy on its own is not certainly enough and I understand fully and even to some degree, share the skepticism many feel toward such language. But I am not quite ready to declare a politics of piracy as always politically bankrupt or necessarily backward. I guess what I embrace is a diverse political ecology. For some, the drama of spectacle and thrill of transgression are what turns their political mojo on; for others it is the cool and reasoned debate common to policy and reform; for others, they want to focus on building alternatives as we see with Free Software or radical tech collectives. For some, it is both the reasoned salt and the transgressive pepper that spices their political world. And I would rather have more spice than less, especially in an era where the blandness of political apathy is that which is our most dangerous enemy. Related Links: Here is a wonderful animation by the NZ Book Council that captures what I love about books and renders its materiality wonderfully alive. On the Media has a episode on book publishing and Cory Doctorow has penned some thoughts about the future of book selling. If you want to keep abreast on the politics of liberating books, check out Free our Books. If you are more interested in the technical side of things, check out the book liberator project.

Reality needs fantasy to render it desirable, just as fantasy needs reality to make it believable. Stephen Duncombe

This fall I have been awash in a few obsessions including book piracy and spam. I recently got to talk about one of these obsessions when I was interviewed about book piracy by Nora Young for her weekly CBC radio and podcast show Spark. I mostly gave a lay of the land panorama with a nod toward some of the conditions, technological and social, that can help us grasp the contemporary explosion of book piracy and also raised some thoughts about what might change the future landscape. What I don t raise is whether a politics built around an explicit embrace of piracy is regressive, progressive, or something else but these ethical questions were posed in the comments left for the full interview. Some of the comments pointed to the pitfalls and shortcoming that can follow the terminology of piracy many of which I share. But what keeps me interested in the politics of piracy is how it can speak the language of spectacle, which can be a powerful tactic and technique for broadcasting a political message. Here I just paraphrasing and cribbing the work of Stephen Duncombe, who has argued, I think quite persuasively, that we cannot rely solely on reasoned debate for building political programs. Duncombe does not argue that we must toss out rationality and truth seeking (these are absolutely necessary) but notes how on their own or if not clothed in some other cloak, they may not be enough to convey and compel, especially in this day of total media saturation. Or to put a but more poetically by him Reality needs fantasy to render it desirable, just as fantasy needs reality to make it believable. Much (though not all) of contemporary digital piracy follows the logic of spectacle. It builds and conveys a fantastical drama of right and wrong, of new possibilities, of freedom from the noose of the law; it signals and speaks to the thrill and fun in twisting, even breaking, existing structures and constraints; and provides a window into another way of acting/behaving. In many cases what it provides is a commons (and I will be exploring it in depth in my class next semester on the commons) and many folks, I imagine, turn to piracy simply for the free stuff, and a number of them come out of the other side transformed into copy fighters willing to engage in a politics beyond sharing stuff and waving the pirate flag. For those of us who believe in greater access and different ways of imagining structures and strategies of re-compensation, piracy on its own is not certainly enough and I understand fully and even to some degree, share the skepticism many feel toward such language. But I am not quite ready to declare a politics of piracy as always politically bankrupt or necessarily backward. I guess what I embrace is a diverse political ecology. For some, the drama of spectacle and thrill of transgression are what turns their political mojo on; for others it is the cool and reasoned debate common to policy and reform; for others, they want to focus on building alternatives as we see with Free Software or radical tech collectives. For some, it is both the reasoned salt and the transgressive pepper that spices their political world. And I would rather have more spice than less, especially in an era where the blandness of political apathy is that which is our most dangerous enemy. Related Links: Here is a wonderful animation by the NZ Book Council that captures what I love about books and renders its materiality wonderfully alive. On the Media has a episode on book publishing and Cory Doctorow has penned some thoughts about the future of book selling. If you want to keep abreast on the politics of liberating books, check out Free our Books. If you are more interested in the technical side of things, check out the book liberator project.

Biggest, in terms of money involved, piece of equipment is a nice piece of glass to put in front of our camera. Since my wife had been using a Canon SLR since forever (and we stayed with that when moving from the EOS 300 to the current EOS 40D), the choices to upgrade from the kit EF-S 17-85mm f/4-5.6 basically have been:

• EF-S 15-85mm f/3.5-5.6 IS USM: since it's been announced with the 18Mp 7D it should be quite good on the 10Mp 40D. Newest design, certainly one of the best IS on Canon, true wide angle.
• EF 24-70mm f/2.8 L USM: The old trusted one. No IS, but a constant f/2.8. Narrowest zoom range of the lot. A real tank, at almost 1kg.
• EF 24-105mm f/4 L IS USM: The other full frame L lens. Not quite as big, longer, but only f/4.
• EF 24-70mm f/2.8 L IS USM: including waiting for it to be announced and available, of course.

In the end I got the EF 24-70mm f/2.8 L USM, because the EOS 40D is no high ISO monster (we don't plan to upgrade immediately.) Also: I bought the Tokina AT-X 116 PRO DX (11-16mm, f/2.8) a while back and we're quite happy with that so wide-angle is covered. And since we're often shooting indoors (family and other events), f/2.8 is a big plus. On the tele end, there's quite a gap from the 24-70 to the old EF 100-300mm f/4.5-5.6 USM [age of the page to reflect the age of the lens ;-) ] but then the latter is probably the next lens to be replaced anyway. Since I only got 24-70 I can not directly compare these lenses. But after a few early tests I think I'm happy with the 24-70: while it seems to be a bit soft wide open at 24mm and at 70mm, it seems to be very sharp center to edge even at f/2.8 when used in the 35-50mm range. (Note that the 40D is a crop sensor camera, so I'm nicely using the sharp center area of a lens designed for full frame!) Yes, it's huge, so for casual walking around the 17-85mm will probably still get some use. Time will tell. And since it can, potentially at least, be used on a a EOS 5D Mk II, I now have another gadget to covet. Although this would mean giving up the Tokina 11-16mm. Anyway, not for quite some time yet... (The test also included the venerable EF 50mm f/1.8, Mk I, and I must say I'm quite surprised how sharp that one is in the f/4 to f/11 range.)

resurrecting CamlJava (testers welcome) CamlJava is a great project by almighty Xavier that bridges the OCaml and Java worlds via the respective C interfaces (Caml/C interface for OCaml and JNI for Java). Unfortunately, the last stable release was a bit out of date and seemed not to work with recent JDK (both in terms of buildability and of runtime correctness, i.e., segfaults). With the tremendous help of Gr goire Henry, I've managed to prepare a set of patches that enables to build (and use without segfaults ...) CamlJava with recent JVM: in particular it seems now to work with both Sun's JVM and OpenJDK. A Debian package has been prepared; while it gets processed by archive manager, you can get an equivalent unofficial package from my APT repo:

    deb http://people.debian.org/~zack/debian zack-unstable/
    deb-src http://people.debian.org/~zack/debian zack-unstable/

Any form of testing is very welcome. In case you want to try O'Jacare on top of CamlJava however, you need to wait a bit more: Gr goire is working on it, but in the process he banged his head against bugs in both CamlP4 and CamlP5 (the only two available porting paths from the last stable release of O'Jacare)

Email scams have changed... for good and for bad (depends on the POV and the case).

I decided to pick two samples that demonstrate two directions scams seems to be taking:

NAME
ADDRESS
TELEPHONE
SEX

As simple as that. Now the subject takes a more important role than the content: "Your email ID has been awarded one million pounds. in our Tobacco Promo". This, I must say, seems to be one of the worst scam emails I've ever seen. Compare it to the following:

Dear Raphael,

This email might come to you as a surprise and the temptation to ignore
it as not serious could come into your mind but please consider it and
accept it with a deep sense of humility.
[...]
The sum of ( 10,700, 000.00 Million Pounds), has been floating as
unclaimed since 2002 in my bank as all efforts to get across the
relatives of our customer Mr. Ruben Geissert who deposited the money
have hit the stones. Unfortunately, He died of Cardiac Arrest in the
year 2002, without a registered nest of kin.

I've highlighted the important bits of the email; the difference is clear.

I was already wondering some time ago when this kind of "improvements" to the scam (and spam in general) emails would be seen.

What's next?


P.S. if you haven't voted at the Earth Hour website please consider doing so.
If you are having problems voting because of the flash application, here's a direct link.

I ve been investigating the Ext4 filesystem [1]. The main factor that is driving me to Ext4 at the moment is fsck times. I have some systems running Ext3 on large filesystems which I need to extend. In most cases Ext3 filesystems have large numbers of Inodes free because the relationship between the number of Inodes and the filesystem size is set when it is created, enlarging the filesystem increases the number of Inodes and apart from backup/format/restore there is no way of changing this. Some of the filesystems I manage can t be converted because the backup/restore time would involve an unreasonable amount of downtime. Page 11 of the OLS paper by Avantika Mathur et al [2] has a graph of the relationship between the number of Inodes and fsck time. Ext4 also has a number of other features to improve performance, including changes to journaling and block allocation. Now my most important systems are all virtualised. I am using Debian/Lenny and RHEL5 for the Dom0s. Red Hat might back-port Ext4 to the RHEL5 kernel, but there will probably never be a supported kernel for Debian/Lenny with Ext4 and Xen Dom0 support (there may never be a kernel for any Debian release with such support). So this means that in a few months time I will be running some DomUs which have filesystems that can t be mounted in the Dom0. This isn t a problem when everything works well. But when things go wrong it s really convenient to be able to amount a filesystem in the Dom0 to fix things, this option will disappear for some of my systems, so if virtual machine A has a problem then I will have to mount it s filesystems with virtual machine B to fix it. Of course this is a strong incentive to use multiple block devices for the virtual machine so that a small root filesystem can be run with Ext3 and the rest can be Ext4. At the moment only Debian/Unstable and Fedora have support for Ext4 so this isn t a real issue. But Debian/Squeeze will release with Ext4 support and I expect that RHEL6 will also have it. When those releases happen I will be upgrading my virtual machines and will have these support issues. It s a pity that Red Hat never supported XFS, I could have solved some of these problems years ago if XFS was available. Now for non-virtual machines one factor to consider is that the legacy version of GRUB doesn t support Ext4, I discovered this after I used tune2fs to convert all filesystems on my EeePC to Ext4. I think I could have undone that tune2fs option but instead decided to upgrade to the new version of GRUB and copy the kernel and initramfs to a USB device in case it didn t boot. It turns out that the new version of GRUB seems to work well for booting from Ext4. One thing that is not explicitly mentioned in the howto is that the fsck pass needed to convert to Ext4 will not be done automatically by most distributions. So when I converted my EeePC I had to use sulogin to manually fsck the filesystems. This isn t a problem with a laptop, but could be a problem with a co-located server system. For the long term BTRFS may be a better option, I plan to test it on /home on my EeePC. But I will give Ext4 some more testing first. In any case the Ext3 filesystems on big servers are not going to go away in a hurry.

• [1] http://ext4.wiki.kernel.org/index.php/Ext4_Howto
• [2] http://ols.108.redhat.com/2007/Reprints/mathur-Reprint.pdf

Now that I'm not letting the cat out of the bag (I bought these as gifts) I can write a review. The use case was pretty simple: I thought it'd be a cool Christmas present for our parents to give them something Internet-enabled that would give them regular updates on their grandchild (when he/she arrives). I was thinking a picture a day type of thing. So I hunted around for a WiFi-enabled digital picture frame, and found the iGala being sold pretty much exclusively by ThinkGeek. The reviews seemed pretty good. I know WiFi-capable frames have been around for a few years, but they always seemed to be pretty lacking in terms of WiFi functionality. Like they wouldn't do any security, or they'd only do WEP. This particular product claimed to do the whole gamut, including WPA2. The fact that it was a touch screen and ran Linux also made it appealing. So I ordered a couple of them for a few weeks before we headed to Australia, with the intention of making sure that they'd work. Here's the highlights. WPA2 didn't work (nor did WPA) Despite the software on the frames claiming to be able to talk WPA2, the frame would not associate with my Linksys WRTU54G-TM. I had to drop it all the way back to WEP to get it to connect. For me, this was the most disappointing failure. I bought the product specifically on the strength of its claim that it supported WPA2, and it just didn't work. It was also pretty impossible to debug the failure. I downloaded the latest firmware update, and that added additional settings for TKIP or AES when selecting WPA2, but neither option helped. The automatic updates are brain-dead Speaking of downloading firmware updates, the latest firmware that I downloaded and installed on the frames added automatic over-the-air firmware updates. Nice enough feature, except for the implementation. The frame tried to make an HTTP GET request for a non-existent file, every 6 seconds. So the frequency of checking alone is totally ridiculous, but couple with this the fact that it's making a GET request (this is what $DEITY invented the HEAD request for, people!) and the website has a "friendly" 404 Not Found page that weighs in at a little over 10 Kb. By my calculations, that's nearly 150 Mb of failed update checking traffic a day. Taking these frames to a backward country like Australia, where ISP users still have monthly quotas, gives the frame a pretty horrendous running cost in terms of traffic. Not to mention the outbound bandwidth requirements for the server hosting the updates. Crikey, the mind boggles. I'd have thought checking once a day and on power on would be perfectly sufficient. Transitions are unavoidable It may be just me, but I hate cheezy transitions. Digital picture frames tend to come with a myriad of them, but they all look cheap. It's impossible to tell the frame to just change the picture, it has to use at least one transition effect all the time. It defaults to randomly choosing from all the available ones. At least you can tone it down to just one. Automatic on/off time I liked that it was possible to configure operating times. No need to have the thing chewing power 24x7. It just seems to turn off the backlight outside of the programmed operating hours, so it's still doing the lame uber-frequent and bandwidth-intensive checking for updates even when it's "off". Photo check frequency is configurable Another nice feature was the ability to check for new photos at varying intervals. What I wanted for my parents was to just update once a day, so they'd get a new photo every day (assuming we put a new one in the Picasa web album that it's checking). This was very doable, and coupled with the automatic on/off time, means they should wake up to a new photo every day (that we change it). Built in photos are a bit too sticky There's 3 or 4 in-built photos as part of the firmware. If there's nothing accessible or available online, it'll cycle through these. Somewhat annoyingly, you need to have at least two photos in your online source for it to stop wanting to incorporate the stock photos in the mix. The workaround is to put the same photo in the online album twice, so you don't realise it's switching between two images. Lame, but it works... Touch screen UI was adequate Given the alternative user interface for digital picture frames is a little IR remote control and some dinky menus, the iGala was nice to configure. A full on-screen QWERTY keyboard pops up for entering WEP/WPA/WPA2 keys and configuring the Picasa/Flickr connections. Fairly responsive support The main near-showstopper for me was the lack of advertised WPA2 support. I emailed the Aequitech support folks quite a bit during my "evaluation" period. They got back to me fairly quickly most of the time and wanted to know exact details of my setup so they could reproduce it in the lab. They'd be well served having an actual ticketing system, instead of hiding behind an email address, as it made it hard to keep track of the multiple issues I was raising with them. It's written in Lua?! I have no familiarity with Lua, other than I know of its existence as a programming language. I'm curious as to what their motivation was for this language choice. All of the Lua code shipped in the complete firmware refresh ZIP files is bytecode. I have no idea if it's possible to decompile it. The CPU architecture would appear to be a Blackfin based on the few compiled binaries included in the full firmware. Easy to update Prior to the new update "functionality" I've already railed against, it was pretty easy to update. Download a ZIP file and a shell script, put them in the root directory of a USB key, and plug it into the frame and stand back. The updates don't seem to cryptographically verified (even the over-the-air ones), so I wonder if it's possible to break into the frame by way of a cleverly crafted "update". I have no idea what breaking into the frame would buy you. I don't know what sort of computing power they have. Conclusion I still think the iGala is a reasonable, if somewhat immature product. If the software is going to be actively worked on, and the support people continue to be responsive, then I think it's got good potential. For the price, I expected a more polished product, though. I received an email from their support people shortly after returning from Australia saying that they'd fixed the WPA2 problem. Unfortunately I had no intention of trying to remotely talk my parents through how to reconfigure their access point or the frame (interestingly WPA2 didn't work with their Linksys WAG54G2 either, so I'd love to know what WPA2 devices it was tested with), so it's 128-bit WEP until I next go to Australia.

This weekend while I was on Guatemala just a few hours before to give a talk, my acer one decided to suddenly shut down, I tried to started again, remove the battery, plug the charger, etc, I actually even tried to boot it with some liv-usb distro, but the netbook keep shutting down a few seconds after boot I m still not sure what happend to the computer, it could be the motherboard or the HDD, I still have to check if it can be fixed Sadly, this was my main computer, I always used for almost everything, even for task when building a package tooked 50 minutes :p, but I m lucky since I did not loose any senssitive data (in case the problem is the HDD), and I still have other computers where I can work, but I still need to get used to a bigger screen/keyboard.

So this is in some sense a nadir for shell scripting. 2 lines that do something out of 111. Mostly cargo-culted from cowpoke by ron, but much less fancy. rsbuild foo.dsc should do the trick.

#!/bin/sh
# Start a remote sbuild process via ssh. Based on cowpoke from devscripts.
# Copyright (c) 2007-9 Ron  <ron@debian.org>
# Copyright (c) David Bremner 2009 <david@tethera.net>
#
# Distributed according to Version 2 or later of the GNU GPL.
BUILDD_HOST=sbuild-host
BUILDD_DIR=var/sbuild   #relative to home directory
BUILDD_USER=""
DEBBUILDOPTS="DEB_BUILD_OPTIONS=\"parallel=3\""
BUILDD_ARCH="$(dpkg-architecture -qDEB_BUILD_ARCH 2>/dev/null)"
BUILDD_DIST="default"
usage()
 
    cat 1>&2 <<EOF
rsbuild [options] package.dsc
  Uploads a Debian source package to a remote host and builds it using sbuild.
  The following options are supported:
   --arch="arch"         Specify the Debian architecture(s) to build for.
   --dist="dist"         Specify the Debian distribution(s) to build for.
   --buildd="host"       Specify the remote host to build on.
   --buildd-user="name"  Specify the remote user to build as.
  The current default configuration is:
   BUILDD_HOST = $BUILDD_HOST
   BUILDD_USER = $BUILDD_USER
   BUILDD_ARCH = $BUILDD_ARCH
   BUILDD_DIST = $BUILDD_DIST
  The expected remote paths are:
  BUILDD_DIR  = $BUILDD_DIR
  sbuild must be configured on the build host.  You must have ssh
  access to the build host as BUILDD_USER if that is set, else as the
  user executing cowpoke or a user specified in your ssh config for
  '$BUILDD_HOST'.  That user must be able to execute sbuild.
EOF
    exit $1
 
PROGNAME="$(basename $0)"
version ()
 
    echo \
"This is $PROGNAME, version 0.0.0
This code is copyright 2007-9 by Ron <ron@debian.org>, all rights reserved.
Copyright 2009 by David Bremner <david@tethera.net>, all rights reserved.

This program comes with ABSOLUTELY NO WARRANTY.
You are free to redistribute this code under the terms of the
GNU General Public License, version 2 or later"
    exit 0
 
for arg; do
    case "$arg" in
        --arch=*)
            BUILDD_ARCH="$ arg#*= "
            ;;
        --dist=*)
            BUILDD_DIST="$ arg#*= "
            ;;
        --buildd=*)
            BUILDD_HOST="$ arg#*= "
            ;;
        --buildd-user=*)
            BUILDD_USER="$ arg#*= "
            ;;
        --dpkg-opts=*)
            DEBBUILDOPTS="DEB_BUILD_OPTIONS=\"$ arg#*= \""
            ;;
        *.dsc)
            DSC="$arg"
            ;;
        --help)
            usage 0
            ;;
        --version)
            version
            ;;
        *)
            echo "ERROR: unrecognised option '$arg'"
            usage 1
            ;;
    esac
done
dcmd rsync --verbose --checksum $DSC $BUILDD_USER$BUILDD_HOST:$BUILDD_DIR
ssh -t  $BUILDD_HOST "cd $BUILDD_DIR && $DEBBUILDOPTS sbuild --arch=$BUILDD_ARCH --dist=$BUILDD_DIST $DSC"

My primary workstation is a 3 and a half year old Dell XPS M1710 laptop and it is getting old the 320 Gb hard drive is getting small and slow, the 3 Gb or RAM (expanded from 2 Gb) look too small and screen is turning brown in one corner. Also dead or dying: keyboard (after cat+coffee incident), built-in speakers, battery, power adapter (twice replaced), DVD writer (rads but does not write any more) and fans (one replaced, one getting louder by the week). Also the video card is a bit slow for nowadays needs. So I set aside some money and started considering the options. In short, I could get another laptop OR get a regular computer for the same price but with twice the power. After considering all the laptop options up to 1000LVL, I decided to get a regular computer and if/when I ll need to travel I ll either take one of the old laptops with me or get a new netbook. Now comes the fun part choosing the components! So far my choices are as follows:

• 1080p LCD/TN monitor with a built-in DVB-T TV receiver, around 23 around 180 LVL (comparable options without the TV receiver are around 50 LVL cheaper, getting an extra digital TV in the house is a nice extra)
• Intel Core i5 processor and a corresponding motherboard from ASUS with 4 RAM slots and 1 video card slot (I like ASUS hardware and the TurboBoost technology of i5 sounds a very nice alternative to buying a high-Ghz dual core setup) 125 LVL + 80 LVL
• NVidia 250GTS video card (for my WoW raiding fun) 60 LVL
• 2*2Gb of DDR3 1600 KINGSTON RAM with lifetime warranty, leaving 2 slots for expansion later 60 LVL
• 1 Tb HDD (Samsung Spinpoint F3 HD103SJ got great scores in recent digital times reviews) 55 LVL
• Chieftec 500W PSU and case (good experience with them so far and good reviews) 70 LVL
• Blueray player with DVD-RW (why not at this price?) 60 LVL

And that is it a great setup that will last me a few years for around 700 LVL and it will have more partial upgradability than my laptop that I paid twice as much 3 years ago. Any tips? Did I miss anything? Is it likely that anything in the above list will cause me any trouble in latest Ubuntu/Debian installations? Update: got all of the above, except 500 Gb HDD of the same kind (faster, cooler, but higher price per Gb) and no Blueray (no drive in LV at the moment and did not want to wait a few weeks). The results are good, but I wish I would have gone with a 5 LVL more expensive video card that has a quieter cooler. Now I am buying a separate video card cooler for around 20 LVL that will be both more efficient and much quieter than the stock cooler I have Zalman VF1000 is the model. Has not arrived yet. P.S. It looks like updating a post in WP, automatically bumps it back into the Planet feed. Sorry