‘Til All Are One

Freedom is the right of all sentient beings

May 9, 2009

Will it be Domesday or Doomsday for our information?

Filed under: History, Open standards, syndication-floss — Sridhar Dhanapalan @ 7:20 pm
1 Star2 Stars3 Stars4 Stars5 Stars (No Ratings Yet)
Loading ... Loading ...

The ABC have a piece from National Library of Australia web archiving manager Paul Koerbin, about the importance of digital records preservation.

Of equal importance, how can we be sure that we can actually read those archives in the future? Literacy of Egyptian Hieroglyphs was long-gone by the 18th century, and it took the discovery of the Rosetta Stone for them to start making sense again.

It’s difficult enough deciphering human language. Understanding machine language is another thing entirely.

I’ve written about this in the past, contrasting the thousand-year-old Domesday Book (which is still legible) with the BBC Domesday Project (which was rendered virtually unreadable a mere sixteen years after production).

The means of preserving our culture for digital preservation is to use open standards. If the means for ‘reading’ the information is widely documented and understood, without any encumbrances, we stand a much greater chance of being able to interpret it in a couple of hundred years.

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

Imagine you ran a company that had important and valuable written records stretching back for decades. Storing vast libraries of paper is expensive and inefficient, so you decide to digitise them all. That’s great — you now have a system that is easy to manage and search. Ten years later, you want to migrate your now-ageing data management system to something more modern. Only, you can’t — it’s all stored in a proprietary format that cannot be accessed by anything else.

If you had kept those paper records, you would have still had access to that information. Your choices now are to continue with your old, obsolete system for all eternity, or hire some clever hacker to decipher the file format. With no equivalent of a Rosetta Stone, that’s no mean task. After spending buckets of money on this avoidable problem, and losing even more due to inefficiencies and competitive disadvantage from the old system, you’d be wise to make sure it cannot happen again.

This is a very common kind of scenario. If our information can’t even last ten years, how can it last a thousand?

From a business perspective, open standards protect the independence of a company. It means no vendor lock-in, so you are not stuck paying monopoly prices. Through the creation of a free market surrounding a method/technology, open standards give you the freedom to select the vendors, products, methods and technologies that suit your requirements best, or you can even create your own. They are the ultimate in risk mitigation, and through their flexibility can also open avenues for competitive advantage. They just make good business sense.

LotD: Vioxx maker Merck and Co drew up doctor hit list and Merck Makes Phony Peer-Review Journal

May 3, 2009

Install Adobe Flash 10 and Reader 9.1 on Ubuntu 9.04 x86_64

Filed under: Ubuntu, syndication-floss — Sridhar Dhanapalan @ 1:25 am
1 Star2 Stars3 Stars4 Stars5 Stars (No Ratings Yet)
Loading ... Loading ...

The ability to run in a completely 64-bit environment is a major benefit of Linux over the competition. With everything open source, the community can port and compile applications to new architectures with ease.

On Windows, you have to suffer from the fact that just about everything is proprietary. If there’s no 64-bit version of your application, you’re forced to run it in a degraded (compared to the rest of the OS) 32-bit mode. Even worse, if there’s no 64-bit driver for your hardware then you can’t use it at all. You’re at the mercy of the vendor, and if the hardware is no longer being sold then there really is no economic incentive for them to write a new driver for you. Once Windows 7 comes out, you’ll probably be back to square one (since most drivers are OS version-specific).

What happens when you have a proprietary piece of software on Linux? Fortunately there are very few of these worth using. For the ones that are, the situation isn’t too different than on Windows.

Take Adobe Flash, for example. Adobe (and before them, Macromedia) have claimed that porting the code base to x86_64 is no walk in the park. On Linux, the means of dealing with this has been to use nspluginwrapper to coax the 32-bit Flash plug-in to work inside a 64-bit Web browser. Simultaneously, there’s been development on free runtimes for Flash media, like gnash and swfdec. The ‘solution’ on Windows and Mac OS X is truly suboptimal: run a 32-bit Web browser. If you’ve ever used Windows 64-bit, you’ll notice that Microsoft bundle both 32- and 64-bit versions of some of their software, with most icons pointing to the 32-bit variants. On the plus side, the user generally is none the wiser.

Adobe have made available a pre-release version of their x86_64 Flash 10 plug-in for Linux (still no luck for other operating systems, 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. Uninstall any existing Flash packages that you may have installed. Package names include flashplugin-installer, flashplugin-nonfree, adobe-flash, mozilla-plugin-gnash and swfdec-mozilla.
  2. Download the tarball (the link is at the bottom of that page).
  3. There’s only one file inside, libflashplayer.so. Extract it to $HOME/.mozilla/plugins/ (create that directory if it doesn’t exist).
  4. If Firefox is running, restart it.
  5. In Firefox, go to the about:plugins page.
  6. Look for the entry called Shockwave Flash to confirm it has been installed.

Warning: You are manually installing a pre-release version of a proprietary Web browser plug-in. This can have security implications. Because it is not managed by the operating system’s package manager, you need to manually make sure that you stay up-to-date to avoid security vulnerabilities.

Adobe Reader does not have an x86_64 variant for Linux, so you’ll have to install the 32-bit version.

  1. Download the latest DEB packaged from the Adobe FTP server.
  2. To install from the command-line, you’ll need to tell dpkg to ignore the architecture of the package:

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

Warning: Just as with the Flash-plug-in, be aware that you are installing software from outside of the operating system’s repositories, and that you are responsible to keep this package up-to-date.

You’re probably wondering why you would need to do this when there are several great, free PDF readers out there. I almost always use Evince, but there are a couple of reasons why I like to keep Adobe Reader around:

  • some PDF files don’t work properly in the free readers
  • most Windows users use Adobe Reader, so it’s good for testing (just as it’s useful to keep a Windows VM around to test Web sites against Internet Explorer)

LotD: autonomo.us - Towards Free Network Services

The content on this site is © Copyright 2002-2010 Sridhar Dhanapalan. Unless otherwise noted, content on this site is licensed under a Creative Commons Attribution-Share Alike 2.5 Australia Licence.
Creative Commons BY-SA Licence
Powered by Linux and Free Software