Yesterday I went to activate phone service out at the farm. It got me to thinking a bit about how things change, and how they stay the same, too.

Before I go on, I'll have to say that every one of my history books is in storage, so if I get some details wrong, it's because I'm not remembering correctly.

Anyhow, phone service came to our community via an unusual route about 100 years ago. It wasn't Bell/AT&T or some other company that brought it there, as it was most places. I'm sure they figured that a small, scattered rural community would cost too much to support. So the community organized, built, and supported the phone system themselves.

Even today, roads around here can be impassible after a good rain. I'm sure that, in the early 1900s, before heavy road-maintaining machinery, things were worse -- and, of course, transportation was a lot slower then anyway. There were real problems: getting the word out about funerals, being able to summon a doctor when necessary, or letting people know that church was cancelled because of too much snow.

People in the community saw a phone system as a real need. So did the churches, which have left a legacy that is still reflected in phone company territories today.

Once phone service arrived, it was used for all the things that people expected, of course. But it also proved to be an important part of the social fabric of the community. Since party lines were the norm, it was possible to announce things to every listening subscriber pretty quickly. Older people remember announcements of fresh fruit arriving at the grocery store, funerals, or other news of the day.

To place a call, you would pick up your phone and turn your crank. That caused a bell to ring at the telephone office, which everyone called "Central." The operator would connect to your line and ask whom you wanted to talk to. The operator would then send the distinctive ring for your party down their party line, and patch -- manually -- your call through to them. And, if he was busy, the operator wouldn't listen in on your conversation -- but others on the party line very well might.

Central's hours were published. If you were making a call in the middle of the night, you were going to wake up someone at Central to do it -- plus everyone on the entire party line. So calls after hours were rare.

Fortunately, while some of the old Central operators were still around, some people in the community wrote down some of their stories.

There were some people in the community that were notorious for eavesdropping on other people's conversations. Two brothers one time figured that they knew somebody was listening to their conversations, so they devised a code. One called the other, and said, "I'll be going to McPherson in the morning for band practice." That meant something along the lines of going to town to buy groceries.

A few days later, their prime suspect came up to him and said, "What on earth are you going to band practice for? I didn't know you knew how to play an instrument!" Apparently she realized she was had when he burst out laughing uncontrollably.

The Central operators learned to know the habits of telephone users. Sometimes they would connect calls without even bothering to ask who people wanted to talk to -- and seemed to always get it right.

The phone system supported itself for about 50 years. But as the rest of the world moved on provide direct dialing, this proved a controversial subject in the community. People liked having their operators. The people that worked at Central were everybody's friend. They were people that were there, 24 hours a day, to assist with any emergency. They would gather volunteer firefighters to help fight a fire, or be able to spread community news quickly. This wouldn't be available with the newer phone systems. How would the community be informed of events quickly now? Who would just happen to know whose house the doctor was at when he was urgently needed?

The change was resisted for some years, but eventually the finances of the telephone cooperative turned out to be in deep trouble. Operators grew to be much more expensive than automation, and in the late 1960s, the telephone cooperative was no more -- sold to a phone company from a small town more than twice our size, and a for-profit company at that! Central no longer existed. I remember reading about this event -- it seems people were sad about that for quite some time. They felt that they had really lost an important part of the community when Central went away. Some machine locked in a cabinet doesn't care for people the way Central did. Even today, the older people in the community sound a little sad when they remember telephone modernization, and get the wistful look of somebody that has just remembered something that they miss.

The phone company that bought the system wasn't an AT&T, though. It was a small, independent phone company. To this day, that phone company serves only the two communities. And it was this company that I called yesterday to establish service out at our house.

They had already upgraded our lines -- over a mile of new copper, benefiting only us, at no charge to us -- last fall. The box was already on the outside of the house. Just need to get it activated.

So I called the phone company. They said I needed to drop by their office and sign some papers. Uh-oh, I think -- this is a bad sign. Sounds like a bunch of phone company bureaucracy.

But not so much. I went to the office and signed up. They asked the usual questions: name, address. Plus a few that bigger companies wouldn't ask: who used to have service at that address? Of course, most people would know that answer in our community. I couldn't have told you in Wichita, Dallas, or Indianapolis.

Then they asked when I'd like service to be activated. "As soon as possible," I say, figuring that this would be a couple of weeks like it is with AT&T or Sprint. "Well, we probably can't get out there for a couple of hours. Would it be OK if it's on at about 3?" Yes, that would be fine!

Now, how about DSL? "Well, we're a little backed up on that right now." Uh-oh. Sprint took several weeks when they *weren't* more backed up than usual. "So it'll probably be Monday or Tuesday before we can get out there. Should I just have the installer call you and arrange a time when it gets closer?" Yes, that would be fine, too!

Now, how about finding a phone number.

Out comes a large paper book. Yep, paper. They paged through it, and told me that my grandpa's old number would be available if I wanted it. I said yes -- after all, we've got his old address, so might as well keep the same phone number. OK, no problem. She whips out some white-out, whites out grandpa's name, and writes ours in. Done.

Now, do we want any optional services? Caller ID, call waiting, voicemail? How much is caller ID, I ask. $5 a month. We'll try it for now. "OK". A box was checked on the form and that was that. No high-pressure sales pitch on taking "the works" for some poorly-disclosed price, providing a ton of services I'll never use and don't want. No confusing "discounts" for having The Works and DSL at the same time.

Then I ask about an unlisted number, or at least an unlisted address. We figure that anybody that we really want to be able to reach us will figure out how without using a phone book, and these things get in so many databases these days. Sprint charged almost $10/mo for a fully unlisted number, but only a few dollars a month to just keep our address off the directories.

Our new company charged 50 cents a month for a fully unlisted number. Done.

Now it's time to pay for the first month's fees and the setup. Oops, I've forgotten my checkbook in the car. No problem, the secretary says, I'll watch your baby while you go get it! Jacob was with me, but had fallen asleep, so I brought him inside in his car seat. I went to get the checkbook -- just out the door and close by. I was back in a few seconds later, and the secretary was already on the other side of her desk talking and playing with Jacob. "My baby's 12 now," she said, and for a second, looked like a person that was remembering Central.

Greg Kroah-Hartman's new book Linux Kernel in a Nutshell is now available in stores, as well as for download on his website. To quote O'Reilly:

Written by a leading developer and maintainer of the Linux kernel, Linux Kernel in a Nutshell is a comprehensive overview of kernel configuration and building, a critical task for Linux users and administrators. No distribution can provide a Linux kernel that meets all users' needs. Computers big and small have special requirements that require reconfiguring and rebuilding the kernel. Whether you are trying to get sound, wireless support, and power management working on a laptop or incorporating enterprise features such as logical volume management on a large server, you can benefit from the insights in this book. Linux Kernel in a Nutshell covers the entire range of kernel tasks, starting with downloading the source and making sure that the kernel is in sync with the versions of the tools you need. In addition to configuration and installation steps, the book offers reference material and discussions of related topics such as control of kernel options at runtime. A key benefit of the book is a chapter on determining exactly what drivers are needed for your hardware. Also included are recipes that list what you need to do to accomplish a wide range of popular tasks.

It's yet another great book licensed under a Creative Commons license. It's good to see that more and more books are now being freely licensed...

Dear lazyweb,

• I've tried to avoid join or start flamewars in the Debian mailing lists. I think i managed this task very well.
• Based on my experience into pkg-perl, i had the idea to start a related Python project since there were a lot of Python modules out there and just a few packaged. I've founded python-modules with Guilherme Pastore (pkg-python name wasn't available) and we were joined by Raphael Hertzog some time later.
• I had the idea and talked with Otavio Salvador in Brasilia, Brazil during a cluster, linux and FOSS community gov't related event about the ltsp status in Debian and how it would be cool start a project in cooperation with Ubuntu. We've founded pkg-ltsp and had a online meeting at #ltsp were ogra and mdz (from Ubuntu fame) participated too. Since then, ltsp in Debian is way better than it was. I did technically way less than i could to the project itself, but i've an entire year to fix this. Thanks vagrantc and pere too for all the hard work and help.
• Merged debian-desktop development page, mailing list and alioth project in a focused thing with permission of the founders and was joined by pkg-gnome, pkg-kde, pkg-xfce, pkg-galago and tasksel members. The group did some great stuff together and it was just a restart.
• Worked very hard on Custom Debian Distributions camp, specially with Vagrant Cascardian on Simple-CDD for Etch.
• Joined pkg-gnome, tasksel and a lot (really) others projects that i did my best to help.
• I did my first security upload.

Looking back, what a insane year, but not due to the Debian related stuff that was fun to do, to say the least. Anyway, i hope to write similar stuff in the next year but with a even more exciting content. Thanks for those that helped me and those who did something for Debian in the past year. See you!

Now that I have my desk sorted in my new flat i’ve begun to use my wireless mouse again. I was pleasantly surprised to see that gnome-power-manager (through HAL) gave me battery statistics on my mouse. Cute. So in the next major release I expect it to warn me when *my* energy levels are running low and suggest I take in a caffeine fix.
GNOME power manager strikes again!

Just spent a long weekend (Thursday night to Monday afternoon) in Finland. Hanna invited me over a while ago with a promise of sauna and ice swimming, and I'm a sucker for travelling to parties these days... *grin*. Unfortunately, the weather in Finland (just like in the UK) at the moment is ridiculously warm for the time of year. When I visited in November for the BSP, there was some snow on the ground and temperatures were as cold as I expected. This time, there was no sign of any snow and I was worried that we might not get any ice...! Lars was kind enough to offer me some crash space at short notice for my visit (there's nothing like last-minute organisation for this kind of jaunt!). On Friday we met up with Jesus, Jeroen, Hanna, Pixie and Dave for lunch and some wandering around in the middle of Helsinki. Then on to some bars later for some drinks and food. I could get used to this... :-) On Saturday, we got up early, bought large amounts of food and drink to take with us, and caught the bus north-west out of Helsinki towards central Finland. 90 minutes on the bus and in a taxi, and we were dropped off at Hanna's family's cottage by the lake below: As we got there, the temperature was dropping just enough that we could actually see the ice forming on the lake. Beautiful! In the middle of nowhere in the forest, things were incredibly quiet and peaceful. We lit the fire for the the sauna, and wandered off for a walk through the forest. Later on, beer, sauna and (almost) ice swimming. Naked geeks! I must admit that I chickened out a little - coming out of the sauna into freezing temperatures slowed me down a little. By the time I reached the bottom of the steps to the lake surface, I couldn't force myself into the lake fully. I got three toes wet, then ran back inside into the warm... :-) Dave was more resilient (in and out FIVE times!), but it looks like he maybe overdid things. He crashed out later and was acting quite oddly for a while - we worked out that he was probably dehydrated. We carried on drinking and snacking at the cottage, then headed back into Helsinki for the bars and clubs later that night. More of the same on Sunday along with a cinema visit, and I was thoroughly exhausted and ready to head back to the UK on Monday. Thanks very much to Hanna, Lars, Jesus and the others for making my trip so much fun. Helsinki is a lovely place to visit, although probably too expensive for me to manage it too often. I'm saving already for the next time! I've put my photos online as usual.

Debians /etc/network/interfaces is a powerful way to setup multiple profiles; NetworkManager is a pretty UI for managing your network. However they don't play well together: NetworkManager will ignore devices managed via network/interfaces. However, NetworkManager lacks a couple of important options, including static IPs and several wireless options; I can't connect to my universities WAP2 network using NetworkManager because of some missing options. This is why I wrote this small script:

#!/bin/sh
# disable network manager:
dbus-send --system \
  --dest=org.freedesktop.NetworkManager \
  /org/freedesktop/NetworkManager \
  org.freedesktop.NetworkManager.sleep
sudo ifup eth1=eth1-lrz

My /etc/network/interfaces contains a working setup for my wireless named "eth1-lrz"; since this differs from the real device name, this works fine. Running this script will tell NetworkManager to disconnect and instead setup the wireless for my university network. When connecting to a different network, I only have to do "ifdown eth1" and then click on the NetworkManager applet to enable it again. (would be "org.freedesktop.NetworkManager.wake")

There are some things that I have learned over the years as bad practice. There are some that I have learned through reading and contemplation, and a little experimentation. One of the categories of bad things that I have learned is visual aids for statistics. There is basically one cardinal rule for data presented in a graphical form:

Let the user see the actual data.

It seems kindof obvious, doesn't it? I'm presenting data, you should be able to see it. If you want to show me that there are 450 widgets, and 230 whazits, and only 210 whositz, then you should show those. The simplest way of doing this is by just listing them out in a table:

Type	Amount
Widgets	450
Whazits	230
Whositz	210

That's simple, isn't it? However, it doesn't help the viewer any. They're pretty good if you want to know exactly how many of something there is, but not great at other things that you want to do with data. How do you find the minimum (or maximum) of all of the values? You scan, remembering the highest one you saw so far, and then go back to that one and find out. If the goal is to somehow compare, the viewer will be helped out by using a graphical display of some sort. One thing that humans are good at estimating is length. Quick, tell me what we have the least of:
That was easy, wasn't it. Bar charts are good - they can still be abused by people in evil ways, but most of the time they're pretty useful.

All of this is working up to pie charts. What's smaller, Whazits or Whositz here:

Is Widgets half or more than half of the pie? Pie charts are the bad seed of the graph world. They aren't very useful, hang out a lot, and don't help you much. The worst thing about pie charts is that they aren't even good at the thing they're supposed to be the best at: comparing relative sizes. Consider thanksgiving, or christmas, or whatever large gathering you prefer where there is pie. Lots of pie slices are laid out on the table. Which one is the biggest? It's hard to tell. It's even hard to cut even slices from a normal pie. Sure, you can cut in 4ths, 6ths, or 8ths, but I challenge you to cut a pie in 5 pieces equally - it's really hard! It's because humans aren't great at judging the differences between angles. They're only really good for seeing one thing: the largest piece in the pie. Even then, it's sometimes questionable - if you looked at a evenly sliced pie, could you tell the difference between a 23% piece from a 20% piece? The bad thing about this is that they are ingrained into our culture. There wasn't a finance report in the last 10 years without a pie chart.

All of this ranting was basically brought to you by a recent post on BoingBoing. This post features the most horrible monstrosity I have seen in a long time: the hierarchial pie chart. Feast your eyes on this monstrosity. I challenge any reader to tell me: what is the smallest third-level category? What is the largest?

Our brunch yesterday went super-well. We had about 15 people over, which was far too many for our supposedly mellow evening. But it was great -- we got to catch up with a lot of folks I've been missing over the holidays and haven't gotten to see. I hadn't seen Lucinda Catchlove much for a few months, and Heather Kelley and Damian DiFede made an appearance, too. We got to see John Usher, who's off to do weird things to people's ears at the Consumer Electronics Show in Las Vegas. Niko came with friend Johanie, who made some great black-bean brownies; DJ Ghostbeard was still feeling ill from NYE; and Meg showed off her deep purple hockey bruises. It was also nice to have some new friends come, too. I've been wanting to hang out with MC Turgeon, one of the most experienced bloggers in Quebec, founder of me dia and toiles-du-Web, since we met last year at South by Southwest. She and her partner Chris came over with a nice bottle of wine and got to know everyone there. Actually, she knew a lot of the people already -- she and Anne-Marie had met at Mutek, for example. When Patti came in, she said, "Oh, yeah, I know M-C. We do a lot of panels together." Ah, the panel circuit. Altogether a really good time. Probably the only downside is that our oven was really dirty, and while I was making quiches and roasted potatoes I smoked up the entire house. But it cleared pretty quickly, and with the nice weather we're having, I could even have the kitchen door open to clear the smoke. Unheard of! tags: bruncher mcturgeon montreal cooking

Making a point Speaking of unseasonably warm weather, the Green Party of Canada held a picnic and ice cream social on Mount Royal last Saturday, which would have a couple of feet of snow on it in a regular year. The subject of discussion? Climate change, of course. I dunno -- clever move, but do they have to rub it in? tags: green party picnic climate change

Shameless plugs My friend Allegra has started a great new blog, Sucking-stones. She's got a really good voice and it's now in circulation as one of the blogs I read each morning. Also, my friend Anne-Marie Bergeron has her first travel TV show on 33mag tomorrow. She's got a four-part series on her trip to Iceland which they're going to show. It's in French, but her husband Jeff only cusses in English, so that's probably what you'll hear when they're climbing glaciers and lava floes. Did that get everyone? I hope so. You know what they say: You can plug your friends, and you can plug your ears, but you can't plug your friends' ears. Or something. tags: allegra sucking-stones annemarie jeff 33mag

Chix I was just reading Angela Beesley's end-of-year blog post and realized that I'd missed the establishment of WikiChix. It's a new organization for female wiki participants, in the great tradition *Chix tradition of Linux Chix or Debian Women. All the more galling is that two other blogs I regularly read also covered the new group. Joseph Reagle made a note about gendered spaces and the role they play in any movement (like Open Content and wikis). Biella blogged about his bloggage and put some social-science twist that was a little hard for me to follow. In any event, good luck to WikiChix. I find clubs extremely fun and useful and by nature exclusionary, and nothing to get worked up about. Of course, as one of the two founding members of the Maldekstrulaj Vegeteranaj Esperantistaj Linuxamantoj (Left-handed Vegetarian Esperantist Linux-users Club), I'd probably be pretty hypocritical calling anyone else exclusionary. tags: wikichix wiki angela beesley joseph reagle biella coleman clubs

Quadmachine is a virtual instruction set architecture, designed mainly as a target for simple educational compilers. It has the following noteworthy features:

• RISC design
• word size 64 bits
• address size 64 bits (theoretical maximum memory size 16 exabytes)
• all memory access is in word units
• 65534 general-purpose 64-bit registers
• 2 additional special-purpose 64-bit registers
• a variant of the “register windows” technique with automatic spilling

All of these, except for the preposterously large register file, are more or less realistic for a 64-bit RISC design. The size of the register file is intended to trivialize register allocation in compilers. This is the second Quadmachine design. Main differences from the previous design are a move to a load-store RISC architecture and the upgrade of the word size to 64 bits. There is a software realization of the Quadmachine architecture, with a graphical debug console. It is written in Java for portability; speed was not an implementation concern. Read more

In my other posts about Christmas, I wrote about my memories of Christmas awhile back.

In this final post, some more recent memories.

Terah and I don't really have a Christmas tradition yet -- things seem to keep changing.

Our first Christmas after being married was in Indianapolis. Our church there didn't have a Christmas Eve service, so we went to a different one. We also bought a tree from Tree Classics that year:



The next year, we moved to Kansas. Our church has a children's program on Christmas Eve, but Terah likes the more meditative lessons and carols service that her church used to have on Christmas Eve, so sometimes we've gone to a different church that evening -- or even to two different services.

This year, we're in an apartment, and we've got Jacob. That makes everything more fun. Here he is in a festive holidy mood:



Of course, the one thing that a festive holiday mood is sure to lead to in a 3-month-old is a not-so-festive holiday bout of fussiness.



Our tree this year is borrowed. Ours, along with all of our Christmas decorations, lights, and wrapping paper, is in storage. So some of our gifts aren't wrapped. But that's OK -- we enjoyed Christmas all the same.



In this, my last post on Christmas for this season, I wanted to follow up on my earlier post about my Grandpa Klassen. I wrote:

Grandpa was great with the harmonica. And the song I best remember him playing at is Nun Ist Sie Erschienen. I remember sitting on his lap many times listening to him play it. And I'm pretty sure it was a year-round song for him. Terah and I even had it sung at our October wedding -- if it was year-round for Grandpa, that was good enough for us. It's always special to sing the song in church.

I was going to have a picture of Grandpa with his harmonica here, but I didn't get it ready in time. So I'll have to describe it. Imagine a black and white picture of a gentle man, dressed conservatively, holding a harmonica in his hands. He's looking towards it tenderly -- it seems to be something important, and maybe it represented fond memories for him, too. I'll post the photo as soon as I get a copy of it.

Well, here's the photo:

As part of my work on Xen I've been playing with Xephyr (a replacement for Xnest). My plan is to use Xen instances for running different versions of desktop environments. You can't just ssh -X to a Xen image and run things. One problem is that some programs such as Firefox do strange things to try and ensure that you only have one instance running. Another problem is with security, the X11 security extensions don't seem to do much good. A quick test indicates that a ssh -X session can't copy the window contents of a ssh -Y session, but can copy the contents of all windows run in the KDE environment. So this extension to X (and the matching ssh support) seem to do little good.

One thing I want to do is to have a Xen image for running Firefox with risky extenstions such as Flash and keep it separate from my main desktop for security and managability.

Xephyr :1 -auth ~/.Xauth-Xephyr -reset -terminate -screen 1280x1024

My plan is to use a command such as the above to run the virtual screen. That means to have a screen resolution of 1280x1024, to terminate the X server when the last client exits (both the -reset and the -terminate options are required for this), to be display :1 and listen with TCP (the default), and to use an authority file named ~/.Xauth-Xephyr.

xauth generate :1 .

The first problem is how to generate the auth file, the xauth utility is documented as doing it via the above command. But this really connects to a running X server and copies the auth data from it.

The solution (as pointed out to me by Dr. Brian May) is to be found in the startx script which solves this problem. The way to do it is to use the add :1 . $COOKIE command in xauth to create the auth file used by the X server, and to generate the cookie with the mcookie program.

In ~/.ssh/config:
Host server
SendEnv DISPLAY

In /etc/ssh/sshd_config:
AcceptEnv DISPLAY

The next requirement is to tell the remote machine (which incidentally doesn't need to be a Xen virtual machine, it can be any untrusted host that contains X applications you want to run) which display to use. The first thing to do is to ssh to the machine in question and run the xauth program to add the same cookie as is used for the X server. Then the DISPLAY environment variable can be sent across the link by setting the ~/.ssh/config file at the client end to have the above settings (where server is the name of the host we will connect to via SSH) and in the sshd_config file on the server have the line AcceptEnv DISPLAY to accept the DISPLAY environment variable. It would have been a little easier to configure if I had added the auth entry to the main ~/.Xauthority file and used the command DISPLAY=:1 ssh -X server, this would be the desired configuration when operating over an untrusted network. But when talking to a local Xen instance it gives better performance to not encrypt the X data.

The following script will generate an xauth entry, run a 1280x1024 resolution Xephyr session, and connect to the root account on machine server and run the twm window manager. Xephyr will exit when all X applications end. Note that you probably want to use passwordless authentication on the server as typing a password twice to start the session would be a drag.

#!/bin/sh

COOKIE= mcookie
FILE=~/.Xauth-Xephyr
rm -f $FILE
#echo "add 10.1.0.1:1 . $COOKIE" xauth
ssh root@server "echo \"add 10.1.0.1:1 . $COOKIE\" xauth"
echo "add :1 . $COOKIE" xauth -f $FILE
Xephyr :1 -auth $FILE -reset -terminate -screen 1280x1024 $* &
DISPLAY=10.1.0.1:1 ssh root@server twm
wait

Amita June is reaching a point in her life where it's time for us to start weaning her from breastfeeding. Most parents do this much earlier, if they breastfeed at all, but we've been devotees of attachment parenting for a while, and we wanted to give her as much time nursing as possible. But at 15 months, she's ready to start doing things like sleep through the night on her own, drink only cow's milk, and be a little more independent. So, this month we're starting to do some night weaning. What does this mean? First of all, Maj is no longer nursing the baby to bed. She now is doing the main pre-sleep prep work (a bath), does a short nursing period, and then hands the baby off to me for some reading, songs, and walking down to sleep. This will gradually move into fewer, shorter nursings before sleep, and ultimately to none. Once that connection has been broken, I think the main point of nursing will be occasional comfort nursing during the day. Gradually, that will fade out. And then there will be none. It's kind of exciting to be the Primary Sleep Guy for the baby. We're re-connecting in a way that we haven't in a while -- I was only putting her to bed occasionally for a quite a while. It's also been pretty successful so far, which has been good. tags: amitajune weaning sleep parenting babies

Souper Bruncher When Maj and I first moved to Montreal, we had help from some friends who we'd known from before. After we moved into our apartment, we invited them all over for dinner to say thanks. In order to get to know people in our new hometown, we also asked each person to bring someone we didn't know, so we could make new friends. The event was so successful, and we met so many new people, that we made it a regular occasion. For almost three years, every Tuesday night we invited friends over to our home for dinner (or souper in Quebecois French), with an open invitation to meet new friends and interesting people. It was a great way to meet interesting folks in Montreal, and most of our best friends here we met through these dinners. We were even profiled in Elle Quebec as a model for how to make new friends. But when the baby was born, we just couldn't manage to organize dinners any more every week. Cooking for 20+ people isn't that expensive, especially since we're pescevegetarians and that kind of food just isn't that costly. But it does take a lot of time and energy, and with a newborn baby we just didn't have either. Now, with Amita a little more than a year old, we're trying to start up our regular home parties on a more manageable scale. We're doing brunch at our house on Sunday afternoons around 3PM, with a much smaller list of invitees, requests for RSVPs, and a clear indication that the event only goes until bedtime. (Our Tuesday night dinners would occasionally stretch until dawn.) It seems to be working pretty well; we've had a lot of fun at the last couple of brunches we've had. And brunch is a much more laid-back meal than a dinner party, anyways. (Although John Usher asks incredulously, "By what stretch of the imagination is 3PM between breakfast and lunch?") I'm looking forward to our next brunch (tomorrow) a lot, and I hope to get many more friends over to our home in the next few months of Sundays. tags: brunch montreal making friends souper bruncher

(continuing with clearing the blogging backlog) Four days after returning home to the US from the trip to Australia, I was at it again, flying the other way around the world. In hindsight, this was totally insane, but I'd expressed interest in going much earlier in the year, I think before we'd organised to visit Australia. I flew to Madrid, via Philadelphia. I've said it before, but I'll say it again, Philadelphia International is a very nice airport. It's the first time I've flown across the United States, and it really is a long way. Just like Brisbane to Perth, it's a long time on a plane for staying in the same country. Arriving in Madrid, entering the country was extremely straightforward, as I've also said previously, the immigration guy barely looked at my passport long enough to open it and find a page to stamp. It was my first time in a country that didn't speak English and wasn't terribly bilingual. Fortunately the airport was signed in English as well as Spanish, and the information/assistance people all seemed to be able to speak English. I arrived in Terminal 1, and the European contingent were mostly arriving at Terminal 4, which is essentially a completely separate airport, a short shuttle bus ride away. My flight arrived in the morning, and I had about 4 or 5 hours to kill before the first of the European contingent rocked up. It was tempting to get a train or taxi into Madrid and have a bit of an explore, but I really didn't want to risk not getting back in time, so I just loitered around Terminal 4 for the time. The highlight of the waiting was I bumped into Doug Foster, who I used to work with a SecureNet in Canberra, disembarking a flight from London (where he's now working). It really is a small world. After everyone turned up, we got on a bus and headed for Badajoz, a mere 5 hour bus ride away. We didn't get away until about 7pm, so by the time we hit the road, it was dark, so there wasn't a lot to see. We arrived at Badajoz around midnight, and made a short walk to the hotel and had a late dinner and hit the sack. Unfortunately with all my travelling in the three weeks, I'd managed to come down with a cold, which started manifesting itself pretty much from the moment I got to Badajoz, so I started to feel increasingly suboptimal as the week wore on. Badajoz itself is an incredible little city. It's just like what I envisaged an old European city to be: narrow winding streets. It had a funny effect on me. I'd alternate between finding it really quaint, and incredibly claustrophobic (and I'm not usually the claustrophobic type). After doing a bit of self-analysis, I think the problem was the lack of sky. With so many buildings crammed in together and the narrow streets, the amount of sky you got to see was minimal. Definitely no horizon. I felt more comfortable at night, in fact the place looked really awesome at night. Everything was lit up, I think especially so for Christmas, and everyone came out and walked around and did shopping. The other thing that, well, I noticed about the city was that it was wall to wall concrete (or bricks, or bitumen). The buildings all connected up, there were no gaps between them, and the sidewalk basically ran from the front edge of the building, to the kerb, then there was the road, and then the reverse, so it was a real concrete jungle. That said, it was pretty clean. the sidewalks were all swept, there was no rubbish in the gutters. By about the second day, my cold had driven me crazy (my nose was running incessantly) and I just wanted some pseudoephedrine to dry it up. I didn't have a clue how pharmacies operated, but fortunately I was able to get Miriam to tag along with me, who spoke English as well as Spanish. She'd never heard of pseudoephedrine before, but as soon as she said it to the pharmacist, he knew what it was and came back with some form of Nurofen (ibuprofen) that also had pseudoephedrine in it. I didn't really want or need the ibuprofen, but when sick in Spain, beggars can't be choosers, so I took it. I didn't feel that it did a great deal for me anyway. Getting home again was fun. Due to various peoples' flights, the bus was leaving at 6:30am, and that wouldn't get me back to Madrid the ideal 3 hours before departure, so I took a taxi with a few people who needed to be there earlier. It left Badajoz at midnight, and arrived at Madrid at about 4am, where I had to wait for about 5 hours before I could check in for my flight. I had a bit of fun leaving, which I've already written about, and was happy to get home late on Sunday night. My cold had gone to my chest by this stage and I had bronchitis, so I was just glad to get home and see a doctor on Monday. So now I can say I've been to Europe. It was a shame I didn't get to see Madrid itself. Next time. Update Photos from the trip are here

Ocamlnet 2.2: test it by yourself from experimental A couple of days ago I finally managed to complete the packaging work of Ocamlnet 2.2. This upstream version is a (r)evolutionary release in which it aggregate in a single source package libraries who used to be distributed separately, namely: equeue, ocaml-rpc, netclient, and ocamlnet itself. I've been quite surprised to discover that upstream is explicitly nice with us packages and provides guidelines on how to split the various libraries in binary packages addressing both dependency and licensing problems (e.g. for nethttpd which is GPL and can't be shamelessly linked with other components which are MIT/X11-licensed). The packages are in experimental but need NEW-processing, as well as cryptgps (a pure-OCaml implementation of some symmetric crypto algorithms, which is a new build-dep of Ocamlnet). Hence to ease testing I set up an apt-gettable repo here:

deb http://people.debian.org/~zack unstable ocaml

Please try it and give feedback to debian-ocaml-maint@l.d.o. In all my tests the upgrade from ocamlnet pre-2.2 has been smooth: the (too many) transitional packages I had to create did their dirty job. The only "issue" non-addressed (and I don't know how to actually) is that the nethttpd library used to be distributed in libocamlnet-ocaml-dev and is now distributed in libnethttpd-ocaml-dev. Since the former package is entirely useful without the latter there is no dep among the two and it's possible that upon upgrades an user ends up without a working nethttpd library on the system. I added a Recommends in the hope it's enough, let's see how many complaints I will receive ...

Seems that I manage to publish yearly news. Well this time I've many of them. DebianPeru's event videos.
As promised, we've published the videos for our D aDebian 2006 anual event. You can find the event videos and also the lightning talks videos.
I want to thank our sponsors and people involved on producing them. We are already working on our next event which is mainly focused on attract, teach and involve more people on directly contributing to Debian and free software. Talking about Debian events and user-base growth, when I went to the place to make stickers for give out on our last event, I went with the swirl logo and said to the business owner: I want to print this. He said ok, and later he asked me: is it Debian right? I was like... yes!. Later we talked a bit more and he told me that he found Debian on the Internet while looking for alternatives to have his business run safely, since, as he related me looking worried, the police came to their place and seizure all the computers from other businesses claiming that they are running "pirated" software. So he found Linux and Debian. He told me that was having some issues with their devices, mostly his CD/DVD printers and scanners. We talked a bit more and I invited him to our local group and the event of course. It was a very cool incident, and I nominated him our official merchansiding supplier ;) Debian gaining market share.
Last year was quite good for Debian in Peru, besides the growing user-base, some government agencies have explicitly named as the operating system or linux-flavour they want third party deploy for them. One of the most important cases, IMHO, is the PDT software, which is the program that every business should use to submit taxes information. Currently it's only available for Windows and it's written in Visual Basic. Although, mostly because it's lack of stability and extensibility by third party, some government agencies have been pushing for SUNAT open it's source code. It was, as with many other out of place subjects, source of lot of flames and irrelevant waste of time by the local linux-supporters. Anyway, they didn't open the software, but instead they called for software vendors to compete for the development of a new version which should be multi-platform and according the specs at least run on Windows, Linux and Mac OS X, and on the Linux side they mentioned specifically that the program should be apt-get-able, thus vendor should provide a Debian package compliant with 3.0 or superior. Microsoft loves Debian.
I was invited to, which was meant to be, the true and first Microsoft vs. free software debate in Peru, but was, as we in APESOL have experienced for years: Microsoft refusing to debate. So it was mostly APESOL being technical, as requested by orga, and Microsoft being funny. I was astonished that almost half of Microsoft speakers mentioned Debian at least 5 times in their talks and dedicated almost half of their time to talk about free software (open source), interoperability and technological neutrality. It was fun for me to see them helping us to get known. There are some pictures on my flickr page. Personal life and Debian work.
Last year I've lost my two cats, both died in not a very good way, they are missed for sure. I'm sure I want a full white one, but not sure how soon. I've been really busy working on my business which led me to not being able to contribute as much as I wanted but I managed to do some stuff. In the other hand I've learned many important things that we, as free software community should seriously consider. Most of them have been already pointed out by some people on p.d.o already. Ok I believe this is enough, blame this to the not-blogging-for-long-time syndrome due the commies hidden over there locking my access to former hosting.