Tungsten Update

Reg­u­lar read­ers will remem­ber that I got a Tung­sten T2 last year. It worked fine, except for one prob­lem — the digit­izer kept drift­ing, and I had to recal­ib­rate it every couple of days. Even­tu­ally the screen star­ted to cycle con­tinu­ously on an inter­mit­tent basis. I tried the tips on the Palm web site, which did­n’t fix the prob­lem. So, since it was still with­in the one year war­ranty peri­od, I called Palm support.

I had to fax in cop­ies of my pur­chase receipts (note to self: be glad you prin­ted those out!) and call back a couple of days later when they had the inform­a­tion attached to my file. Then I spoke to a tech­ni­cian, told him I’d tried the tips on the web site, and the rest was rel­at­ively pain­less (apart from the $30 it cost to ship the old one to Ontario from Van­couver). A week later (I chose the slow ship­ping option, which is why it was *only* $30), I had a brand-new Tung­sten T3, which actu­ally seems a lot bet­ter. Full kudos to Palm for stick­ing to their word and repla­cing the defect­ive Tung­sten without quibbles, and with a bet­ter ver­sion as well! I’ve got so used to incom­pet­ence in the cus­tom­er ser­vice world that it’s a refresh­ing change to meet a com­pany that does­n’t settle for that.

XML FAQs

The XML FAQ is one of those web sites that those who’ve been doing XML for a while tend to for­get about, until asked to explain some piece of XML that causes large volumes of dis­course on xml-dev (such as wheth­er to use ele­ments or attrib­utes). Then it comes in really handy to be able to point people at the care­fully col­lec­ted pearls (in this case, at D. 3 Which should I use in my DTD, attrib­utes or ele­ments?) and even remind your­self of them.

Which is why it’s good that Peter Flynn, who has main­tained the XML FAQ for some years, has revamped the site, and made it easi­er to find what you need (or just to browse, mut­ter­ing “that’s inter­est­ing” to your­self on a reg­u­lar basis as you dis­cov­er some new fact­oid). Thanks!

OpenSolaris

Well, it’s out. OpenSol­ar­is, that is. I thought it would be fun to indulge in a little fake his­tor­ic­al writ­ing (or dream­ing, some of it really out there)…

Even the people in the middle of it all, those who came up with the idea of mak­ing Sol­ar­is open source, those who came up with the idea of launch­ing a major ini­ti­at­ive by blog­ging, did­n’t real­ise what an impact this would have on the world. Even now, 5 years later, we’re still dis­cov­er­ing nuances, still dis­cuss­ing wheth­er this product or that sys­tem could even have been con­tem­plated without the boost provided by the OpenSol­ar­is initiative.

So what was so new about this? Two things spring imme­di­ately to mind. This was the first time a major oper­at­ing sys­tem had moved from closed-source to open source. A num­ber of organ­iz­a­tions had made such a leap in the years imme­di­ately pri­or to OpenSol­ar­is, not­ably the Moz­illa Found­a­tion (which cre­ated the Fire­fox browser) but those were all applic­a­tions. Linux (the main oth­er open source oper­at­ing sys­tem) was open source from the begin­ning. The oth­er was the launch-by-blog­ging. Sun Microsys­tems was one of the first major com­pan­ies to truly embrace blog­ging by any employ­ee as a means not only to get inter­est­ing inform­a­tion out there, but to build com­munity, and we can now see (and this was inten­ded at the time) the blog­ging launch of OpenSol­ar­is as being a nat­ur­al part of that com­munity-build­ing pro­cess. The 132 Sun engin­eers who wrote 215 000 words to launch OpenSol­ar­is was seen as a dis­ap­point­ment at the time by some, as a tri­umph by oth­ers. It was clear that this was only the begin­ning of what would become a wave of launch-by-blog­ging mar­ket­ing that was copied widely and is a stand­ard part of any product launch today.

What was not expec­ted was the sheer speed at which non-Sun developers took the oppor­tun­ity to cre­ate end-user applic­a­tions. Up until the launch, Sol­ar­is was con­sidered a cor­por­ate oper­at­ing sys­tem. Sol­id, secure, but noth­ing fancy that would tempt a con­sumer to switch. There were few applic­a­tions cre­ated by third party developers; sev­er­al hard-work­ing cor­por­ate applic­a­tions but little of interest to oth­ers. But by the end of 2005 there was an explo­sion of applic­a­tions, some duplic­at­ing sim­il­ar work on the Linux plat­forms such as new desktops and ports of vari­ous pop­u­lar applic­a­tions, and some that were tailored to the OpenSol­ar­is oper­at­ing sys­tem, tak­ing advant­age of fea­tures that were not avail­able else­where. OpenSol­ar­is became the slash­dot­ter oper­at­ing sys­tem of choice, and reports star­ted com­ing in of com­pan­ies being deluged with requests to port their applic­a­tions to OpenSolaris. 

Now, 5 years after that fate­ful day, we see OpenSol­ar­is being used as the base of gam­ing con­soles, bank sys­tems, even mobile phones! Oth­er oper­at­ing sys­tem developers and vendors were inspired to improve their offer­ings, and the sta­bil­ity and secur­ity of all oper­at­ing sys­tems has increased to the stage where teen­agers don’t under­stand adult jokes about blue screens.

Ok, now back to real­ity. I use Sol­ar­is on my laptop so some of the above is my dream — more choice in Sol­ar­is-based oper­at­ing sys­tems and desktops (the Sol­ar­is equi­val­ent of Ubuntu, for example) and in applic­a­tions. There are lots of applic­a­tions avail­able for Linux (Skype, for example) that could be por­ted to Sol­ar­is with (I assume) rel­at­ively small effort. The basic things do work — brows­ing, edit­ing office doc­u­ments, email. I can even use punchin (though not in con­junc­tion with my Debi­an fire­wall, since I need to set up ipsec tables and that requires updat­ing to sarge, then recom­pil­ing the ker­nel, then fig­ur­ing out the magic incant­a­tions. If any­one is using punchin on a Sol­ar­is box behind a Debi­an fire­wall and has hints on the best way to tackle this, please let me know!). I like using Sol­ar­is, it feels sol­id and stable and although it’s been a long time since I worked on a Unix-based sys­tem, so I have to refresh my memory on how to do a lot of things, it’s good to have the choice.

Comment Spam

Any­one else notice a flood (well, trickle) of com­ment spams? They are com­ments of the form “great site”, “glad I found this site” etc, i.e., all mind­less com­ments that could apply to any site, with senders that are poker or online gambling sites. Some­how they’re get­ting past Spam Karma 2 (which nor­mally catches all the spam), so I’m hav­ing to delete them by hand. It’s not as it I have a par­tic­u­larly pop­u­lar site either!

Upgrading WP

Last week I upgraded the blog soft­ware to Word­Press 1.5.1 from 1.5. Here­with a few notes for oth­ers plan­ning to do this.

The upgrade was mostly unevent­ful, with only two prob­lems of any note, under­scor­ing that you really should deac­tiv­ate any plu­gins you have before start­ing the upgrade process:

  • BAStats does­n’t work, as it appears some of the func­tions it calls have been rearranged into dif­fer­ent files. The author seems to be think­ing of releas­ing a new ver­sion at some stage, so for the time being I’ve just turned it off. 
  • The feeds were empty, but search­ing on the WP sup­port for­um came up with a patch (update: no longer avail­able, or needed) which fixed the problem.

Of course, now the Word­Press team have released 1.5.1.1, which includes that bug-fix, so I just spent the last 10 minutes (lit­er­ally) installing that. The 10 minutes includes back­ing up the com­plete data­base, deac­tiv­at­ing all the plu­gins, installing, react­iv­at­ing the plu­gins, and check­ing the results.

All in all a rel­at­ively pain­less upgrade. I gath­er there are a lot of secur­ity fixes, which alone make the upgrade worth­while, and it also meant I could install Spam Karma 2, which is a big improve­ment over the pre­vi­ous ver­sion, both in being able to get rid of old com­ment spam and not have it clut­ter­ing up your data­base, and in its fil­ter­ing abil­it­ies. Both of these factors made upgrad­ing worth­while. Now I just have to find the time to write more!