Crossed Wires RSS

Photo printing pain

Tue, 16 Dec 2008 03:47:34 +0100

S went to print some photos the other day, and what was supposed to have been a simple exercise turned out to be a very frustrating one for both of us. I was utterly amazed to discover that even on the eve of 2009 there are web sites that think the world is only viewed through Windows…

S's and my respective creative sides are being adequately satisfied by the iLife suite on the Mac, but there are times when we need to get the pictures out of the silver tower and onto other media—on this occasion paper, for albums and so on. A large retailer here has part of their floor space in each store set aside for those photo printing kiosks, and I introduced S to the art of putting photos onto a USB stick so that she could print some photos when next she went there…

On her return from the shop, she reported that we hadn't successfully put the photos she wanted onto the stick. When she'd plugged the stick in, she'd found only less than half of the photos we'd stored there. Sure enough, when I plugged the stick in all the files were there safe and sound. Strange thing was I could find nothing in common about the files (uppercase/mixedcase filename, long or 8.3 filename, datestamp, etc) that would have yielded the number of photos that the kiosk had found on it.

Annoying, but life is too short to worry about it. After all, this same retailer was plastering adverts of their new web-based photo printing service… S could submit the photos online for printing and pick them up from the store later.

<sarcasm>This is where the fun really started.</sarcasm>

Their app is Flash-based but seems to have some Java involved as well. While it loaded quickly enough, the app portion of the web page had an incongruous grey background that just looked dodgy. S had to create an account and sign onto the site just to get this far though, which was a bit annoying.

The workflow seemed to be to create an album, upload pictures to the album, then select photos from the album for processing. Creating the album went fine, but when the upload function was selected there were no action buttons visible to complete the operation! S was using Safari, but Firefox made no difference.

Then I suggested she use her laptop, which runs Ubuntu 8.04. The situation actually seemed a bit better to start with, as instead of the upload function showing an embedded file selection dialog like it did on the Mac we got a "normal" GNOME file dialog box. However, only some of the photos showed again: this time, it was because they had hard-coded a non-modifiable filename filter for the dialog that was only picking lower-case file extensions!

Trying to work around this, I mounted the stick manually with different mount options. I succeeded in getting all but one of the files showing with a lowercase name, and a rename fixed that one. Back in the web page however, it still didn't like us: any file chosen from the dialog box resulted in a nonsensical error message followed by a "You have selected no files to upload" dialog.

S was beyond caring by this stage (she has a very low threshold for being stuffed around by technology). She went to Snapfish after a friend's recommendation, and found a well-designed and easy to use WEB site that required no downloads or other junk.

So why did this wind me up to the point of spending all this time blogging it? Because nowhere on Big-W's site is there any mention of browser or operating system compatibility. Not even a "we've tested only on Windows, Mac users may experience difficulty"[1]. Not a blessed thing. Their Help page has a single paragraph about trouble uploading, blaming "your IT Department" for "setting certain network properties that inhibit the upload tool from working".

I wonder if the developers of the app were just so blind to believe that their gunk would just work wherever it was run, or whether they really think that it's a Windows world. Of the two I hope it's the former. ;-)

So Snapfish gets a recommendation for being not just an application hosted on the web but a web application. They do good photos too!

[1] I never expect to see Linux mentioned on these things and get pleasantly surprised on the occasions it is; even if it says "Linux is not supported", someone there at least knows enough to mention it.

BOM Radar for Cisco 7970

Thu, 11 Dec 2008 17:26:09 +0100

I've written an XML app to display rain radar images from the Australian Bureau of Meteorology on the screen of a graphics-capable Cisco IP phone. It seemed like it would be simple to do, and I couldn't work out really why no-one had done it. Well it wasn't hard to do, but I can see now why it hadn't been done…

While the screen of the 7970 looks nice on it's own, and is certainly a drastic improvement over the 7940/7960, it doesn't have the resolution to be able to display anything useful other than text and simple images. The BOM images are 524x564, while the largest image the Cisco can show is 298x168.

Here's an example of my app in action:

Because the phone's image viewer can't scroll a large image I've had to scale and crop it, losing a fair amount of detail in the process (I did try just scaling it to fit the entire image, but it was totally useless to view). Plus, one of the key attractions of the BOM radar site is the animated images, and the phone has no way to display animations.

So what do you think, lazyweb? I've learned a bit more about coding Cisco XML apps, but other than that have I wasted my time? I will put it up on my Projects site eventually (once I've put in some more error handling etc), but let me know with a comment here…

Living with an iPod touch

Wed, 10 Dec 2008 22:23:35 +0100

I held out for a long, long time. I'd even talked myself entirely out of getting one. Like they say in the classics though, "you think you've escaped, but they pull you back in". I now have a 32GB iPod touch and it's doin' alright, even though it took me nearly a week before I bothered putting any media on it!

I think what finally did it for me was the App Store. I love being able to simply go to an app on the device and easily look for software, installing what I like with no fuss. I especially like the fact that my downloads are synced with my computer, so that I don't have to keep track of all the individual items I've installed (unlike my phone; I can't think where all the sis and sisx files for different stuff I've installed might be).

My Facebook friends will know that I'm much more active there suddenly. Why? The Facebook app on the Touch — I no longer have to start up a computer or open a browser to update my status or reply to comments. I had a bit of this function with Fring's Facebook interface on my phone, but the large screen of the Touch makes things like this much more friendly.

I came very close to getting an iPhone actually — but not to use as a phone. This was after I'd realised that it's just as valuable as an Internet-connected device as an actual phone. The cost of iPhone service is still a bit prohibitive to me though, especially for an occasional-use device.

One of the things that had turned me off was the closed nature of the iTunes ecosystem (iPod, iPhone, Apple TV, iTunes). People sometimes ask me about Skype, and I say that the worst thing about it is that it Just Works. I mean, it's a closed system with no interconnections other than those provided by Skype themselves — by this nature it should fail, and yet because it works (arguably) better than any other desktop VoIP product it enjoys immense success. Same goes for Apple's stuff: the iTunes ecosystem Works And Works Bloody Well.

I've been thinking for ages about sync for calendar and contacts and stuff; I've been hunting for services and software and tools for ages. I could build something myself, and indeed started to (I've looked at Google Apps, used Chandler, checked out Ovi, and played with Sync4J before it was called Funambol). I could spend time and effort coming up with something myself…

Or I could just buy an iPod.

The difference between pipe and redirection

Thu, 04 Dec 2008 01:58:29 +0100

Newcomers to UNIX-like operating systems are often confused by the difference between the shell operations pipe and redirection. The difference is easily explained with an example, in the context of web development. The shell command echo "st=1" | ./lifeswork.pl shows how a pipe is used to supply command line input to a script usually invoked via CGI in a web server. This allows the script to be more easily debugged by testing at the command line. The shell command echo "st=1" > ./lifeswork.pl shows how redirection uses command line input to overwrite a script file, destroying the file and the web developer's sanity. Hopefully this example illustrates the difference between pipe and redirect, and helps you avoid the idiotic mistake I just made.

Security blows

Tue, 25 Nov 2008 02:00:45 +0100

I was about to post about how pleased I was with Synergy in helping me tidy up my desktop clutter (by removing a keyboard and mouse from the surface). Ironically, I'm instead posting about a problem with the configuration that will cause me to throw it out and look for something else. Why the title? Because the default configuration of a Linux distribution nowadays has given me no way to fix this ridiculously simple problem without powering off the running PC, VMware guests and all.

The problem is that Synergy and the VMware console don't play well together (I could have sworn that when I first started using Synergy I had no trouble with it, but there are a few hits around that describe problems like I've now hit). The problems people are reporting are that keys like Shift and Ctrl are not passed to the VM (some described here and here).

My problem is slightly different: the screen of my Synergy client (the one that's running VMware) locked while a VMware guest had focus. Now, the Shift and Ctrl keys are not picked up by gnome-screensaver to unlock the screen. Even the real keyboard attached directly via USB doesn't work. Big problem, for the following reasons:

* Thanks to password strength rules enforced on the Linux build I use, my password now has a Shift-obtained punctuation character.
* I can't switch to a virtual console, since that requires Ctrl (e.g. Ctrl-Alt-F1).

Okay, so the keyboard doesn't work. This client machine just happens to be a tablet PC, and I had hacked gnome-screensaver (to display the onscreen keyboard to allow the screen to be unlocked in tablet mode). I grabbed the pen and tapped out my password, but it *still* didn't work: even the output of the virtual keyboard gets the Shift modifier dropped. Hmm... Starting to fume now.

Never mind, I'll connect via the network...

* Fedora does not start SSH by default (okay, yes, and I didn't make sure it gets started after I'd finished the install).
* There is no remote desktop (VNC server, XDMCP) configured.
* The shiny web-based management interface on VMware Server 2.0 only listens on 127.0.0.1 (or is being blocked by the Fedora firewall).

So with no way to get access to the machine to try and fix it, a power-off is the only solution. Some readers are probably thinking "boo-hoo, diddums had to kill-switch his widdle poota, how tewwible," but I hate having to do that; not because the system doesn't recover, but it's "problem resolution, Windows-style".

Even though the real problem was between Synergy and VMware, I'm blaming the (perceived) need for security since without that I wouldn't have a cryptic password that I can't enter without Shift and a system I can't administer over the network. Red Hat and Fedora doing everything in their power to ensure I don't fall prey to nasty Internet fiends (rich analogies to governmental nannying, but that's probably over-thinking things).

So in summary: Synergy is great, just as long as you're not using VMware console and have a password with punctuation or uppercase... Remember to have your SSH or other network access enabled before you play!

We finally meet K (a.k.a. Clinker)

Wed, 19 Nov 2008 00:07:13 +0100

To our beautiful baby girl, the warmest and fondest welcome!

The post I made here last night was going to be a comment about how ironic it was that we didn't want to know our baby's gender and yet the time of the birth was known. Well as fortune would have it, I would have been wrong on both points!

We were due to arrive at hospital at 1:30pm today for a 2pm induction, but our baby had different plans! S went into labour spontaneously at about 1:30am this morning, so we had the dash to the hospital that we never thought we'd have. By 2:30am we were in the birthing suite, and just over one hour after that our baby girl K arrived!

As for the gender thing, although we were obviously going to be happy to have a healthy baby of either gender we'd both been hoping for a girl. This time, something was telling me that it was in fact a girl--I guess you'd say I was very confident. So confident in fact, that S was quite angry at me about a week ago for not committing to a name for a boy. :-)

N met his baby sister this morning... he has a very proud-looking smile on his face whenever he looks at her! He's a wakeup to our grownup tricks though--we'd bought him a present to take home with him "from the baby". When given the present, he reportedly (and in his best "hang-on-a-minute-you-can't-trick-me" voice) said "that's not from the baby, babies can't go shopping!"

PS: What's Clinker? That's the nickname that S's work friends gave to her baby-bump!

Tomorrow is a Big Day

Tue, 18 Nov 2008 02:59:39 +0100

Every one of us experiences life-changing events. Sometimes we're fortunate enough to know about them in advance. One such event will come tomorrow for my wife and I, with the scheduled arrival of our second child! All going well, I'll make an update here with news (and I'm veejoe on Twitter, so look out there for progress too).

Scourges of the Universe: Blog Spam, and ISPs

Sun, 09 Nov 2008 20:12:25 +0100

If you can read this, it means that Round 3 of my fight with my ISP is over and my ADSL is back up, which is a good thing because it means that I can tell you about why my ClustrMaps image has so many red dots on it suddenly...

Every so often I found that some random junk would show up in comments to my blog posts. When I saw it I'd just delete it, and it didn't occur often so I didn't really think much of it.

This was until I spied a comment that I actually needed to reply to, and found I couldn't. I started looking at why the record number of the comment was so high, and found that my blog of little-more than 100 entries had become home to over 13000 items of blog-spam. :(

I blame myself, obviously, as the software I use had introduced spam-filtering techniques a couple of versions ago and I hadn't kept up.

In cleaning up the garbage, behind the red mist of rage I saw at having my blog being violated so, I noted something interesting. The issue had been going on for some time, and I realised that in front of me, in my humble little blog, I had a snapshot of the evolution of blog-spam.

The early stuff was primitive, and easily identified by querying for the names of erectile dysfunction drugs and other medications. The later stuff was harder and harder to detect until I was virtually picking it record-by-record out of the database. Some of it made absolutely no point to me at all: strings of random alphabetics with not even a URL in sight; maybe this was a worm just looking for the kudos of a DOS.

The thought occurred to me that perhaps I should have kept it, in much the same way as someone I know keeps copies of PC viruses and worms in a little (hopefully isolated) folder. Then I realised two things:

* Preserving something, or putting it in a museum, gives it some legitimacy. I don't want to legitimise blog-spam; and
* The art (if any) in blog-spam is in the code that generates it, not in the crap it leaves behind.

As for all the hits on my ClustrMap, I figure 80% are the spambots infecting the blog and about 19% are the poor folk that got drawn to my site as a result of the spam. I had been thinking of a different blog platform, perhaps this episode shows that I need something a little harder.

Of course another way to fight blog-spam is to get your network disconnected from the 'Net, and my ever-so-unfriendly ISP went out of their way to do that for me this weekend. Unsolicited, of course, which is even better. On a Friday afternoon, too -- better still, as if you do actually manage to get someone on the phone it's too late for them to find anyone who can do anything about it (apparently).

Recommendations of a good ADSL ISP accepted: although keep it to yourself if your ISP's called wwkjukhkkjlpuggh or qjkdfsdfaksjkulkfhg... :)

Sometimes, Gentoo bites

Thu, 30 Oct 2008 02:51:01 +0100

I had a failure of my Cacti system over the weekend, entirely caused by bad Gentoo emerges. Two different problems, both caused by bad upgrades of packages brought in from ~amd64 or ~x86, made Cacti colourfully dysfunctional for a couple of days.

The first was an update to the spine resource poller, part of the Cacti project but installed separately (it used to be called cactid). Turns out that somewhere between 0.8.7a and 0.8.7b, bugs were introduced that made spine unreliable on 64-bit systems. The update brought in a SVN version of spine which, while still labelled 0.8.7a, must have been somewhere after one or more of the bugs came in. The symptom was that every data value obtained via SNMP was garbage and ignored.

The second issue was strange -- graphs were getting generated (even those for which there was no data) but there was no text on them! Titles, margins, legend, axes, all were blank. Some posts pointed to a problem accessing the TTF font file provided with rrdtool, but the actual problem turned out to be the upgrade to rrdtool 1.2.28 which introduced different parameters for the configuration of text attributes in graphs -- and a corresponding "feature" that suppressed any text output if the new parameters were missing.

So what does "~" have to do with this? The software on your system is built according to the architecture of your machine. In Gentoo, this is called your "arch" (for architecture) and is usually "x86" or "amd64". Gentoo implements a "testing branch" in an arch which starts with "~"; if a pre-release version of a package exists in portage you can bring it in with the "~x86" keyword. The nice thing about this is that you don't have to enable a testing repository across your whole system -- you can enable the ~ keyword for specific packages on your system, and everything else stays stable.

Unfortunately, this flexibility has a cost. The "amd64" arch seems to lag a bit behind "x86" in terms of packages being marked stable or just simply having packages available. This means that just to get things installed, it's necessary to flag packages with "x86", "~amd64" or even "~x86". This flagging is easily done -- almost too easy in fact, as it creates a problem later on when the package you actually set the keyword for eventually becomes stable and you don't need the keyword set any more. It's a manual process to revisit the keywords you've set and verify that they are still needed (and you know how well manual processes work).

Some time ago I started adding comments to the Portage config file where keywords are set, trying to explain why I set the flag: "to bring in version 1.2.34" for example. That way, if I ever do get around to manually auditing the package.keywords file, I'll be able to check if some of the keywords are still needed. Still a manual review though.

So in the case of rrdtool and spine, I had set the "~" keyword some time in the past for some reason, possibly to get early access to a bug-fix ebuild. With no established method to revisit the keywords, I continued to pull in unstable versions of packages long after the packages I really needed had been marked stable. Eventually, it bit me.

The pre- and post-upgrade chacklist grows some more... :)

Heading home from Singapore

Sat, 20 Sep 2008 02:12:55 +0100

So here I am in the Qantas lounge at Changi Airport after my the last day of my trip to Singapore. The education went well (lots of smiling farewells) and I've forged some links with the locals that I hope will be fruitful for all.

I'm trying to get over the silly habit I've developed of bringing home stacks of coins from overseas, and it looks like I've had a bit of success this time. Somehow I've managed to come home with almost no coins! I brought a stack of coins I had collected on previous trips, and not only have I got rid of all them I've collected hardly any more.

I indulged my gadget addiction to the tune of an Archos 605 Wi-Fi media player. Yes, I know that there is a new series of devices released by Archos, but they are not generally available and may not be for a while (in this geography at least). Besides, the 605 has what I need (especially since the supplier over here includes the key plugins that I need) and is available now. The store recently reduced the price too -- admittedly, probably to clear stock in advance of the new models coming in a few months.

Here's hoping I get some sleep on the plane, as I want to have a good day with N and S before I have to do the Canberra thing all over again.

Short trip to Singapore

Tue, 16 Sep 2008 01:33:28 +0100

This week I'm in Singapore, running a training course on z/VM and Linux on System z. I really enjoy coming here! This is the first time I've done any kind of work here, and I'm enjoying fitting into the daily commute in another city!

The weather here is, obviously, hot and humid. It's been far from unbearable though, in fact I'd almost say it's comfortable (which is quite something from someone who usually can't stand hot weather). I've rediscovered the transport system, the excellent MRT train system with its regular services and its cheap fares, and I'm using it to go to and from work.

I'll make some further notes as the week goes on. Wish me luck with the training!

On being an early-adopter

Tue, 02 Sep 2008 03:19:39 +0100

I like new things. Many of my friends and colleagues do as well. Some of us are very familiar with "early adopter tax", the high price of paying for a new release product or program in spite of the knowledge that delaying the purchase would save money. I got to thinking about early-adoption a little while ago, and came to somewhat of an epiphany: nothing to do with shiny gadgets or cool software, either...

Some months ago I was in an IRC channel with a group of folks in the team I was working with at the time. The conversation had come around to green electricity, what deals our respective electricity companies were offering, and whether we were "doing the right thing" and selecting green energy.

I was a nay-sayer. "It's a scam," I railed. "Why should I pay extra for green power when the electricity companies know they should be doing that anyway?" The conversation turned to subsidies for installing solar power systems, and soon after that we actually got back to work. :)

Months later I recalled that conversation while listening to a podcast. The presenter was discussing climate change and the need for urgent action, whatever the cost. Which is when it hit me: green energy and it's friends are like an early-adopter tax for a sustainable future.

In the early 90s, I remember models of the IBM ThinkPad would cost A$12k and more. Twelve THOUSAND dollars! Over time however, the developments in the technology have led to such remarkable improvements that a modern laptop can be had for a fraction of that amount, and projects like OLPC becoming viable. None of it wold have happened, however, if early-adopters had not backed the IBMs, Compaqs, and Toshibas (and the Osbornes before that, bless them) and supported the idea.

In 1978, when Mercedes-Benz first fitted ABS to the S-Class[1], I expect they would have wanted to make it at least an option on all their vehicles. That they didn't, when the cost of doing so would have been astronomical, ensured that they were able to viably continue research and development on the technology and bring the cost down over time. Together with other car makers who progressively did the same, they ensured that even a modern $10k car can have access to such technology, but again it wouldn't have happened if not for those S-Class buyers validating the idea and stumping-up the cash.

I've realised that businesses don't have a conscience, and that the current economic model cannot reward a company for "knowing what it should be doing". In quite a real way, companies need their customers to be their conscience by supporting those products that make a contribution to society, and rejecting products that are damaging or harmful. Longer-term, those companies that "get it" will thrive while those that don't will fail.

So my consideration on things like green electricity changed to, simply, "can we afford to?". Knowing that in around three months I'll be meeting my second child (all going well), and becoming maudlin about the state of the world that a new person is being brought into (as new parents sometimes are wont to do), perhaps the question should be "can we afford NOT to?"...

[1] Other manufacturers fitted ABS systems to cars earlier than 1978, but they seemed to be one-off decisions that were inconsistently implemented or met with commercial failure. Mercedes-Benz, once the decision was made, stuck with it.

Umbrellas like Canberra

Sun, 31 Aug 2008 01:16:48 +0100

Or at least the ones bought there do. In my travels to Canberra I've now bought two compact travel umbrellas and lost *both* of them within a week of purchase. Seems like an umbrella bought in Canberra really wants to stay in Canberra -- the last one lost was liberated by someone who sought to relieve me of a burden at the x-ray screening at Canberra Airport. To that someone, if you're reading: I'd rather have kept the umbrella, thanks, and you could have asked me before you liberated it from me...

New gadget: Nokia E71

Sat, 23 Aug 2008 03:45:53 +0100

I have been in the mobile phone market on-and-off for nearly 12 months. There wasn't really anything wrong with the N70, I guess I was just getting a little fidgety with lots of new "shiny" going around. The trip to the US in May, and seeing an iPhone in person for the first time, probably didn't help, nor (obviously) did the local release of iPhone 3G. Once I'd talked myself out of getting an iPhone though, the itch was still there... and I must say it's being well-and-truly scratched by the E71.

I've had this phone for just on a week now, and it's certainly one of the best phone purchases I've ever made. In a nutshell, the key things about it are:

* QWERTY keyboard, in a form factor not much larger than the N70. Importantly, it's much smaller than the E61 that preceded it (now there's a phone that was just MADE of ugly). Despite it's size the keyboard is amazingly easy to type on, although I may have to update this after I give my thumbnails a trim.

* Symbian OS. Maybe I'm biased, as the owner of a Psion 5, but to me Symbian has an edge over other phone OSes. Not only with the functions in the handset and Nokia's Series 60 interface, but the range of third-party apps for Symbian (or Series 60 specifically) is great. Almost straight after charging the battery I downloaded PuTTY (SSH client) and "vejotp" (S/Key one-time-password utility). Plus, the recent news that Nokia intends to open-source Symbian is a great thing.

* Nokia Maps and A-GPS. While the iPhone glitterati download the entire UBD or Melways every time they walk down the street thanks to Google Maps, I get quick GPS mapping for zero download (the last few times I've used it, the download counter has stayed stuck on "0.0kb" even though A-GPS is supposed to cost a bit of data every startup). It's not the most accurate GPS ever made, for sure, but it'll do me for now at least.

* Built-in podcast support. I was getting more and more frustrated with the way that Amarok and iPod fought with each other over my podcasts. It never seemed to work as well as it did on iTunes! Now, I can use the device I download the podcasts with to listen to them as well. It's self-contained, tidy (no more podcasts mixed in with the music library and causing havoc), elegant.

* Wi-fi capability and SIP client. Being able to connect to the home network obviously means that I can do things like update my podcasts without having to second-mortgage the house to pay for HSDPA data. The SIP client is very cool too: I've connected it to my Asterisk box, and now have a cordless home phone and mobile in one device.

* Solid construction. It's got to be the most sturdy-feeling phone I've ever owned. The case is metal, and it has a nice weight to it. The buttons feel solid, almost like real keyboard keys.

* Drop-dead gorgeous. I got the grey version, the metal casing looks like titanium and has a glossy finish (which is a little prone to fingerprints, but cleans easily). The screen is just amazing, usable in daylight, bright and colourful and incredibly high resolution.

I'll mention more as time goes on, but for now I am very happy!

Canberra

Sat, 23 Aug 2008 02:08:49 +0100

I've been extremely slack at blogging recently. It's ironic that what has been keeping me from blogging has probably been the very thing that I could be blogging plenty about: the constant travel to Canberra. I'm planning on writing a bit more about my experiences of and in our nation's capital, so for now here is the first edition.

I've been doing the three-day-per-week thing now for nearly two months and it's fair to say that I'm over it. :) It's not the weather so much: okay, it's cold, but at the moment I'm breezing in and out so I don't have to live with it. It's not the loneliness; I've been working at home (and away) for long enough that solitude doesn't bother me at all. I have a bit of an idea of things it might be, though...

* The inconsistency of accommodation: one week I'll be staying five-plus stars, the next I'll be in a little fleabag place with barely adequate heating and hundred-year-old floors (which is quite a feat when the city itself has only been there eighty years[1]). One week I'll have a kitchen and be making myself healthy meals, the next I'll be eating lukewarm takeaway noodles using toothbrush handles as chopsticks.

* Trying to do the right thing by work by saving money: this has me riding my motorbike to the airport at 5am to save a night's accommodation and a couple of taxi fares. I'm DEFINITELY over that.

* Separation from N: Although he's coping really well now (much better than me, I think), it worries me that I'll be one of those absent fathers that ends up having only a passing influence on the lives of their children. A bit dramatic, sure, as this is not meant to last for long, but how long is too long? How long is long enough to do damage? It seems like I do little else but spend time with N when I get back, which is probably making things worse.

* Separation from S: I think we've changed. We used to do the living-apart thing really well (when I was working in Melbourne and Auckland, we really seemed to be living proof that "absence makes the heart grow fonder"), but now things are different. She is looking after N, and is in full-time work, so she has a lot more on her plate than before, and I barely get wound-down from one trip than I'm having to gear up for the next.

* Not being able to "connect" with the place: When I have worked away from home in the past, I went to special effort to do things that would familiarise me with the locality. In Melbourne I went on tram rides "just because", and in Auckland I'd ride my motorbike here and there. Day trips, intended to not only help me know my way around but to give me a feel for where my career had sent me. With Canberra, however, these work trips have never been across weekends and I've not had any opportunity to do my "connecting". If not for a colleague of mine who was living in Canberra about eight years ago, and whom I visited one weekend while I was working in Melbourne, I would never have visited places like the Australian War Memorial, Parliament House, Mt Stromlo Observatory, and the comms tower on Black Mountain. After all the visits I've made I've never seen the National Gallery, The Royal Australian Mint, and the dozens of other things worth visiting.

However, probably the number-one thing that's getting to me:

* Having little (nothing) to do when I get there: I'm a technical person, and I feel most useful doing technical things. From that perspective, there is no need for me to be in Canberra to do what I'm doing. My presence there at the moment is merely a perception thing, building trust and a relationship; intangible things that probably are tremendously significant to the client and their perceptions, but don't register with me at all.

I mentioned how well N is coping with me being away: he's doing so well that I'm in awe. It seems like he's keeping me sane. He got upset the first couple of times, but now he almost packs my bag for me! I took him to preschool the other day and this is the conversation that took place:

I said "now, Mummy's going to come and get you this afternoon, mate."

"Why?" said N.

Oh great, I thought, I almost made it without mentioning anything. "Well I'm going on the plane this afternoon," I said.

"Are you going to Sydney, or Canberra?" he asked. I was taken-aback: no tears, no don't-go-daddy-I-need-you...

"Canberra," I told him, "back to Canberra."

"Oh, okay Daddy," said N, "have a good trip. Bye!", and off he ran to play with his friends.

Four. Years. Old. :-D

So on Canberra... I think I've worked out which are the roads not to be on when I need to get from place to place (not having to spend much time in, near, or passing through Civic helps in that regard). I used to take a drive around after work at least once a trip (the closest I've been able to come to my "connecting"), but I've stopped doing that now as I think I've been to most of the districts. I have a bit of an idea what are the good food places, and which restaurants one can go to (as a male person dining alone) without ending up feeling like a total outcast.

Next update I might talk a bit more about the places I work and stay. Don't expect anything too soon, though, as I have about 18 more months in which to do it...

[1] Okay, my little joke. The floors obviously aren't a hundred years old. They do, however, sound like they belong on the sound-stage of a cinematic re-enactment of the voyage of the First Fleet. :)

Motion Computing Tablet PC

Wed, 13 Aug 2008 03:06:24 +0100

Thanks to work, I am now the possessor of a rather cool piece of kit: a tablet PC. It's a Mobile Computing LE1700, and I'm quite impressed with how it works. The big question though is of course... Will it run Linux?

At the moment it's still running Windows XP Tablet Edition, but that's only because a Hardy Heron install DVD is quite some way away from me right now.

I just trained Microsoft speech recognition and this paragraph has been dictated using speech recognition. The recognition rate is actually quite good for the amount of training I've done, although I am having to go back and correct quite a few minor errors.

Back to handwriting recognition, which is outstanding: it's only just now, as I write on the screen of this device, that I realise how poor my handwriting has become! Almost certainly this is due to lack of practice and under-use! I can tell as I'm writing that its recognition is somewhat dictionary-based, as if I pause or lift the pen it will make a guess abort what I've written which it will change as I complete the word.

Credit where credit is due, I think tablet Windows looks pretty good. Having used it before just putting Ubuntu on, I'll be expecting a bit more from Linux...

On the hardware side, the machine looks quite sturdy and solid -- so much so it's a bit or the weighty side. I did install the additional battery pack though, and I'm sure that if I was adopting a proper tablet-PC posture it wouldn't feel as heavy as it does. It has a 3G modem built-in, which works fine with my Telstra USIM (that's how I'm posting this now), and the usual complement of Wi-Fi, Bluetooth, PC-Card, SD and infra-red. It even has a place to stow the pen-stylus.

As I said, I don't have a Linux disc handy to start setting up properly so the big Linux question will have to wait for a while. Some early Googling shows that there is support for most of the hardware components in it (the digitiser is Wacom, the Wi-Fi is Intel 3945, I've even seen support for the 3G adapter. It's the interface and application level that I'm worried about -- the state of handwriting recognition, whether XRandR lives up to the promise, and so on. I'll post more as I get used to it and see what it can do...

Laptop hard disk replacement, part two

Sun, 22 Jun 2008 21:18:32 +0100

Way back in May I had a hard disk in my laptop fail, and after the warranty replacement disk showed up it took me a few days to get around to doing the replace. It didn't get off to a very good start though...

In the past when I've done this kind of recovery I copied the details of the partition table and copied each partition in turn off the failed drive. This time however in my haste (or something) I imaged the entire 80GB in a single file by using dd pointing at the disk device node (/dev/sda, say) instead of each partition.

When it came to restore, this brought me undone. I tried the reverse of what I'd done to create the image, just dd to the disk device node, but at around the point where the first partition would have ended it failed with an I/O error.

Assuming that I did actually have a valid image of the entire drive, I needed to find a utility that would treat a disk file as an image of an entire drive, partition table and all. Then, theoretically, I could copy each partition out of the source file in the same way I was used to.

As usual, the lazyweb came through for me. I found a beaut utility called kpartx, apparently part of multipath-tools. I also found some blog posts describing how to use the tool for what I needed. What kpartx does by itself is scan a block device or normal file (significant, as I'm sure when I first used it I had to use losetup) and create device-mapper mappings to the partitions it finds. kpartx was just what I needed!

This blog post describes the process I went through (and no losetup here either). For me, I let kpartx create device-mapper nodes for the partitions in the disk image, and then used dd to copy from each of those partitions to the real partitions in the new disk (carefully created using fdisk to match the originals). Then I set up grub on the new disk, and installed it into the laptop. It worked first go!

So now on its third hard drive, this Sony Vaio (same one with the weird wireless issue in Hardy) gets yet another lease on life. The battery is almost expired though, so I think it won't be long before it goes to the Old Hardware Shelf...

Edit: I realised my confusion about losetup. kpartx uses losetup under the covers if it detects that you're trying to work on a disk file instead of a block device. When you use the -a or -l switches to kpartx, if it needs to it straps up a loop device for you and automatically works on that; running kpartx with the -d removes not only the device-mapper nodes but the loopback node as well.

Don't you hate it when defaults change?

Sun, 22 Jun 2008 20:29:42 +0100

Sometimes when working with computers and networks (as with most things in life) the thing that causes the most problem is the last thing you suspect--or often something you never suspected. I had a reminder of this the other day, when a moderately complex task I'd set myself looked to be scuppered for absolutely no reason I could fathom.

I've got a system here that is a host for a virtualisation environment I run. I dedicated a couple of network cables to the adapters owned by the virtualised system, and a third one was attached to the host's IP stack. To get connectivity for another system, I had to steal the host's cable though--which wasn't a problem as the operation of the system works more-or-less entirely from the console rather than over the network. Just for grins, however, I decided to set up connectivity to the host by routing through the virtualised environment it hosts.

Having established the tunnel connection between the virtualiser and the host stack, I set about configuring the special details required to support routing through this system. After a few tries at getting it right, I was rewarded with successful pings between the systems on my LAN and the hosts system on its routed connection. So I jumped onto the console of the machine and light up Firefox, but got an error page. I realised I hadn't set DNS resolution--on the LAN, the machine was having resolv.conf configured by DHCP, so now I had to do it manually.

Okay, so DNS resolver now correctly set, let's see Firefox WIN! Oh. Fail.

When I hit Try Again or Reload, the page would instantly refresh. This was starting to look like no routing problem. I used dig to test name resolution, and it told me it was being rejected. I looked at my dns.conf... Nope, so subnet restrictions coded there...

So I hit the lazyweb, and it didn't take too long before I found a forum post that led me to this. In BIND 9.4.1-P1, ISC basically changed the default behaviour of a couple of query filtering settings. This had the effect of rejecting some requests that were previously accepted, such as those from non-local subnets. A reconfiguration of my DNS server gave me success at last.

Hooray for persistence! Now, someone hand me some Cat-5 so I can make a cable and plug this thing back in properly. :)

Ubuntu 8.04 Wireless Weirdness

Wed, 18 Jun 2008 01:10:23 +0100

Over the last fortnight I finally got the wriggle-on to upgrade all my (K)Ubuntu systems to Hardy Heron. Various issues occurred with each of them, but overall the entire exercise went smoothly (my wife's little old Fujitsu Lifebook was probably smoothest of the lot). I had one rather vexing issue however, on my old (I'm tempted to say "ancient") Vaio laptop.

The onboard wireless on this thing is an ipw2100, hence only 802.11b, and I had a PCMCIA 802.11g NIC lying around (actually it came from the Lifebook, liberated from there after I bought it a Mini-PCI 802.11g card on eBay). On Gutsy, I used the hardware kill-switch to disable the onboard adapter to make double-sure that it wouldn't try and drag the network down to 11Mbps.

This laptop was the last machine I upgraded to Hardy, and I was playing with KDE 4 on it so I was looking forward to seeing what KDE4-ness made it into Hardy. While the upgrade was taking place the wi-fi connection dropped out, but I didn't think anything of it since Ubuntu upgrades try and restart the new versions of things and I figured NetworkManager had fallen and couldn't get up. After the reboot, however, KNetworkManager (still the KDE3 version, don't get me started there) could find no networks -- could find no adapters, in fact.

I logged back into KDE3 and poked. Still no wireless (as if the desktop would make a difference, but I had to make *some* start on pruning the fault tree). The Hardware Drivers Manager was reporting that the Atheros driver was active (for the PCMCIA card), and an unplug-plug cycle generated all kinds of good kernel messages.

On a whim, I flicked the hardware kill-switch for the onboard wifi[1]. Almost instantly, KNetworkManager prompted to get my wallet unlocked -- it had found my network and wanted the WPA passphrase. I provided it, and got a connection: via the PCMCIA NIC.

"That's odd", I thought, and flicked the switch. A few seconds passed, and the link dropped. Flicked the switch on, link came back. Flicked the switch off again: this time a few minutes went past, but again the link failed. Tried it several times again, and the same thing happened. The state of the kill-switch for the onboard NIC was influencing the other NIC too!

It seems that this is altered behaviour in NetworkManager, applying the state of the hardware switch to all wi-fi adapters. If it annoys me significantly I'd like to think I'll trawl changelogs, or even better lodge something on Launchpad... more likely though I'll forget all about it having found a kludgy workaround.

I've now added ipw2100 to the module blacklist and things work okay (presumably because the state of the onboard switch can't be reported any more). I'll also have a think about whether a few dollars for another g-capable Mini-PCI NIC will be throwing good money after bad, as this laptop really is quite long-in-the-tooth.

Oh yes, that's right... KDE 4. Next time perhaps. :-)

[1] I can't think why I did this. I knew that I'd disabled 802.11b in my access point, to make triple-sure an 802.11b device wouldn't slow my network down... The onboard 802.11b NIC would never successfully get a connection.

Whither Twitter

Tue, 17 Jun 2008 01:54:09 +0100

I really don't use Twitter much at all. It's one of those things, like Facebook, that I just signed up to more-or-less on a whim. But with all the stability and performance problems they've been having recently (and the flak they've been taking in the press, I understand) I'm hoping that they pull through. You have to wonder though, when their Status Blog gets a post entitled "Odd whales"...

Odd whales



We're seeing a number of whales pop up around the site, especially on profile pages. We're aware of the issue and working on it now.



Update: site back up and mostly whale free.

Bizarre -- but maybe if I was a more regular user it would make more sense. ;-)

Unfortunately my visibility of their problems started when they shut off their IM functionality -- unfortunate because at around the same time I had done an upgrade of my Jabber server and blamed the upgrade for not being able to connect to Twitter. Hours of fruitless config checking and Googling finally led me to the aforementioned Twitter Status Blog and the news that IM had been disabled. Ever since then (two or three weeks ago) IM function has been the "number one priority to get restored"...

I'm not complaining. It's a service I barely use, and one I've never paid for. I can appreciate people getting upset however; as someone who does have trouble keeping in touch with friends and family, if I had gotten more used to it I'm sure I'd be one of those complaining.

Doom-and-gloom time... Part of the flak Twitter has been copping is around the design of their systems (virtually no redundancy or scalability) -- if this is systemic to Web 2.0 startups and the investors and venture-capitalists catch on, things could get ugly FAST. Are we set for a repeat of Dot-Bomb? Could Twitter be the first victim of an impending burst of the Web 2.0 bubble?

I hope it comes back. Twitter is a nice way to see what folks are doing, and it's a reminder of the fact that there are people out there. :) Perhaps I'll even make a bit more use of it, if it can get its IM groove back on. Good luck folks, and watch out for the whales...

Annoying cliche of the week

Thu, 12 Jun 2008 21:29:26 +0100

If I see or hear one more reference to something being a "perfect storm" I think I'm going to be sick.

Slack blogger

Thu, 05 Jun 2008 19:33:36 +0100

It doesn't take much to see just how rubbish I am at this blogging thing. The last few months have been full of interesting happenings, and the blog has been silent. I'm not going to embarrass myself by saying "I'll do more frequent updates, really I will" because I know it won't happen. Oh well, as appears in the gospel according to Dirty Harry, chapter Magnum Force, "A man's got to know his limitations". :)

USA travel!

Mon, 12 May 2008 21:47:27 +0100

I'm in the US right now, for a work conference and some meetings. It's been an interesting trip already: a non-eventful flight over (when I was expecting it to be really bad having not flown economy to the US before, yes I know I'm spoilt), and a fascinating and very enjoyable tour of Los Angeles yesterday with a local limo driver. The technical program of the conference starts tomorrow, and it looks like a very intensive programme. More details as they happen!

Edit: Technically I have flown economy to the United States: when Susan and I went to Hawaii we were on economy. I should have said that I haven't flown economy to the mainland US before. Or maybe I shouldn't have said anything... ;) Anyway, it was far-and-away the longest economy class flight I've ever done and I must say it wasn't anywhere near as bad as I was imagining it.

Zeroshell redux

Sun, 04 May 2008 04:08:59 +0100

I wrote about Zeroshell, and how I thought it was pretty great. I still do, but it hasn't taken centre-stage in my network configuration like I thought it would. I've had to tone down my raves about some of its integrated features as well.

The fact that it hasn't taken centre-stage is possibly as much to do with VMware's bogus clock-drift problems as anything, as I haven't dedicated hardware to my Zeroshell instance yet (I could keep it running virtual, but some of the things I want to do with it will make more sense if it's a separate machine). VMware Server takes another barb for its handling of VLAN tagging (but to be fair that might be the Linux 8021q module works). It seems that if you have any VLAN definitions on a network card, VMware won't get to see any VLAN tags on that NIC. You can get a guest attached to a bridged interface to see the real VLAN tags, but only if Linux has not got any VLAN awareness over that NIC.

Alright, so enough ragging on VMware. I have Zeroshell attached to the networks it needs and all is fine. Except that I can't actually change anything! The web interface that I spoke so highly of originally is actually very restricted in some areas. One of these is in the RADIUS server, and it bit me badly when I decided I'd use Zeroshell's RADIUS server to authenticate access to the Web interface of my Linksys switch. Turns out that the Linksys firmware expects a particular attribute to appear in the response from the RADIUS server.

The fact that Linksys don't document this anywhere is not Zeroshell's fault, but that there is no interface allowing me to do updates to the records above what Zeroshell uses for its own applications is a bit of an issue. It means that instead of a Zeroshell box potentially becoming the hub of administration functions, it is in danger of becoming just another little vertical application server that doesn't integrate.

Having said that, the backend for most (all?) authentication data is LDAP so a tool like PHPLDAPAdmin might be usable to extend the base records. But, arguably, I shouldn't have to do that! It is still beta software though, so improvements and enhancements will be made.

The other area that it's a bit lacking in is monitoring/graphing. Okay sure, I'd probably integrate Zeroshell into the rest of my Cacti setup, but it would be nice if Zeroshell did like other router distos and had a pre-built statistics/graphing page.

Zeroshell is still my pick (I revisited pfSense and fixed the problem updating, but to me it doesn't have enough function to justify running its own hardware), but it's just not quite the bees-knees it was when I first saw it.

When Upgrades Go Wrong

Sun, 04 May 2008 03:14:33 +0100

I'm running Debian on a Linksys NSLU2 storage device, and it works really well in general. So well in fact that a lot of the time I forget the thing is even there! It's sitting in the garage minding its own business, serving out video and music files, and storing backups of the other systems in the house. Just occasionally, however, the thought pops into my head to run a system update over it -- a habit I've gotten into for the Gentoo systems in the house, but "the Slug" usually misses out. About a fortnight ago however I decided to do the "apt-get shuffle". Timing, as they say in sport and comedy, is everything.

I've become fairly complacent about system updates. All the distros I use now have got excellent tools for keeping everything up-to-date, and for making sure that things don't go wrong in the process. It's all just software, however, and it's all too easy for something to get missed or for a bug to creep in. One such bug that did exactly that is this one. Unreported at the time I did my update, it rendered my Slug unbootable after the update I gave it.

It took me a day to realise that the Slug was off the network. The failure of the nightly backups was my first clue. Next was the inability to stream any of the media files stored on it. For the next week, on-and-off, I tried a dozen things in an attempt to get it working again. I finally arrived at a process that used the Debian Installer firmware image as a way to get a running system onto the device, allowing me to then access the hard disk and try and reflash earlier kernel and initrd images to it.

I started trying to work on the boot disk, but I couldn't see it for some reason. Then I discovered that the power supply of the USB2 disk enclosure that holds it was playing up! Now, I had two problems--was one related to the other? Was my boot problem just a hard disk problem all along? Turns out that the power supply failure was a coincidence--replacing the power supply got the disk working again but made no improvement in the bootup scenario.

The NSLU2 boots differently to a PC. On a PC, the BIOS locates some boot code on a storage device and executes that, which usually is a program like LILO or GRUB that has more intelligence and (in the case of GRUB) a way to interact with it. These boot loader programs then load in the kernel and start executing it. With the NSLU2, however, the kernel and the "initial root device" are written into the flash memory of the device--they more-or-less are the BIOS.

On a PC, if there's a problem with the kernel or initrd you can generally select another one from a list. Worst-case would have you installing the hard-disk in a different PC and fixing the problem from there. On a NSLU2, however, any problem with the kernel or initrd can't be fixed by changing the hard disk because the kernel and initrd aren't read from the hard disk but from the flash memory instead. There's also no option for selecting another kernel, since the NSLU2 is a "headless" device with no console (besides, there'd be no room in the flash memory for two copies of kernel and initrd).

Once I'd been able to get my Slug booting (by writing out a previous version of a kernel and initrd) I was going to leave it alone... but curiosity got the better of me. I'd suspected a bad update to the utility that generates the initrd, and sure enough an "apt-get update && apt-get upgrade" revealed a pending update to the initramfs-tools package. Google led me then to the above bug report. With fingers crossed I did the update, reflashed, and rebooted... successfully!

The Slug is now back in its usual place, quietly going about its business of entertaining us and keeping critical data safe. I might at least think twice before doing a kernel update on the poor beast in future though!

Laptop hard disk replacement, part one

Sat, 03 May 2008 22:17:40 +0100

A couple of weeks ago I had bootup problems with my old Sony laptop. I had replaced the hard disk in it last year (February), and everything was pointing to another busted hard disk. First time I'd had a machine outlive two hard disks! :(

Sure enough, I put a different disk in the laptop and it worked, and the original disk in a USB caddy failed (but only after working successfully a couple of times, leading me to think it was a transient problem and reassemble the laptop, at which point it failed again... sigh).

Through persistence and determination (and a couple of goes in the freezer) I managed to get a copy of the disk onto another drive. I then went shopping, but decided to check the warranty on the dud drive: lo-and-behold, it still had nearly four years of a five year warranty to run. Better yet, unlike the Western Digital I had to send at my own cost to Singapore for replacement, Seagate have an address in Australia that can be used.

Sod it, I said, anything more than the original 80GB (since for less than what I paid for the 80GB a year ago I'm looking at 160GB or more!) is wasted on this particular machine, so I completed the RMA, found a box to pack the drive in, and sent it off.

The address in Australia is a mail forwarder to Seagate in Singapore. I had to keep that in mind when I checked their order status page, which a week later was still showing "awaiting your return". Nevertheless, it wasn't long before the page changed to "shipped". Looking a bit closer I could see that my 80GB drive must have put on a bit of weight on the way to its birthplace, as Seagate was sending me a 100GB drive in return!

Having left Singapore last Thursday the drive arrived on Monday, but due to work commitments (plus having to fix the Slug first) I wasn't able to do anything with it until today. Stay tuned for the recovery exercise...

Zeroshell: network services distro

Sat, 12 Apr 2008 02:36:28 +0100

I love it when, almost by chance, I find something new. I decided yesterday to look at FLOSS-based router distributions. I've been using IPCop for a while, as an easy way to create a VPN to another location. Unfortunately, IPCop failed my latest requirement: 802.1Q VLAN support. So I went surfing and found an absolute ripper in Zeroshell, but I didn't find him straight away...

First I found pfSense, a FreeBSD-based distro that seemed to fit the bill--indeed the very first question the Live-CD asked me on bootup was "do you want to use VLANs?". It also promised a very extensive set of additional packages that extend it's capability into areas like file/print, WWW proxying, and a host of other features. However, even though it has a very nice web-based configuration facility, due to what looks like a problem on their web site I was unable to even look at what packages are available. Since some of the basic function I would like is provided by these packages, I've had to move on--but pfSense gets an honourable mention because of its easy installation and excellent configuration interface.

I looked again at Smoothwall, but soon remembered why I discounted it at the time I chose IPCop. For me, the level of function I think I'd use is a bit too close to the threshold of function in the "community" (read, "free") version. Astaro would go in this category too, except that I was too dense to be able to even find much clear information about the level of function you get in their community version. So no recommendation on either of these, as I've never used either--I do work with a fellow who happily uses Smoothwall though.

Then, I came across Zeroshell. The lead developer describes it as "a small Linux distribution for servers and embedded devices aimed at providing the main network services a LAN requires". And does it ever! It's a veritable Alladin's Cave of features and functions. It certainly does everything I was looking for, from VLAN tagging through QoS to VPNs, from an SPI firewall to multi-zone DNS and multi-subnet DHCP servers, but also has Certificate Management (using a self-signed CA certificate or one you import), a RADIUS server, WiFi access-point capability with multiple SSID and VLAN mapping, captive portal or "normal" HTTP proxying, 802.1d bridging, clients for Dynamic DNS, a Kerberos 5 server, plus a raft of other capabilities. Zeroshell--named because the author wanted to provide a system that was extremely flexible and powerful yet did not require users to access a shell prompt--is remarkably feature rich, and yet the download for the ISO image is only around 100MB (a bit beefier than pfSense, admittedly, which weighed in at around 60MB).

There are a couple of downsides, however. Until very recently, installing to a hard disk was not supported. The distro is designed to boot from a CD only, but can use an installed hard disk (if available) for what it calls "databases", where configuration and other data is kept. With the latest release, however, the developers have created a "1GB USB drive" download (the size of the download isn't 1GB), which is designed to be copied to a USB pendrive or hard disk.

The other downside (and it's not fair to say that, as will become clear) is the web interface. Not because it's ugly or not functional: it is neither of those. It's clean and well laid out, and fairly consistent. It's very technical, however. Where other distros tackle the "SOHO divide" by hiding details such as protocol numbers or port ranges, Zeroshell uncovers all this stuff in its gory detail. So it's great for someone like me, who looks at the interfaces on other systems and pines for the knobs I can't fiddle with, but it's not for newcomers.

It looks to be a fairly new project (current release is 1.0beta9), but the forums look good and there does seem to be a bit of activity around it. I'm running Zeroshell in a VMware guest at the moment while I kick the tyres--the VMware download is also available from the project's mirrors--but I reckon this one will be a keeper!

ORDB: "If I go down, I'll bring you down with me"

Tue, 01 Apr 2008 04:34:56 +0100

Okay, I'm sure it's not really like that. I'm ashamed to admit this one bit me, though: ORDB, which 16 months ago called it quits but has still been online and more-or-less functional, decided last week to false-positive all queries (a mailing list thread on the issue can be seen here. Harsh, but fair--I do stuff-all email through this site but it still has been costing someone bandwidth to bounce my silly queries back to me. Multiply that up by all the part-time-sysadmins like me that don't pay close-enough attention, follow old wiki articles, or get bad advice, and pretty soon you're talking about a HEAP of bandwidth wasted to NOT provide a service any more. Shame it had to end like this though.

MythTV fun and games

Tue, 01 Apr 2008 03:56:51 +0100

Bad things don't always come in threes. For my MythTV setup, four bad things all happened at once. First was that the governments of the Australian states that run Daylight Savings Time (DST) decided to jump on the energy-saving bandwagon and change the end-time for DST this year. Second was that the OzTivo folks changed the API for connecting to their program guide data, and closed the old API interface on the same weekend that DST was originally due to finish. Third, for some reason that I'm still investigating, my run-an-emerge-world-at-least-every-fortnight MythTV backend had an old timezone-data package, so any times it handled that should have still been DST weren't. Fourth, Shepherd isn't quite as smart as I thought it was, and I didn't find out until too late...

Let me get something straight: Shepherd is the bees-knees of EPG grabbers for Australian MythTV users. If you're a MythTV user in .au and not running Shepherd, stop reading this right now and go and update your system to use it--you'll be glad you did. If I had just looked at some of the output it has been generating since OzTivo announced it's changes, most of the agro I've suffered the last few hours would have been avoided.

In a nutshell, Shepherd is a "meta-grabber". It includes code that can get program data from a dozen or so sources, and keeps looking up sources until it fills your listings with data goodness. It automatically updates these individual source grabbers as well, so you should never need to worry about its up-to-date-ness (more on that later though). It also fetches extra program data from IMDB and TVDB, and can even automatically grab station icons for you. Highly, highly recommended.

I could see that some of my EPG data was coming from OzTivo because I had seen the notes that they had put in the program data advising of the API change. The weird thing I saw was that for a program I was recording in the same timeslot each day, sometimes the message would be there and other times not. While I thought that this was a little strange, I figured that the OzTivo folks were just being overly cautious and trusted Shepherd to do all the updates it needed.

Then, ever since Sunday morning when the southern states *didn't* switch back from DST, I've had recording times out by an hour--programs trying to record an hour early. So as I mentioned, I had ye-olde timezone data on the backend, which can't have helped depending on the data source (although I'm trying to work out if this actually is a contributor as I would have thought it would send the recordings an hour late... plus, others who have confirmed their timezone data have had the same problems). For a couple of programs, I actually had double entries: one an hour too early, then a second one at the right time. This was weird, and I still can't explain it!

A manual run of mythfilldatabase showed why I was getting the repeated OzTivo API messages. Shepherd had downloaded the updated grabber alright, but the new version has a Perl dependency that wasn't satisfied and it couldn't run. Rather than bail out, Shepherd elected just to keep running with the old grabber. Given the circumstances, I'm still deciding how I feel about that. :-\

So once I was confident that the grabbers were working okay again, I decided to get the EPG straight. I remembered that mythfilldatabase will not replace any existing data it thinks is valid, which is why only data post-April-5-or-so looked nice again. So, with a mailing list post or two as encouragement, I truncated (database-admin-speak for "deleted all the data from") the "program" and "programrating" fields in the mythconverg database and ran mythfilldatabase. After about 20 minutes, voila, fixed guide data!

So now I'm thinking of how I can alert myself to a problem with Shepherd. I used to just check the result of the last mythfilldatabase run through Information Centre or mythweb, but since Shepherd ends cleanly so does mythfilldatabase. Looks like I might have to come up with something hackish to look for Perl runtime errors in the mythfilldatabase log and do a Nagios passive service check or something... Sigh, as if I needed another little project to keep me busy... :)

SLES, you make it so hard to like you

Fri, 14 Mar 2008 17:45:26 +0100

Just wended my way through another SLES 10 install on s390x. It's b0rked though, and I'll probably have to redo it. I had some kind of I/O error during the install which seems to have resulted in a couple of the filesystems being remounted read-only. Not too much trouble you'd think...

Some things aren't starting because of missing binaries in /usr, frustrating but probably recoverable. The network startup is totally clagged though, and I can't even begin to work out how what happened... happened.

During bootup, at the time it tries to configure the network interface, I get streams of error messages about problems running the "ip" command. The error text is full of garbage that the init script is trying to parse as text configuration--it looks like a corrupted filesystem or a binary file.

I manually configured the network (not a trivial task in s390x, it must be said), and started to poke around. I got this when I logged in as root:

Last login: Sat Mar 15 12:48:36 2008
/usr/X11R6/bin/xauth: error while loading shared libraries: libXau.so.6: cannot open shared object file: No such file or directory
-bash: read: read error: 0: Is a directory
lxs0za01:~ #

Okay, so I won't get funky X-based YaST.  No problem, I've spent more time in the ncurses-mode YaST anyway...

lxs0za01:~ # yast
warning: the ncurses frontend is installed but does not work
You need to install yast2-ncurses to use the YaST2 text mode interface
lxs0za01:~ #

WHAT!!! What the @#!$ happened there?!?!?

Okay, so I've calmed down about that, so I go looking for the problem with the network initialisation...

lxs0za01:~ # cd /etc/sysconfig/network
lxs0za01:/etc/sysconfig/network # ls -go ifcfg*
-rw-r--r-- 1   141 2006-06-17 07:30 ifcfg-lo
lrwxrwxrwx 1    16 2008-03-15 02:23 ifcfg-qeth-bus-ccw-0.0.0f00 -> /lib64/ld-2.4.so
-rw-r--r-- 1 27470 2006-06-17 07:30 ifcfg.template
lxs0za01:/etc/sysconfig/network #

Priceless. You can't make this stuff up. I cannot for the life of me work out how this could possibly have happened. I guess I just blame it on a whacked-out filesystem and move along.

Okay, so both of these issues probably have extenuating circumstances unrelated to SLES or YaST... but it's nice to have a vent now and then. I'll write up something a bit fairer once I fix this b0rkedness. :)

Are we letting Microsoft define our industry?

Mon, 10 Mar 2008 02:28:26 +0100

I've been trying to solve a problem at work for a few weeks now -- one of those tricky "it's only software so it shouldn't be this hard" sort-of problems for which you know the solution is just a matter of putting the right bits and pieces together. At work, I'm more-or-less forced into using Red Hat Enterprise Linux (the distro formerly known as RHEL), and one of the pieces I'm looking at is OpenLDAP.

My first stage in the process was to get OpenLDAP set up with the right config -- but when I started it, slapd complained about an error in slapd.conf. The overlay I was trying to use, it claimed, was not found. I spent the next couple of hours trying to find additional packages, trying different things, reading doco, searching Google, to no avail. The overlay I want is missing from Red Hat's build of OpenLDAP.

So "boo hoo", you say, "just build from source". Well, remember how I said I was forced into RHEL? The corollary to that is that I am only allowed to use exactly what the Shadowman ships on the DVD. No build-from-source, no other OSS, is allowed.

But what does any of this have to do with Microsoft?

In my research, I found the release notes for Red Hat Enterprise Linux 5. In it was the following text (highlighting mine): OpenLDAP Server and Red Hat Directory Server Red Hat Directory Server is an LDAP-based server that centralizes enterprise and network data into an OS-independent, network-based registry. It is set to replace OpenLDAP server components, which will be deprecated after Red Hat Enterprise Linux 5. For more information about Red Hat Directory Server, refer to http://www.redhat.com/software/rha/directory/.

You guessed it: Red Hat Directory Server is a pay-for product. So Red Hat's setting a direction here: server platforms comprising only the base OS, and additional function provided through extra-cost modules -- now where have we seen this before?

Does this now mean that on RHEL-next, in order to run a Samba server with an LDAP IDMAP backend, companies will have to pay for RDS? That won't fly at my work: "we already have a corporate directory, we're not paying for another" will the customer sayeth.

"Okay", you say, "so don't use Red Hat". As far as I'm allowed (this is at my employer remember) the only other choice is SLES... from Novell... that organisation that felt the need to cross-licence with Microsoft to "protect" against undisclosed and unproven patent infringement.

(Note that this post is not about Novell-Microsoft, nor is their deal a reason not to use SLES in my opinion. The thought only popped into my head because I was already thinking about Microsoft as a result of the Red Hat thing with RDS.)

So it seems like the two biggest names in corporate Linux are marching to Microsoft's drum. Have I misread something? Am I overreacting?

New job

Sun, 09 Mar 2008 21:09:22 +0100

Well it's official now -- or at least, my current boss announced it to the team, so that more-or-less makes it official. :) I will be starting a new job in about a month's time -- still at the same shop, but no longer in Services. I'll be with the team that does technical pre-sales in the System z arena. Lots of talking with customers, lots of designing and building and planning, a bit of travel, and lots of nerves to start with as I get used to a totally different work mindset. I'm looking forward to it!

The events leading up to it becoming official were what led to the first installment of the Fractured Fable. Now that the issues have been resolved, the mood has changed so it'll be tough to maintain the energy for Part Two. :)

Thinking of a Gentoo desktop

Mon, 03 Mar 2008 03:51:36 +0100

I know I'm going to cop a beating on the Planet for this post, but here goes... For a long time I ran a desktop system built on Gentoo Linux. A while back I tried Ubuntu, and I've been running that as my desktop ever since. Every now and then, though, I feel an inclination to pop back to Gentoo -- usually it will be because of some package I want to be able to install, or later versions of packages that don't make it into the usual binary-distro world without introducing "dependency hell" (I'm having this problem at work, with a distro based on RHEL 5.1 and hardware that's just too new for it... Even if I wanted to build drivers from source, the libraries the drivers link against are too old as supplied, meaning I'd have to rebuild the libraries too, which probably means something else will be too old...).

I run Gentoo on both my "servers" at home. At the time I got my dual-Opteron, Gentoo was the only "free" distro around that had a x86_64 version ready to roll. When it came time to build my phone-and-TV server, it got Gentoo as well because it was the only way I could get the right combination of all the versions of code (Apache, PHP, Asterisk, MySQL, MythTV, ccxstream, etc) that I needed and have them all maintained in the distribution's package management system (Debian has no ccxstream package, for instance). I don't run Gentoo because I'm a ricer. Portage has the right package mix for me, and its ability to control the configuration of packages through USE flags gives me an opportunity to control the options that are enabled in the packages I install.

I have blogged previously about some hardware I bought that I haven't been able to put to good use. I decided to give it another try by building a Gentoo system on it, because an ebuild for the bleeding-edge ATI driver that is supposed to support the graphics chipset in this clunker is in Portage.

Let me say, it's been a while since I built a Gentoo system from scratch. You don't even do it truly from scratch anymore either -- the days of starting with a stage-1 tarball are over apparently, and stage-3 is always the way to go. Even so, this system took a whole weekend to get to the stage where I could log on and get a KDE desktop (to be fair though, there was a lot of kicking off an emerge, coming back to it a couple of hours later to find it had died ten minutes in, fixing the issue and restarting... so it wasn't 48 hours solid time spent).

Unfortunately the ATI driver still doesn't support XVideo on this chipset, so I still can't use this board for its intended use as a MythTV frontend (I do have an old PCI nVidia 5200 card that, even though it's at least three years old, I'm sure will run rings around this stinking ATI 1250). So the point of the whole exercise was, unfortunately, lost. But I did get a refresher in the amount of effort a Gentoo build would take.

After that weekend's effort, I was a bit put off by the thought of building up an entire desktop system from scratch. When I thought about it though, my concerns were for nothing. The compiling? The kind of systems I'm building on (modern dual-core chips) will chew through compiling most software in a snap -- heck, for simple packages I can install on a Gentoo system quicker than yumex can initialise its repositories. I've got running systems I can use as a model to get USE flags right, and my NFS-shared Portage tree means that I sync once and use everywhere (even downloading source packages happens only once).

Plus, now, I know Gentoo. Sure, APT on a Debian-based distro is nice, but I still am lost when it comes to the right dpkg command to locate what package provides a certain file, for instance. I get frustrated when something fails to build on Gentoo because some other package wasn't built with the right USE flag, but I know how to fix that, and its fixed in a flash. Likewise for rebuilding some system library that causes a bunch of other packages to fail without warning, and likewise for the strange b0rkedness that happens in Portage sometimes when packages change versions (gnupg is a recent example). I know how to fix Gentoo when it breaks -- I can't say that with much confidence for other distros.

Some might say "use a distro that doesn't break in the first place", which is a fair comment. But if I have to choose between an occasional hiccup and missing functionality, then hand me the Eno (Pepto-Bismol, Tums, etc)... ;)

Which brings me to my dilemma -- apart from the fact that I have crappy unaccelerated non-video graphics and I haven't been able to run Compiz for ages (a problem that Gentoo wouldn't solve for me anyway), Ubuntu isn't really broken for me. There's not a compelling reason for me to throw Gutsy out, and with Hardy around the corner there's even less reason to switch right now.

So, I'll wait. And watch. Having to work on more Red Hat systems at work is reacquainting me with their particular mojo, perhaps even enough to try Fedora. Also, I've just scraped together some parts to make an openSUSE 10.3 build for something work-related so I'll catch up with things there (since I haven't really seen a SUSE system as a desktop since SuSE Linux 7).

I love this about Linux -- freedom to choose!

Happy Birthday Nicholas!

Mon, 03 Mar 2008 00:26:03 +0100

Our not-so-little guy turned four today! He had a McDonalds party on Saturday, with a few of his best mates from day-care in attendance. Today he took a cake to day-care for everyone to share (and he had great fun taking it around the playground to show everyone when he arrived!). The only low point was when we popped in to the doctor for his immunisations -- but he was so brave! Not a tear, not even for the second of two needles! We eased whatever grief there may have been with a trip to the pizza shop for dinner. Best wishes little man, and lots of love from Mum and me!

A Fractured Fable, Part One

Fri, 29 Feb 2008 14:48:44 +0100

"Once upon a time, in a land far from here, there was a clothing factory. One part of this clothing factory made uniforms. The uniforms came in many shapes and sizes: some were sporting team outfits, some were "corporate wardrobe", others were emergency services uniforms... but they all looked alike. Few of the people working in the factory spent any time actually making uniforms -- more time was spent on things like adding or removing badges and insignia and players' names from the uniforms, or completing reports to state that the holes in customers' uniforms were appropriately mended (whether or not any such holes actually existed)...

"Sometimes the sleeves would fall off, and the pockets would be on the back instead of the front (or on the front instead of the back), and when this would happen and the customers complained the managers of the factory would make lots of noise and implement more procedures and promise the customers it wouldn't happen again. The factory workers would have to complete more reports, spending more time on the reports and still less time making uniforms.

"Many of the factory workers were unhappy, and dreamed of getting back to making uniforms instead of writing reports and sewing badges. Others dreamed of designing uniforms. Still others dreamed of moving to a different part of the factory, where suits or pyjamas or swimming togs or wedding dresses were made without the need for any of the strict rules that the managers said were required when making uniforms..."

Part Two coming soon...

Telstra service

Fri, 01 Feb 2008 00:08:17 +0100

I have to say that over the last couple of years I have only had good dealings with Telstra. Ironically though, the most recent example is about the only service I have with them, and they want to take it away. You see ISDN is outdated technology that is holding Telstra back from delivering new services, and they want me to replace my ISDN line with shiny new analogue phone lines. So says a letter I received late last year...

I have a service that Telstra calls "ISDN Home Highway". Its original purpose was to give "broadband" Internet connectivity to places that were unable to get ADSL, but it was still a normal ISDN basic-rate phone service with a special NTU that included a modem (serial and USB attached) for data connectivity. Data calls to Bigpond (Telstra's ISP division) were subsidised, and local phone calls were cheaper as well (AU$0.175 instead of the "normal" AU$0.25). The best bit though was actually the price: by the time you option up a normal PSTN line from Telstra with caller-id and other stuff you're looking at something like AU$40 per month -- Home Highway was AU$45 per month which includes both B-channels and two DIDs (so basically the equivalent of two phone lines, ISDN standard, for only a fraction more than one analogue line).

Like I said though, Telstra sent a letter last year advising that they were removing the ISDN Home Highway service. There's this thing called "BigPond Broadband ADSL" that I could use instead of my ISDN service, apparently. It seems that they believe that the only reason people got ISDN Home was for Internet access, and now that ADSL is available in more places that ISDN shouldn't be necessary any more.

There are a number of flaws in their reasoning, however, not the least of which is the fact that I had ISDN Home because it's an ISDN voice service! If they had done a bit more homework, they'd know that we already have ADSL -- there's another service coming into the house, an analogue line that is there for the sole purpose of ADSL provision.

My alternatives were looking like replacing the ISDN Home service with an ISDN Business service. From Telstra's point of view, it's non-productive, as it defeats the purpose of them trying to get people off this "legacy" ISDN equipment -- I just switch to a different type of service, forcing them to keep the ISDN gear. It just doesn't make sense. Of course I could also switch to VoIP, but without number portability (yet) it's a pain that I wasn't looking forward to (not only that but my employer currently has a prohibition on work calls going over VoIP).

So why is this a positive dealing with Telstra? Because I got a phone call from a lass from Telstra this morning to ask me about whether I got the letter and how I felt about it. As I described my displeasure, she made attentive noises at me and took notes (well, she said she was taking notes). She said that they've only just started ringing people about it, and that there was a possibility that enough people making comments like mine might force a change.

It's a positive thing right now because it's the first time I've been given the impression that Telstra gives a stuff about a customer. It can't be cheap to have people sitting, calling people, and potentially wearing abuse from people who they intend to displace. I never thought I'd say this, especially after the abhorrent BACk campaign (in which they tried to gain public support to fight against Optus in their bid to change a broadband access environment thet Telstra themselves created), but kudos to Telstra for at least asking the little guy what he thinks.

Let's see if it ends positively though. :)

Internet-grade

Thu, 31 Jan 2008 01:55:49 +0100

It's probably been coined already, and I'm sure it's not a new realisation. Something happened at my employer recently that's made me wonder whether the old benchmark of "enterprise-grade" is really relevant any more.

Our internal IM system was closed down for a while this week, and when it was restarted a number of us could not reconnect. It turns out that the IM servers had been set up to lock this particular client out. Nothing unusual about that really, as it has happened in the past with unsupported clients that stress the servers in unexpected ways.

What was different this time is that the client in question is part of a new "integrated communications" offering -- a version of our e-mail client that has the IM client built-in. This product, which will be sent to-market quite soon (and therefore we will be expecting our customers to buy), has been locked out of our IM infrastructure. The further irony is that the part of the business that markets this software runs a "use what we make" initiative to get people to use development versions of their software in their day-to-day work.

The IM system in question is marketed as enterprise-grade -- and in general it lives up to that, having to support a couple of hundred-thousand users at peak. What got me thinking though is that systems like MSN Messenger (or whatever it's called now) and Yahoo! IM and AOL IM must be supporting millions of connections at a time with nary a blink.

So (if it wasn't already) I'm knocking "enterprise-grade" off the top-spot of reliability rankings. Nowadays, the top spot surely goes to "Internet-grade". I mean, just imagine the amount of traffic that must pour through Google Talk and Skype -- these are systems that not only do text chat but voice and video as well -- while our IM is still struggling with smilies and changing fonts. The trouble, in the case of my employer, is that the name of this IM service is synonymous with the concept of IM there. It doesn't matter that even an open system like Jabber could scale better.

In my opinion, our software people need to take a look at what Google has done in taking XMPP/Jabber and creating Google Talk. Either that or the company needs to do what another prominent software company did and actually use one of the public IM systems (I cant remember which one they use, either YIM or AIM) as the corporate IM platform.

I feel for the developers of the new client, who I'm sure would love to have a stable environment to do a large-scale test on. Oh well.

OpenTTD

Mon, 28 Jan 2008 07:06:20 +0100

So I was catching up on the RSS feeds I subscribe to, and came across an article on the latest issue of Full Circle (a magazine about goings-on around Ubuntu Linux). In it I found an article on OpenTTD, an open-source clone of the old 90's game Transport Tycoon Deluxe. As one who spent many an hour in front of games like Railroad Tycoon in my youth, I had to try it. Unfortunately, I'm hooked...

I've been playing the game all night since I found it on Monday afternoon. Sleep seems a distant priority compared to making sure I snag the subsidy for a passenger service from Podlondlington to Nunmubhattan...

It's easy to install on the Ubuntus, but you do need to obtain the data files from the original CD -- the Full Circle article contains instructions on how to do that (or I'm sure the website tells you).

Sure, the graphics don't measure up to today's insane system-melting specifications and the isometric view, while state-of-the-art in its day, is at times frustrating (I'm sure there was a control you could use to hide the buildings so you could see behind things... maybe I'm thinking of Lincity). Still, it's both a great bit of entertainment and a trip down memory lane at the same time. If you're like me and played with the Tycoon games as a kid, or if you're a bit of a retrogamer, I encourage you to check it out. Don't expect to see much of your family for a while though... :)

Cisco XML apps: things made of fail

Tue, 22 Jan 2008 03:52:07 +0100

Since I have a few Cisco phones around here, I've played with XML apps. I have written a timezone calculator, an LDAP phone directory lookup utility (which hooks into the "external directory" function of the phones), an app that uses Qantas' WAP interface to get flight arrival/departure information, and the obligatory RSS reader. They work, in some cases very well, but the inconsistency of the XML interface between different levels of the Cisco firmware makes it a trying exercise.

My latest exercise was an update to the RSS reader I've used for ages. I found RSS2Cisco ages ago and have used it quite successfully, but I've never really been satisfied with its way of displaying the whole feed in one text page. It works well for news feeds, where all you get is a headline and a teaser, but for things like blogs it's not suitable (you're lucky to get through one posting before hitting the limit of a Cisco XML text page). I wanted an interface like a "normal" RSS reader, where it lists the items in the feed in a menu and you then choose an item to be displayed.

Sounded simple, and wasn't too hard to hack rss2cisco around to make it do my bidding (it's not optimal yet as every time you read an item it pulls down the entire feed again). The problem I faced was in making the thing work consistently between the 7960 phones and the 7970s.

All my phones are running fairly recent SIP code, but for some reason the 7960 has an ancient XML parser. By ancient, I mean that the level of the XML SDK it supports is tied back to Call Manager 3.0. The 7970s, on the other hand, have support for a much more recent SDK and support some of the fancy operations that you can't do on a 7960 unless you're running SCCP firmware. At first I thought that there might have been a hardware limitation and that Cisco couldn't fit the extra smarts of a client for later SDKs, but the SCCP code can't be that much simpler than SIP that they'd have more room to fit a better XML browser and all the other features the SCCP code has over SIP...

So the SIP firmware for 7960 has a junk XML browser. You'd think, then, that the 7970 was easier to work with than the 7960... Wrong! Valid XML that worked quite happily on the 7960 would fail with a cryptic "XML Error[4]: Parse Error" message. It took quite a bit of time and quite a bit of trial-and-error to work out some of the dependencies (32 seems to be a magic number, folks...).

Call Manager XML (CMXML) is supposed to be really simple, but I can only imagine how complex it might get to deliver an app with a consistent interface if you had a number of different phone models to support -- I have only two, and I'm looking at two different versions of my app!

In their defence, Cisco have provided a way for the phone to identify itself and its SDK level when it makes a request. A set of HTTP headers identify the device, and one specifically states the SDK version supported by the phone client. Reading these headers would allow a developer to adjust the output of their app to cater for the various phones -- one app, but multiple output capabilities.

It strikes me though as a heck of a lot of work for limited return. These are phones intended for corporate installations, so it's almost a given that there will be a full-function computer at the same desk. Why would a company invest that much effort developing and supporting an internal application for a single platform that's tied to desks, when they could write it as a web app and deliver it practically anywhere? I'm starting to see why the Internet is not exactly awash with sites selling CMXML apps...

Having said that though, I love my timezone calculator. With three button presses I can find out the time in any of my six favourite timezones, and I can find any timezone in the world with only a few more presses. An application somewhere on the web couldn't be anywhere near that speedy for me, and a desktop app would have to be some kind of widget already running and configured (or be the KDE Clock applet, all it takes is a mouseover... shame I'm stuck with GNOME for my work desktop).

So I'm not too keen to apply much development effort to my XML apps. I will stick them on my development site some time soon, but I don't think it's worth the effort to keep them functional. The Qantas one, for instance, is totally dependent on the URL and query format of the Qantas WAP application, which is obviously subject to change at any time. I wonder sometimes if a WAP-XML gateway would be useful, but then I think about the effort of writing a system to translate pages delivered over a dying protocol to an interface that never got off the ground...

In case you're curious what the RSS reader looks like:

and something a bit more voluminous from my blog:

Yes, I am a bit proud of it, even though it's rubbish... ;)

KDE 4.0: be free.

Fri, 18 Jan 2008 01:37:33 +0100

Since I watch Planet KDE it was easy to get caught up in the excitement around the launch of the new version of KDE (the announcement is here). I was unable to resist giving it a try on the laptop! So this post is coming from Konqueror 4.0.0.

I tried an early Beta of the KDE 4.0 Live CD, but it was still using the KDE3 Kicker and was also a bit unstable. I wasn't sure if it was the fact I was running in a virtual machine that made the graphics a bit flaky or whether it really was beta-quality code making things a bit funny. The KDE team put a lot of effort into bug-swatting in the weeks leading up to 4.0 being tagged, and it's a lot better now!

This announcement from the Kubuntu folk shows how to get the KDE 4 packages installed on Gutsy. KDE 4 installs in a different path to KDE 3, so you can try out KDE 4 without affecting your existing environment.

I did have a bit of a heart-starter with this though, as apt-get wanted to remove a package called "kdebase-bin-kde3", which looked risky! It's okay though, as equivalent binaries are provided by "kdebase-bin-kde4". In fact, if you follow Kubuntu's instructions exactly, you should not see the issue: it happened to me because I did a system update after adding the Kubuntu PPA repository but before installing KDE 4. The system update brought a bunch of updated KDE 3 packages out of the PPA, one of which was to replace the standard "kdebase-bin" package with a "kdebase-bin-kde3".

First impressions are that Oxygen (the new artwork for 4.0) looks great -- it's a very modern look. Some might think it borrows from Vista, but to me it's got as much of Mac OS X's appearance as that of Aero. Plasma (the desktop shell) does some interesting things, like turning desktop icons into widgets, but I'm yet to spend enough time with it to experience the other improvements it brings. The biggest thing I'm looking to trying out is the compositing built into the window manager, KWin. Unfortunately the laptop is a bit old for this to work well (or at all in fact), so I'll either have to find some magic Xorg setting or get the KDE 4 packages on the desktop machine. I've had trouble running Beryl and Compiz thanks to something about the terminal program Yakuake tickling a long-lived bug in X11 (I think part of the reason it's long-lived is that the X11 folks don't accept it as a bug but rather a fringe case that Yakuake shouldn't be exercising, hence a stand-off) so it will be interesting to see if KWin has the same kind of issue.

As for bugs, well there look like plenty. :) As I'm keying this, Konqueror is chewing 100% CPU and the characters are delayed by a couple of seconds (and of course, now that I observe this, it stops doing it). Still with Konqueror, this is about the third time I've tried to post this thanks to Konqueror segfaulting for strange reasons. Also, the Alt-F2 program launcher reports that it was unable to launch whatever you told it to, even though it does so successfully.

There has been plenty written by the KDE folks about the "1.0.0 release of KDE 4", and they're copping a fair amount of stick from people who think they've done the wrong thing by releasing as 4.0.0. I'm on KDE's side. Although many KDE folks have used their KDE 4 builds as their daily desktop for months, I haven't seen anyone who wears a KDE hat recommending that others do so. The term "will eat your children" has been used to describe KDE 4 by folks from the KDE team, so there has never been any pretense that KDE 4.0.0 would be a daily desktop for the majority of users. I've never really participated in large-scale software development, but I can see their motivation for releasing what they had as 4.0.0 -- I'm proof of it. As long as it was a beta I was not really all that fussed about trying it out; even after there were release candidates I wasn't all that keen. As soon as you call it a release, however, your early-adopters rush in and kick the tyres and your real testing can start.

By being open about 4.0.0's status (and I don't think you can get more open than "will eat your children"), they can make sure that subsequent releases are a lot better than they would be if they dragged on in perpetual beta -- the model that Google and the Web 2.0 fraternity seem to insist is better, plodding on for months hiding behind beta status and its implicit "get out of jail free" card.

Instead, KDE has shown the courage to take their code, along with its bugs, and hold it up as something they are proud to give to the world. It's the foundation not only for future releases of KDE, but possibly the start of new ways that people work with their computers. By working with the community, instead of closeted away from it, I believe the KDE team will succeed.

Okay, so that finished a bit more ra-ra than I planned! Seriously, give KDE 4.0 a try... but if you aren't happy to suffer a few bugs then by all means wait until 4.0.1 or even 4.1. Oh, and be free. :)

Jabber and Google: part two

Sun, 13 Jan 2008 05:08:44 +0100

In part one I mentioned how I was considering using Google Talk as my main chat ID. As it turns out, I talked myself out of it pretty quickly after I delved into using Google Talk to connect to MSN and other services as I do now with my own Jabber server. While there are a lot of links around for using Jabber transports to hook your Google Talk ID to other services, there's a tiny catch... well, actually, I think it's a bloody great huge catch personally.

You see, it wasn't until I read the how-tos that it became clear how it works. The trick is that Google doesn't run Jabber transports on their own servers, so you therefore need to take advantage of various "open" Jabber servers that do ("open" in this context refers to a server that lets you use its transports without necessarily being a registered user there).

Seeing there didn't seem to be any restrictions on the servers that could be used, I figured that I could use my own server. Sure enough, after the right incantations to expose the service on the 'net, I could connect my Google Talk ID through the Jabber-MSN transport on my server to my MSN account. Yay, right? Well, not really -- each little test message I sent in either direction incurred three trips over my Internet connection! Yes, three: one to go from my Google Talk client to Google, one back from Google to the transport on my Jabber server, then a third from the transport to MSN. Obviously the same happens in reverse as well (for incoming messages from MSN).

Seeing this as a less than optimum setup, and also being wary of getting listed as a Google Talk-friendly Jabber transport provider, I lopped the transport's external visibility and went back to using my own JID for transport access. It's a bit of a shame too; since fring (mentioned briefly in my last post) doesn't let me connect to an arbitrary Jabber server, to keep connected to everything I'd need two mobile chat programs running.

It's not like I do that much IM that I need to keep all this running, but it is at least a little bit interesting... :)

Which Nokia device to get?

Mon, 07 Jan 2008 03:47:37 +0100

I've developed a very strong desire to be connected to people recently. In the last fortnight I've reawakened my Google account and regularly sit on Google Talk, reawakened an old Free World Dialup account and plugged it into my home phone system, and signed up to Twitter. I also found a mobile IM and SIP client called fring that looks good and works really nicely. I'd love to use fring constantly, thanks to its integration to Twitter and Google Talk (heck, it might even make me find my old Skype ID) but...

My current phone is a Nokia N70, which has served me well for a couple of years, but I'm not keen to use it too much for fring because I don't have a mobile data plan (and my phone company charges fairly steeply for casual data). Besides, it's only UMTS 3G so the data rate is not great (better than GSM data, but only occasionally so). What I really need is one of the newer devices around that has Wi-Fi built in. Something like the N80, new N82 or E51, or N95. That way I could use fring at home (which is where I am most of the time nowadays) and not have to worry about data costs.

Thinking about spending that kind of money though (again, my phone company is happy to talk to me about upgrading my handset, but the kind of plan I'd have to go onto to get a phone like that would be insane) makes me wonder about other devices. Something like the N800, or even a new N810. I don't think fring is available on Nokia's tablet devices, but with the alternate OS platform on the N8x0 I could install just about any kind of IM client I want. Plus I'd have a nice device to web-surf, program MythTV, check mail, and various other tasks.

What about other devices? The Asus EeePC has tweaked my curiosity, but I think it would end up being just a bit too large to fit in with the kind of usage I'm imagining for this type of device. Blackberry is a bit scary to me, it doesn't really seem to be a general-usage consumer-oriented device (more a corporate connect-back-to-the-proprietary-box-in-the-server-room kind-of thing). The iPod touch is out as well: it's closed nature would frustrate the heck out of me (it's got a browser, but you can't load anything on it...). The only other manufacturer I'd think about for a mobile device right now is Sony-Ericsson: Ericsson manufactured a couple of the nicest phones I've ever owned, but Sony has ruined them for me. I'm just not interested in getting back onto the hardware-to-lock-users-to-the-Sony-tower treadmill.

It's all just navel-gazing, unfortunately. Realistically, I can't justify dropping a wad of money on some new shiny just to satisfy what is probably just a bit of a personal fad. I think I'll wait a bit longer and see how quickly the newly-released N95-8GB drops in price, or how far it pushes the price of the old N95 down -- ditto the N810 and N800.

Oh, and I'll wait for fring to fix my biggest issue: no support for Jabber. Queries on their forum on this have gone unanswered for almost a year. Technically it can't be a big leap for them, as they have support for Google Talk!

Jabber and Google, part one

Mon, 07 Jan 2008 02:44:21 +0100

I reactivated an idle Google account the other day. A friend of mine from the Netherlands invited me ages ago but I never really did anything with it until I discovered that a Google Mail account can be used for other Google stuff as well, including Google Talk. I read that Google Talk is based on Jabber and works with any Jabber client, so I flicked over to Kopete and plugged in the details. Sure enough it worked... but then it got interesting.

I run a Jabber server for internal things. I wanted to have a secure, private chat facility to use over VPN with my nephews; I want to someday migrate my Nagios IRC bot to Jabber; and I use transports to link into MSN and Yahoo! to reach friends on those networks. The last point is great: I really like the fact that now, from whatever Jabber client I use (even the mobile ones I've played with) that I merely connect to my Jabber server and I'm online on MSN and Yahoo! as well.

Google Talk, though, has proven to be a bit of a challenge. It's actually working like a tower, even though it's based on (arguably) the most open of the IM platforms! You see I more-or-less took for granted that "transport" way of doing things, using my Jabber server to bridge to other networks. There's no Jabber transport for Jabber though!

What I want to do kind-of flies in the face of how Jabber is designed. Ideally, you're supposed to only have one Jabber ID (JID) -- Jabber creates an open network with servers establishing connections when needed, very much like e-mail, and you only need an ID on one server to be able to chat with anyone on any other server. So what I wanted to do, which was connect to one Jabber server and have it "relay" messages to an ID on a different server is just not necessary with Jabber. Nor should it be necessary for Google Talk users to send messages to me using my Google Talk ID only -- they can send straight to my JID on my Jabber server.

In the early days of Google Talk, Google had not enabled the "server-to-server" functionality that allowed this kind of communication to happen. Google Talk worked just like MSN, Yahoo! or AIM -- you had to have a Google Talk account to chat with anyone on Google Talk. While this was the case, folks were looking making a Jabber-Jabber transport for connecting Jabber servers to Google Talk. At some point, though, Google opened the connectivity paths that allowed Google Talk to exist on the open Jabber network (I've tested this for myself). Once this happened, the need for a "Google Talk Transport" for Jabber evaporated in most people's minds.

The solution nowadays is to use a client that supports multiple connections, and connect to your Jabber and Google Talk accounts at the same time. It works of course, but you don't get the nice benefits that a transport provides -- the main one being access to all your IM services and accounts from a single server connection.

So now, having resigned myself to not being able to bring my home JID and Google Talk ID together, the question arose: do I still need my own Jabber server? My current fave mobile IM client only connects to Google Talk... Could I get by just using the Google Talk service? Find out in Part two! :)

Gentoo + jabberd = aargh

Wed, 02 Jan 2008 03:33:30 +0100

I've been running jabberd2 from ~x86 for ages. Tonight I went to make some config changes, and stopped and started jabberd using the init script like usual. Things were different though, as the init script didn't shut down all the Jabber tasks and I had to stop them manually. When I went to restart it, only two processes were shown and not all the separate processes I was used to.

Nothing was being logged either, as I was trying to find out what was going on and why the processes weren't starting. It was as if it was suddenly ignoring all my configuration files!

Careful inspection of some output from eix showed the problem: Jabberd 2 has been moved to its own ebuild (jabberd2), and the highest version in the jabberd ebuild is now a 1.4.4-something. Not only that, they've hard-masked jabberd2:

# Krzysiek Pawlik  (08 Oct 2007)
# Masked untill the split from net-im/jabberd is complete.
# See bug #178055 and bug #195091
net-im/jabberd2

Looks like the last time I emerged I downgraded my Jabberd 2 to 1.4. No wonder the thing was not responding to me.

This is the kind of thing that happens on Gentoo from time-to-time. It's why I started a regular sync of portage and email-output-of-emerge-pretend-world process: so that I didn't get too far behind and have a heap of these things to sort out. This one got me off guard though.

Note to self: pay closer attention to emerge output in future!