May 9 2009

The ABC have a piece from National Lib­rary of Aus­tralia web archiv­ing man­ager Paul Koerbin, about the import­ance of digital records pre­ser­va­tion.

Of equal import­ance, how can we be sure that we can actu­ally read those archives in the future? Lit­er­acy of Egyp­tian Hiero­glyphs was long-​​gone by the 18th cen­tury, and it took the dis­cov­ery of the Rosetta Stone for them to start mak­ing sense again.

It’s dif­fi­cult enough deci­pher­ing human lan­guage. Under­stand­ing machine lan­guage is another thing entirely.

I’ve writ­ten about this in the past, con­trast­ing the thousand-​​year-​​old Domes­day Book (which is still legible) with the BBC Domes­day Pro­ject (which was rendered vir­tu­ally unread­able a mere six­teen years after production).

The means of pre­serving our cul­ture for digital pre­ser­va­tion is to use open stand­ards. If the means for ‘read­ing’ the inform­a­tion is widely doc­u­mented and under­stood, without any encum­brances, we stand a much greater chance of being able to inter­pret it in a couple of hun­dred years.

I’ve got essays from school writ­ten only ten years ago, and I can’t read them any more as they’re stored in a pro­pri­et­ary file format that is no longer supported.

Ima­gine you ran a com­pany that had import­ant and valu­able writ­ten records stretch­ing back for dec­ades. Stor­ing vast lib­rar­ies of paper is expens­ive and inef­fi­cient, so you decide to digit­ise them all. That’s great — you now have a sys­tem that is easy to man­age and search. Ten years later, you want to migrate your now-​​ageing data man­age­ment sys­tem to some­thing more mod­ern. Only, you can’t — it’s all stored in a pro­pri­et­ary format that can­not be accessed by any­thing else.

If you had kept those paper records, you would have still had access to that inform­a­tion. Your choices now are to con­tinue with your old, obsol­ete sys­tem for all etern­ity, or hire some clever hacker to decipher the file format. With no equi­val­ent of a Rosetta Stone, that’s no mean task. After spend­ing buck­ets of money on this avoid­able prob­lem, and los­ing even more due to inef­fi­cien­cies and com­pet­it­ive dis­ad­vant­age from the old sys­tem, you’d be wise to make sure it can­not hap­pen again.

This is a very com­mon kind of scen­ario. If our inform­a­tion can’t even last ten years, how can it last a thousand?

From a busi­ness per­spect­ive, open stand­ards pro­tect the inde­pend­ence of a com­pany. It means no vendor lock-​​in, so you are not stuck pay­ing mono­poly prices. Through the cre­ation of a free mar­ket sur­round­ing a method/​technology, open stand­ards give you the free­dom to select the vendors, products, meth­ods and tech­no­lo­gies that suit your require­ments best, or you can even cre­ate your own. They are the ulti­mate in risk mit­ig­a­tion, and through their flex­ib­il­ity can also open aven­ues for com­pet­it­ive advant­age. They just make good busi­ness sense.

LotD: Vioxx maker Merck and Co drew up doc­tor hit list and Merck Makes Phony Peer-​​Review Journal

May 3 2009

The abil­ity to run in a com­pletely 64-​​bit envir­on­ment is a major bene­fit of Linux over the com­pet­i­tion. With everything open source, the com­munity can port and com­pile applic­a­tions to new archi­tec­tures with ease.

On Win­dows, you have to suf­fer from the fact that just about everything is pro­pri­et­ary. If there’s no 64-​​bit ver­sion of your applic­a­tion, you’re forced to run it in a degraded (com­pared to the rest of the OS) 32-​​bit mode. Even worse, if there’s no 64-​​bit driver for your hard­ware then you can’t use it at all. You’re at the mercy of the vendor, and if the hard­ware is no longer being sold then there really is no eco­nomic incent­ive for them to write a new driver for you. Once Win­dows 7 comes out, you’ll prob­ably be back to square one (since most drivers are OS version-​​specific).

What hap­pens when you have a pro­pri­et­ary piece of soft­ware on Linux? For­tu­nately there are very few of these worth using. For the ones that are, the situ­ation isn’t too dif­fer­ent than on Windows.

Take Adobe Flash, for example. Adobe (and before them, Mac­ro­media) have claimed that port­ing the code base to x86_​64 is no walk in the park. On Linux, the means of deal­ing with this has been to use nsplu­gin­wrap­per to coax the 32-​​bit Flash plug-​​in to work inside a 64-​​bit Web browser. Sim­ul­tan­eously, there’s been devel­op­ment on free runtimes for Flash media, like gnash and swf­dec. The ‘solu­tion’ on Win­dows and Mac OS X is truly sub­op­timal: run a 32-​​bit Web browser. If you’ve ever used Win­dows 64-​​bit, you’ll notice that Microsoft bundle both 32– and 64-​​bit ver­sions of some of their soft­ware, with most icons point­ing to the 32-​​bit vari­ants. On the plus side, the user gen­er­ally is none the wiser.

Adobe have made avail­able a pre-​​release ver­sion of their x86_​64 Flash 10 plug-​​in for Linux (still no luck for other oper­at­ing sys­tems, AFAIK). I haven’t had any trouble with it, and from what I’ve read it’s been well received in the community.

Here are the steps to install it for Firefox:

  1. Unin­stall any exist­ing Flash pack­ages that you may have installed. Pack­age names include flashplugin-​​installer, flashplugin-​​nonfree, adobe-​​flash, mozilla-​​plugin-​​gnash and swfdec-​​mozilla.
  2. Down­load the tar­ball (the link is at the bot­tom of that page).
  3. There’s only one file inside, lib​flash​player​.so. Extract it to $HOME/.mozilla/plugins/ (cre­ate that dir­ect­ory if it doesn’t exist).
  4. If Fire­fox is run­ning, restart it.
  5. In Fire­fox, go to the about:plugins page.
  6. Look for the entry called Shock­wave Flash to con­firm it has been installed.

Warn­ing: You are manu­ally installing a pre-​​release ver­sion of a pro­pri­et­ary Web browser plug-​​in. This can have secur­ity implic­a­tions. Because it is not man­aged by the oper­at­ing system’s pack­age man­ager, you need to manu­ally make sure that you stay up-​​to-​​date to avoid secur­ity vulnerabilities.

Adobe Reader does not have an x86_​64 vari­ant for Linux, so you’ll have to install the 32-​​bit version.

  1. Down­load the latest DEB pack­aged from the Adobe FTP server.
  2. To install from the command-​​line, you’ll need to tell dpkg to ignore the archi­tec­ture of the pack­age:

    $ sudo dpkg -i --force-architecture AdbeRdr9.1.0-1_i386linux_enu.deb
  3. Launch it from the Applic­a­tions > Office desktop menu.

Warn­ing: Just as with the Flash-​​plug-​​in, be aware that you are installing soft­ware from out­side of the oper­at­ing system’s repos­it­or­ies, and that you are respons­ible to keep this pack­age up-​​to-​​date.

You’re prob­ably won­der­ing why you would need to do this when there are sev­eral great, free PDF read­ers out there. I almost always use Evince, but there are a couple of reas­ons why I like to keep Adobe Reader around:

  • some PDF files don’t work prop­erly in the free readers
  • most Win­dows users use Adobe Reader, so it’s good for test­ing (just as it’s use­ful to keep a Win­dows VM around to test Web sites against Inter­net Explorer)

LotD: autonomo​.us — Towards Free Net­work Services