Here s for the second installment of my review of this past year s Summer of Code at Debian. See the previous part here: Debian Summer of Code 08 : Where are they now (part 1/3). I apologize for being so late at getting this second part out but I have been very busy. Still, I ll get the last part out before FOSDEM. Those of you who ever had to write a Java compiler (ok, Java subset, but the OOP part was here ) in brainfucking Ada will understand what I went through working on two of my most loathed languages. Debian NAS, improve support of Debian on NAS devices Presentation There is a large range of inexpensive Network storage devices available on the market. For some of them, such as Linksys NSLU-2 and Thecus N2100, we have added support, but there is many many more devices we could support. For this summer we look forward at supporting multiple Marvell Orion based devices (as outlined in Martin Michlmayr s talk Running Debian on Inexpensive Network Storage Devices), such as Revogear Kuro Box Pro, Buffalo Linkstation, QNAP TS-109+, If you don t have old computers lying around to turn into NAS servers, you need to sleep at night without the soothing sound of computer fans or if you actually pay your own electricity bill, you might want to have a look at standalone NAS devices. They re cheap and can be made vastly more capable by slapping a Debian on it. If you ever heard of DD-WRT, you know the spirit. The project was mentored by Riku Voipio, with help from Martin Michlmayr. The project proposal (sorry, Google cache) was introduced by Martin, who did a presentation about it the previous year at FOSDEM. Student Per Andersson was a 24 year old student working towards a MSc in computer science at Chalmers University of Technology in Sweden. He had been looking for ways to join Debian but with school still being priority one, he didn t find time to dive in. Result This project was successful. The Kurobox Pro is now supported and several useful tools were packaged to make life easier with these NAS devices. Martin Michlmayer is still working on Debian NAS related stuff. Per was happy to be invited to the Emdebian work session in Extremadura and has been active within debian, maintaining the packages he created during the Summer of Code. Cran2deb, generate Debian packages from R packages Presentation GNU R has become the preeminent platform for computing with data . The CRAN archives contain over 1300 source packages of very high-quality, and BioConductor has again almost as many focuses on bioinformatics. We want more of these in Debian, and going beyond the 50+ packages we currently have suggests more scripting and automation. R is a pretty big among statisticians and all of them they wasted no time writing their own package to work on particular research subject. It s a lot like Perl with CPAN or LaTeX with CTAN. It s always a pain to discovery that a particular R package is not wihtin Debian and having to resort to unmanaged installation of said packages. The project was mentored by Dirk Eddelbuetel. The project proposal (which is nowhere to be found but seemed to be good) was introduced by Dirk, along with another proposal he did for R. Student Charles Blundell is a research student at.. hum.. didn t do my homework about that. Anyway, you can find him around R related projects. Result This project was successful. Cran2deb is happilly turning more than 1400 of the ~1500 CRAN R packages, all with correct dependencies. The work has since been moved to R-Forge. It s working, we re almost there. We just need it to be polished and we ll get a whole bunch of new packages into Debian. Charles pinged me about the status of Cran2Deb after the previous post. He admits that he hasn t done much about cran2deb recently because of his new position as a research student but hopes to commit again to it soon. I do encourage him to get these R packages into Debian. I had to manually install some packages myself when I had to use R for school because they weren t into Debian and it s not pretty. Mergemaster, interactively merge changes in configuration files Presentation FreeBSD has a shellscript called mergemaster which is used to interactively merge changes in configuration files, based on 3-way diffs. Debian s approach to configuration file differences is much more primitive: either keep the original file, or blow it away (including all local changes) and use the Debian-provided file. It would be nice to get a system such as mergemaster into Debian. Important is to remember that Debian contains two often-used configuration file management systems: ucf, and conffiles; porting mergemaster in such a way that it will be used in both cases would be great. The handling of configuration files during upgrades has always been a little.. brutal, with the user being asked at gunpoint to make a good decision, lest the upgrade won t continue or configuration files get borked (ever tried automerging nagios configuration files?). Having a less stressful upgrade experience is a good thing since the point of Debian is to make package management a stressless thing. The project was mentored by, hum, Manoj Srivastava. I have no idea who came up at first with the proposal. UPDATE: Wouter Verhelst mailed to say that he made the original proposal. Student Max Wiehle was a physics student at the University of Heidelberg. He did a Summer of Code stint (Archive.org copy..) as a student for Beagle Project in 2006 which, I suppose, was successful. He s been active in the past with Gnome and desktop related projects. Result This project was somewhat successful. He posted an update one month into the program with repositories with code to test. Last commit to the mergecf branch of project was September 19th but it was never merged in. According to Steve McIntyre, it s dead, Jim. I couldn t find any further public involvement of Max within Debian. PAS NSS Debian Installer, improve support of PAM and NSS at install-time Presentation It would be very important for the Debian allowing the user to configure additional PAM and NSS modules (eg. LDAP, NIS) during the installation process inside the Debian Installer. To do this, we have to provide tools and helpers to modify /etc/nsswitch.conf and /etc/pam.d/common-*, as well as changing the maintainer scripts for the packages libpam-* and libnss-* to apply the required changes at install time using debconf and these helpers. To be honest, I will probably never use this. I don t do that many coordinated installs in the same place to warrant doing funny authentication with PAM and NSS, and if I did, I would probably use a more elaborate tool to personalize the install, like FAI. On the other hand, I can see the appeal of being done with authentication mechanisms before the first boot. The project was mentored by Fabio Tranchitella. The proposal came from the student. Student Juan Luis Belmonte was a computer science student. He worked in a couple of companies in the area of Sarragossa. He is now founding debug_mode=ON. Result This was quite a disappointement after seemingly good work. Although Juan was satisfied with the project, the PAM package maintainer (Steve Vorlon Langasek) was not. He was never asked about this project (but didn t intervene timely either when the accepted projects were announced though). In his words, it was the wrong solution to the problem . You can find his lenghty rationale on the wontfix bug report that resulted from the project. It really was a problem of communication with the Debian developpers since Juan could certainly have done the right work if pointed to it. Juan didn t ask thoroughly for existing work and Steve didn t publicize his (enough). That s all for now. The information is quite fragmented I admit. Most of it was pulled from Google, mailing lists, commit logs, blogs, whatever. If some projects are lacking in information here, it s because I couldn t find it readily (which is an issue in itself!). In my next post, I ll try to give a student point of view of the Summer of Code in general, and more specifically, at Debian. It will be post 2.5/3 since it s getting a little longer than I planned. Release early, release often, as the say.
If you re a student or a mentor mentioned above, feel free to fill any of the blanks in my report. It s much appreciated. You re not a student or mentor mentioned above and have an opinion on how to improve the next Debian Summer of Code ? Feel free to comment.

Sigh. I'm not part of the FOSDEM organisation team, and this is by choice. I know that I wouldn't find the time to help organize a conference of the scale of FOSDEM, since I'm rather liable to forget to do important things at times. Having said that, I happen to run a company together with Philip Paeps, who is now one of the main FOSDEM organizers; apart from that, I've also managed the Debian presence there for the past few years (lost count how many exactly), and arranged the key signing party for a few years with Joost Van Baal taking over for me starting this year. As such, I'd like to believe that although I'm not exactly in to all their secrets, I do have a front-row seat when it comes to how things are going there. FOSDEM is the "Free and Open Source Developers' European Meeting". It has been that since 2001, and will always remain so. Yes, originally it was called "OSDEM", because frankly, the organisation of the original OSDEM was done by a group of people who like Open Source, without necessarily subscribing to the Free Software ideals. The core group of the organisation is a rather diverse group; for instance, Philip has been known to be rather... negative... about Ubuntu, while Mark (one of the press contacts) has done some activism and translation work for Ubuntu. The change of name from OSDEM to FOSDEM was done not because the organisation's ideas about software were changed overnight by a mail from Richard Stallman or anyone else from the FSF; but rather, because they were open-minded enough to understand that having a name which only says 'Open Source' would be excluding a considerable part of the community that encompasses both Free and Open Source people. This is why the name wasn't changed in FSDEM; it is FOSDEM. I'm quite sure that the fact that FOSDEM is so open-minded about many of the controversial issues that have separated our community over the years not just Open Source vs Free Software, but so many other things as well is one of the main reasons why FOSDEM is so popular today: because everyone, and I truly mean everyone, will find something that he or she likes. That is why I'm so saddened that some people seem to find it necessary to not only whine, but also boycott a conference, because they believe that FOSDEM should not take money from a big Free Software/Open Source contributor, just because they also happen to be a company, and as such make business deals with Microsoft. Note that I'm not either defending or condemning Novell's attitude here; but it is a fact that not everyone in the larger Free and Open Source community feels the same way about the whole Novell/Microsoft deal (else there wouldn't be an openSUSE anymore), and as such they still deserve a place on FOSDEM. Over the history of the organisation of FOSDEM, it's always been a place where everyone could get their opinion out; whether it be the opinion that "Free Software Must Rule The World", or that "It's All About The Way You Do Things"; as long as your opinion is shared by a large enough number of people in the larger FLOSS community, it is welcome. I feel that blocking one organization from sponsoring the event, just because they have made some deals which a significant group of people, one which nevertheless does not encompass the whole of the FLOSS community, disapprove of, would set a dangerous precendent that might jeopardize the very core of what makes FOSDEM so great: its impartiality. Thank god that didn't happen.

I'm using Drupal from several sites as a CMS/CMF, e.g. Buildd.Net and SysAdmin-Jobs.de. Drupal upgrades its database with a dedicated script, which usually works well. But I experienced some problems with taxonomy terms and nodes after upgrade finished. For example all forum articles are "lost". They are still there but have lost information to which taxonomy term they belong. And because Drupal uses taxonomy terms for its forum tree, no forum article is displayed any longer.
Same problem is with Blog articles that are tagged with taxonomy terms: the node is still there, but the taxonomy information is lost.

Looking at the databases table term_node for Drupal5 and Drupal6 makes the difference visible:





So, obviously the update script of Drupal misses to store the additional table row vid somehow. At least all the difference in the table schema causes the loss of taxonomy terms of those nodes.

So, I wrote a little script called bin/drupal6_fix_taxonomy.sh to fix that problem for my PostgreSQL databases:



It works for me![TM]
Use it at your own risk!

It's been a somewhat long day... I got up at 6:30am for a 7am ankle physical therapy session. I went to the hospital after that. When I got there, a sonographer was doing the echocardiogram on her heart to check the valves. I missed the doctors. Sarah didn't feel any more knowledgeable about her condition even though they'd been through. The patient Sarah was sharing with had a bad night, caused her to have a bad night's sleep also, and she always deals with all of this crap much worse when she's got a sleep debt. Dinner stayed down, but breakfast did not. The sonographer seemed fairly confident about her heart condition. Usually they don't make any comments on what they're seeing and leave that to the doctors, so we took some comfort from that. I managed to corner the physician's assistant who had been following Sarah in her office, and quizzed her on what was going on. It turns out a PICC line had been ordered, and they get installed by specalised PICC nurses and that's all they do all day. The PA implied that it might not happen until tomorrow. The gall stones were definitely unrelated, and something to follow up with her primary care physician. Incidentally, Wikipedia has some wicked pictures of gall stones. Talk about freaky. I think I hung around until 10am, and then headed into the office to try and get some work done, with the intent to come back after work. Not long after, Sarah called me up all beside herself about the PICC line (she doesn't deal well with the idea of getting jabbed at the best of times, and being tired put her over the edge), so I scrapped work, and went back to the hospital for the remainder of the day. I decided to hunt down her cardiologist to see if the PICC line was absolutely necessary, and I managed to get the exact low down on her condition.

• the infection is staphylococcus aureus, not one of the other staph strains that I can't remember, which are considered less serious. The one Sarah has/had is the "bad enough" one, a.k.a. "golden staph". Fortunately it's sensitive to antibiotics, unlike MRSA, which is the really bad news one to have. So my heart skipped a beat when he said it was aureus, but I recovered when he said it was sensitive. I could have sworn the staph infection she had last year wasn't aureus, but he seemed to think that it was.
• when she presented at the ER on I guess Sunday morning, this staph was found in the blood sample they took. What is unclear is whether this is because of contamination from the skin when they took the sample (staph is present on the skin, it's only a problem when it gets internal), or it was indeed in her blood, whereas with the infection she had last year, it was never present in her blood.
• because of her aortic root replacement/graft and the risk of endocarditis destroying her heart valves, they didn't want to take any chances. Hence the PICC line and the two weeks of intravenous antibiotics. Two weeks is really a compromise. He said if they'd wanted to get all paranoid on her, it'd be a six week course, and they'd have done a transesophageal echocardiogram to boot.

So armed with the facts, I headed back to tell Sarah the news that she really should have the PICC line installed, and that she was getting off fairly lightly, relatively speaking. The PICC nurse had a cancellation, so she was able to do the installation today. It was totally less traumatic than I think either of us were expecting. It took about 45 minutes to install, and it was done at her bedside. Sarah was very brave and I don't think it really hurt her all that much. I watched the whole thing, and it was very interesting. It was particularly interesting because there was another nurse observing, so the PICC nurse was explaining everything as she went. She was also really nice and good at what she did (she'd been doing it for 14 years) so I think all of that helped. So Sarah's now got two IV ports strapped to the inside of her upper left arm (attached to the PICC line), and no other IV lines in. She should get discharged tomorrow after they sort out whether she's going to receive IV antibiotics on a 4 or 8 hourly schedule at home, and exactly how all of that's going to work. I think they send someone out to our place to give us some training, and someone comes out once a week to do a bit of maintenance on the PICC line itself. I presume I'll be her personal nurse again. All it involves is a bit of plumbing. Her cardiologist seems to think she should be able to still do her CNA clinical training with the PICC line in. She may just have some problems with lifting duties. I guess we'll just see how all of that pans out. So that was the excitement for today. Sarah had her appetite back at dinner time, and was generally in much better spirits when I left her this evening than she was this morning. I could go into much more detail about the ins and outs of the PICC line installation, but I don't really have the energy.

Moving on from the horrible tax situation, I m struggling to get three pieces of hardware working. I m terrible with hardware. Can anyone help me get these working better, please?

1. I ve been lent an Asus M5200N after I busted my shoulder with a 7kg laptop at #davebcs. I ve managed to enable processor scaling as ondemand, but like the page says, the fan is noisy. Other sites report that the Centrino s thermal limit is 100C, so is it OK to set the fan not to kick in until 78C on the sensor? The default is 40C which means it s permanently on - the coolest the fan makes it is about 74C.
2. The Asus has Ubuntu on it (intrepid I think). Is there an easier way to get my three GPRS connection working than copying the config files from the old laptop and using the terminal? Network Manager doesn t seem to work and I can t see what it s trying to do or why it s failing (where s its debug log?). Alternatively, is there a distribution better suited to occasional laptop use than Ubuntu?
3. I ve been lent an iPod Touch. However, when plugging it into the USB on the Asus, the screen says simply iTunes and the quick start guide says to connect it to iTunes. Can gtkpod do this, is there another way to start it up from Ubuntu, Debian or GoboLinux, or shall I beg access to a computer running iTunes?

Thanks for any answers. I may send out small gifts in return because questions 2 and 3 seem very awkward to me.

Fellow countrymen, happy Republic day to you all. Any trip to Punjab is incomplete without atleast one visit to the daily tamasha at the Wagah-Attari border. This is probably one of the few places on earth where you would see the Pakistan flag right next to the Emblem of India.

I arrived at the place a couple of hours before the vening flag down ceremony but was too late to be able to get a comfortable seat in the crowd of a few thousands; the place was already packed. Luckily, a BSF ranger (who incidentally was not allowing the crowds in any more) looked at my tripod and camera, thought I was a journalist and led me to the VIP section which is as close to the gates as one can get.

For a very long time preceding the ceremony, there is nationalist music blaring on the tannoys, crowds screaming in unison: LA ilAha ill-Allah on the Pakistani side and vandE mAtaram, bhArat mAtA ki jai on the Indian side. On either side of the border gates, kids run up and down the road with their respective national flags while young men climb onto the top-most walls and wave flags high in the air. One gentleman was commenting that while women on 'our' side are allowed to dance and sit anywhere, 'they' don't allow that, "see how the men and the women there are grouped separately".


The half hour of the retreat ceremony is full of action with the Indian BSF rangers in their red turbans and khakhis, and the Pakistani rangers in black salwaar-kameez marching heavily down the road, glaring into each others eyes, competing on who can kick higher into the air and possibly also on who has the best kept moustache. The rangers on either side of the gates know that they are entertaining their home crowd and spare no effort to do their best.


The retreat ceremony is so popular that it is difficult to allow in all the people that come in to watch. So a clone of the ceremony has been setup at the Hussainiwala border. However, Hussainiwala is popular not because of the flag retreat, much less because the 1971 war memorial still has a lot of marks of artillery firing, but because of Bhagat Singh's memorial. The memorial moves one to tears.


Few more pictures from the Hussainiwala memorials:

Executive summary To avoid confusion with the proprietary versions of GForge (known as GForge Advanced Server, GForge Express Edition and GForge Community Edition), the free/libre/opensource codebase will from now on be separately maintained under the name FusionForge by the main developers of the free GForge 4.x codebase. Since this is mostly a renaming, the migration path for existing users will be smooth. Longer version, with details After the initial forking from the Sourceforge codebase, the development of GForge has long been hosted, and many enhancements directly developed, by the GForge Group (GForge, LLC), with regular contributions from outsiders. The results of these evolutions were public and free, subject to the GNU GPL. In parallel, the GForge Group wrote a proprietary re-implementation of GForge, which it sold under the name "GForge Advanced Server", or "GForge AS" for short. This re-implementation added some features for "the enterprise", but was not contributed wholesale to the GForge codebase under a free license. Although some of the features were contributed to the public, the GForge Group concentrated its efforts on its (proprietary software) business model, with more versions appearing, such as "GForge Express Edition" and more recently "GForge Community Edition". As a result, it became increasingly harder for the public to know which version was which without doing extensive research (indeed, some users mistakenly installed one version instead of the other). A consequence was that the free software codebase suffered from a loss in visibility, which lowered its momentum to the point that there haven't been any moderately important releases since the (currently stable) 4.5.x series was announced in late 2005. So, in order to clarify things, avoid further confusion, and regain some of the lost momentum, it was decided by a group of leading contributors that the free software version of the GForge codebase would from now on be developed under the FusionForge name, and its development would be hosted on FusionForge.org. So is this a fork? Well, we don't know yet. It could arguably be called one, since we're taking the code and running away with it under a new name. However, we believe it's not a fork unless both roads continue their own way (more of a oddly-shaped bend). What happens to the GForge codebase developed by the GForge Group at gforge.org remains to be seen, although for the sake of our users we will backport security fixes to the gforge.org Subversion repository (at least for the 4.5.x series and the unreleased 4.6 and 4.7 pre-series) for some time. The bulk of the development will move on to FusionForge and the repositories at FusionForge.org, though, and users are encouraged to migrate at their own pace. Since we're basically continuing the evolution rather than starting from scratch, the migration path should be rather smooth. So why the FusionForge name? Because there were actually lots of locally-patched versions of GForge (and Sourceforge), and we felt it was a waste of resources that should be fixed. It seems many people and organisations took these codebases at some point in time and evolved them for their own needs. Sadly, many of the changes were not contributed back or even published, so lots of efforts were duplicated. Fortunately, many of the people managing these locally-patched forges are now realising that "out-of-tree" patches and features require quite some manpower to maintain. Some formal inter-project discussion is already taking place, and we hope to achieve actual merging of most of the interesting features that have been developed here and there into a common base that can be reused locally with minimal changes. We'd like to "un-fork" as much as possible. We also expect that, by using standard components and tools, we'll facilitate the work of potential contributors, thereby reducing the risk of a new era of fragmentation. And who are we anyway? We're Christian Bayle, Roland Mas and Alain Peyrat, long-time contributors to GForge and responsible for over 95% of the commits over the past two years, as well as a few relative newcomers. Christian and Roland have been maintaining the Debian packaging since the "Debian-SF" era, and Alain has been focusing on code quality. The three of us have, for various reasons, a vested interest in maintaining a lively codebase in a healthy ecosystem. What are our plans? Our short-term goals, as currently planned, include:

• pushing a stable FusionForge release out of the door;
• cleaning up and auditing the database schema to ensure consistency and increased performance;
• merging in new plugins, in particular for new version control systems;
• continuing streamlining the installation process to make it more portable across distributions.

Longer term goals are less well defined, but we're thinking about the following:

• increasing code quality by the use of modern automated tools;
• encouraging a lively stream of external contributions, to reduce the gap between the official version and the locally-patched ones;
• defining an explicit governance model and release process for the FusionForge project;
• as a consequence, a more frequent and predictable release schedule;
• increasing data portability and interoperability with other forges, to reduce lock-in for users and projects.

Some of these items should be facilitated by our switch to a distributed version control system and a new coordinated workflow. Also, the Debian i18n team has been kind enough to offer to host our translation effort on their Pootle server, which means translators will have a much easier time doing their job. We hope to hear from users and contributors alike in the near future. For more information, we can be reached via our fusionforge-general mailing-list (see our lists), which is also suitable for general discussions. We can also be found on IRC (#fusionforge on the Freenode network).

This week's emacs-snapshot release (20090118-1) reached a new milestone with more than 700 downloads in just under a week. I guess this is quite an achievement considering that not everyone wants to download 25MB of Emacs packages on a weekly basis, so thanks to all my users for their continued trust and support!

Here's a quick update on the status of the Emacs 23 release: the last remaining feature on the roadmap was finally completed this week with the merge of the rmail-mbox (pmail) branch into rmail. The pretest (GNU lingo for beta ) phase could start as early as next week, which is not to say that the release itself is right around the corner since a few major tasks need to be finished first, like updating the manuals. The release could also be delayed by the proposed (and long overdue) switch from CVS to Bazaar, pushed by newly-minted Launchpad evangelist Karl Fogel.

That being said, aiming for a release in 2009 isn't entirely unrealistic, and I really can't wait to see Emacs 23 reach a wider audience. It is the culmination of many years of work in lots of areas (Unicode support, font backend, multi-tty, Cocoa, ...) and is by far the best Emacs version to date!

If you are in the NY-area and would like to help out with the project described below, they are looking for volunteers. Help FLOSSIFY the enormously popular book Digital Foundations. The event is being hosted Feb 6-8 at the lovely Eyebeam with some Free as in Beer and Grub provided! ******************************************************* FLOSSIFY 1 : Digital Foundations
For a long time educational courses have been cheap marketing
for proprietary software companies. Can a student really afford all
those expensive softwares required by the courses? No. Ever hear of a
software company kicking up a fuss because students are using
unofficial versions? Well, it does happen but not often. And why not?
Because proprietary software companies know, as the universities know,
that once the students leave their training they will be indoctrinated
with those tools and simply slipstream into being paid up proprietary
software citizens. Simply put, unlicensed software used in education is
tolerated because it is cheap marketing. This is how tools become industry standards . FLOSS Manuals is fighting this flow by converting textbooks that
use proprietary software to using free software in their examples. We call this process FLOSSify . We convert the book from
closed software to Free Libre Open Source Software (FLOSS) hence we
FLOSSify the book. Our first text book is the wonderful Digital Foundations book produced
by Michael Mandiberg and Xtine Burrough
(http://digital-foundations.net/). Its a text book designed to teach
software by teaching design. The current toolset it uses is the Adobe
Creative Suite and we will convert these examples entirely to using free
software. FLOSSIFY 1 : Digital Foundations will focus on a fun 3 day event at
Eyebeam, NYC. Anyone is welcome to attend and some food and beer will be
provided. Come and meet some of your old geek friends, make some new,
and help make a step towards unshackling education from proprietary
software. FLOSSIFY 1 : Digital Foundations
Eyebeam, New York City
Feb 6-8
starts 10ish
finishes when we are done
fast connection, a table, some chairs, and beer and food provided
contact adam@flossmanuals.net for more info venue:
http://eyebeam.org/
540 W. 21st Street, (between 10th and 11th Avenues)
New York, NY 10011
Tel. 212.937.6580 Fax: 212.937.6582

A while back, I suggested to Achim to add a new CRAN Task View for High Performance Computing with R. And as of a day or two ago, we now have the new CRAN Task View for High Performance Computing with R providing an overview about available packages, grouped thematically, with a focus on the various parallel computing application. I have already received a few great comments that even lead to an entire new section on applications. Keep'em coming!

I found a reference on the 'net about a week ago about SimTower. I remembered playing it a long time ago and thought it would be fun to try again since I hadn't beaten it. so I found my old copy and started playing. I've acheieved TOWER status in the game in 9 years.

The basic plan I used to beat the game was to build as wide as possible and to use 3 normal elevator shafts per 15 floors, 8 stairs and 2 escalators. Primarily my building was all offices. For the there are two sets of stairs going up 3 floors from each lobby. There is also an escalator going down from the lobby for each set of stairs and one more set of stairs going down a floor from the escalator. For the floors that have stairs going to them, there should be no elevator for that floor.

Now there are only 9 floors left that need elevator transportation. The best strategy I figured out for these floors was 3 elevators, each hitting 5 floors. That way each floor got one elevator shaft and a 3rd elevator shaft provided a bit of extra transport.

The 14th floor in each set is a good place to put cafes, and shops. I put a couple cafes and shops in, a security office at on one end, then put some offices in to use up some of the remaining space on the outside of the building. I left a bunch of space between the cafes and offices.

The first 15 floors are special since those floors should have 3 floors of offices, 6 floors of hotel rooms, one housekeeping station per floor, and a service elevator between the hotel floors. Then topped off with offices.

The basement floors had shops, cafes, restaurants and a cinema on floors b1 and b2. Parking was on floors b3, b4, and b5. The recycling centers were on floors b6 and b7, then the metro was on floors b8, and b9 with the metro taking up b10. I also put shops and cafes on floors b8 and b9 with the metro.

For the express elevator I tried to have on each express elevator go to the basement floors and 1 above ground floor. This way floor 15 and floor 30 has separate elevators shafts. Each elevator had as many elevator cars as it could take.

Using this strategy I used 63 above ground floors to get to 15k people and had 128 million dollars. I didn't lower the rent on any offices until I was building up to floor 100 for my cathedral, where I lowered prices on many offices between floors 45 and 60 where I did lower the price to keep tenants. I did lower the price on some hotel rooms much earlier in the game.

You can browse with my wide tower.

I spent a while this morning hunting down the root cause of a 100% CPU MIMEDefang process. (Turned out to be one specific email triggering one of my custom SpamAssassin rules that seems to get processed really inefficiently.) I wasn t able to find any documentation on how to debug where in MIMEDefang an email was getting stuck, and even jacking up the debugging output of my mimedefang-filter script seemed to imply it was happening late in the filtering process. After digging through mimedefang.pl, I found a status reporting subsystem and tracked it back out into configuration in /etc/default/mimedefang:

# Uncomment next line to have busy slaves send status updates to the
# multiplexor. NOTE: Consumes one extra file descriptor per slave, plus
# a bit of CPU time.
# MX_STATUS_UPDATES=yes


Turning this on, and then using md-mx-ctrl busyslaves (I command I didn t know existed until today either) I got to see exactly where it was stuck:

3 B 13380 (Running SpamAssassin j951iX1t025805)


Now I m having fun running md-mx-ctl with histo, barstatus, and load. :)

Once upon a time I ran a Valentine-Matching site for Livejournal users. (Actually I did it for about three years in a row, but then got bored.) The basic idea was simple, you'd visit a magical site and it would present you with the usernames of all your friends. You'd tick a few boxes, and that would nominate those users as your potential valentines. Then you'd do nothing until February 14th, at which point you'd discover if you matched. A match being made if you chose bob, and bob chose you in return. (Essentially the site is a big double-blind matching system, albeit with constrained membership, via lj.) The major technical difficulty in early days was preventing spoofed accounts. I didn't want Evil Alice to be able to visit the site and pretend to be Bob. In the couple of years I did this I came up with a couple of fun schemes to minimize the chances of this occuring - anything from using email validation, to requiring that users taking part updated their profiles to include a magic cookie-string, or posting to a specific community which I could later screen-scrape. These days the use of openid allows me to prevent spoofing in a trivial manner - and once I realised that I figured why the hell not?! In short here I am and here we go again:

• http://my.ljvalentine.com/

The motivation? Playing with openID and because I still like to "match people up". I am aware of one marriage that resulted from a match on my system back in 2003. There could be more. If you're a long-time reader you might remember ctrl-alt-date - how time flies - I just let the domain name(s) expire this week. The timing is a little bit of a coincidence, but not entirely. The only thing that I'm doing this time is not sending emails on matches, because I just can't. Unless I asked people to volunteer their mail addresses I don't have the data. Still I expect remembering to return for the results won't be a challenge. Now, lets get viral. But not in an icky fashion .. ObFilm: Daywatch

Some time ago I've blogged about the downside of large disks being long the huge amount of time that it needs to check them with badblocks for medium errors.

As I told there, I bought two Seagate Barracuda ES.2 ST31000340NS and most of you might have heard about the firmware problems of those disks from Seagate. Seagate writes:

*Please email discsupport@seagate.com to request a firmware upgrade if your drive is on a release earlier than SN06.

Please include "ES.2" in the subject line of your email request for proper routing.

Well, I did write last week already, but haven't got any reply yet. This morning I mailed Seagate again, but no reaction so far until afternoon. Not even an automated "We got your mail and will answer it!" mail.
So, if you're in a similar situation you might ask yourself: "How can I get those firmware updates for my ES.2 drives then?"

Well, for me this trick worked quite fast:

1. Go to the Seagate Contact Page
2. Choose your region and country of Technical Support
3. Click on "Chat" and wait...
4. ... and wait...
5. ... and wait...
6. ... and wait...
7. Request your firmware update from the friendly support staff that appeared somewhen
8. Check your emails
9. Follow the instructions in that mail

Yes, I've had to wait nearly one hour until someone showed up in that chat window, but then it worked quite nicely: I've got my email, downloaded that ZIP file and ... no! I didn't updat the firmware yet. I think I'll wait some more days, maybe until next week, and see if this firmware update is now working properly for others.
Maybe some will call me a coward, but I'm just following those friendly letters on that specific book you all know:

Don't Panic!

My disks are still working and my UPS does so as well. So, no need to hurry... But it's good to know that I could upgrade if I would like to... :->

The subscription will end on January the 25th, for people willing to come to this unique OCaml event, this is your last chance !!!! We have 40 participants for now. I am quite happy with this number because it is almost the same as last year -- except that we do it in Grenoble rather than Paris. Anyway, I see that a lot of people who were there last year, will come back to this year events. There is also a few more people, in particular more from CAML consortium members. I have stepped down from the first talk about OCamlCore.org in favor of Stefano Zacchiroli. Zack has really helped me on this project since the begin (with Pietro Abate and Romain Beauxis). I am very happy that he can do the talk. I will do myself, a talk about my last project for Talend. This was a great project targeting to be as fast as a standard C application but in OCaml. The point is that OCaml helped me to do quickly a working prototype and then optimize it for speed. All in all, after 6 months I was able to deliver Talend with a working and fast application. This kind of release cycle is harder to achieve in other programming language. OCaml compile time verification helped me a lot. I hope that in the last remaining 2 days, some more people will subscribe. Wiki Subscription

Today I had the occasion to do something I normally don't do: send a text message. I can report that it's a lot like writing an email. If all the bones in one of your hands are broken, that is.

When I was a kid, I had a daddy with this moustache. One day, he shaved it off. I looked at the pale, exposed strip of lip, and demanded he grow it back. There are no images of this event, besides those burned into my brain. It was in simpler times. Dad did grow it back, and a beard too, and and now he's (great)-Grandpa Hess. Who, come to think, looks similar to my tie-died friend Bdale. Bdale is one of the Debian grandfathers, those old guys who the young ones in the project look up to. And today, he scarred all their minds. The collective shout of "grow it back!" is gonna be huge. Did I mention that it all involves Tasmanian devils, charity, and the mean razor of Linus Torvalds? These are not simple times.

I have been listening to music from the Laya project since a few days. It is a set of CDs I picked up from an interesting hippie-ish place called Psybabas on Castle street. Actually, one rarely gets to listen to such sounds. Ideas of similar music can be found scattered in the movies from the early 90s; Hai la sa reminds me of ETilOni sEpalanTa from donga donga. My favorite track though is LA ilAha ill-Allah which sounds very fresh and different from how one would expect it to be.

On a related noted, ETilOni sEpalanTa was composed by A. R. Rahman. I have great respect for the gentleman and recently H pointed me to an article in Tehelka titled The Mystic Master. While a lot has been written about him recently, mostly in the backdrop of The Golden Globe that he won, this article dwells on the person unlike probably anybody did before. Must read.

Our power alone cannot protect us, nor does it entitle us to do as we please. . . Our security emanates from the justness of our cause; the force of our example; the tempering qualities of humility and restraint. - Barack Obama, inaugural speech, Jan. 20, 2009

This, right here, is why, for the first time in my life, I actually feel good about an American president. Why I have hope about our government for the first time in years. Why I m glad I used a vacation day to sit on the couch and watch TV yesterday. On the occasion, once every 4 or 8 years, that is a celebration of American strength, power, and pride, we see our new president speaking of humility, of peace, of moral leadership, this is something remarkable. Past presidents have used occasions such as these to speak of crushing our enemies, of wanting people dead or alive, of grand government promises that turned out to triple the national debt. Obama spoke of extending the hand of friendship to anyone that would unclench their fist. He spoke that we had kicked the can down the road too far, and now we ve reached the end of the road. We have to stop thinking that we can have everything: low taxes, expensive programs, and a large military, simply by mortgaging our future. And he leveled with us: we all are in this together, and all have to work to make it better. Conventional politicians assumed it would be political suicide to say even half of what Obama has said. Yet he went out there and did it. He was blasted during the campaign by people on both sides of the political spectrum for being just words . He s the first presidential candidate that meant what he said about bringing Americans, and their representatives, together. The shock in Washington has he invited gasp! both an openly gay bishop and an anti-gay evangelical minister to give prayers was telling. It s as if people were saying, Wait, he really MEANT that? Yes, he did. Let s hope he can pull it off. And as Rev. Lowry concluded with his benediction:

With your hands of power and your heart of love, help us then, now, Lord, to work for that day when nations shall not lift up sword against nation, when tanks will be beaten into tractors, when every man and every woman shall sit under his or her own vine and fig tree and none shall be afraid, when justice will roll down like waters and righteousness as a mighty stream. . . Let all those who do justice and love mercy say Amen. (amen) Say Amen! (Amen!) Say Amen! (AMEN!)