’Til All Are One

Freedom is the right of all sentient beings

This blog has moved!
Please go here for the current location.

4 July, 2007

Four legs good, two legs bad!

George Orwell’s classic allegory, Animal Farm, presents many perspectives on human behaviour and society. One of these is how people can be led and manipulated through the control of information. In the story, the Seven Commandments formed a de facto constitution for the Animalistic society. Since only a handful of animals could read, the rest were dependent upon what they were told was written. Gradually, the writing was cunningly altered to the benefit of the pigs above all other animals, and the populace was taught to not trust their recollections of what was written in the past.

What made this subversion possible was the inability of most animals to read. The two animals that could read (aside from the pigs) chose not to do anything about what they saw. Amongst other things, the right to access and read information is an important cornerstone of democracy.

This is where open file formats come in. As our lives become increasingly defined by electronic records, there needs to be a way for independent viewing and auditing. Paper is easily read, but computer files require software to decypher them. Imagine if you needed special (and expensive) glasses just to read the letter that you yourself wrote only a few years ago.

There has been a fair amount of discussion in the press regarding the OpenDocument and the so-called ‘Open’ XML formats. The primary focus of this reporting thus far has been on the political and technical facets. This is slowly changing, as the importance of long-term data preservation and freedom of information become apparent to ordinary folk.

The BBC has published a report on the problem, and discusses how the UK National Archives are attempting to deal with it. Alas, it appears that they have opted for a short-sighted approach, relying on virtualisation of older operating systems and applications, through a direct partnership with Microsoft. With this approach, the format decoders/viewers (not to mention the operating system and software performing the virtualisation itself) remain closed in source and specification, and one must deal with a cumbersome virtual machine just to view a document.

Where is the guarantee that files can be read hundreds of years from now, just as we can do today with paper documents such as the historic Magna Carta? How does this partnership benefit me, an ordinary citizen who might wish to view ten- (or even two-) year-old public documents that are only available in a proprietary electronic format?

It’s both sad and frustrating to see that history is yet again repeating itself. Whilst the contents of the Domesday Book can still be read nearly 1000 years after completion, the digital BBC Domesday Project was rendered virtually unreadable a mere 16 years later.

Thankfully, there are efforts to create an infrastructure for long-term preservation and management of digital documents. To start with, there are open formats such as OpenDocument and PDF. The Australian National Archives have long been supporters of OpenDocument, to the extent that they are standardising upon it. Putting their money where their mouths are, they are building a completely open source (GPL, no less) data managment system that anybody can use or improve to suit their needs. Michael Carden gave a great talk [Ogg video] at this year’s linux.conf.au about this technology, known as Xena [PDF]. Whilst their UK counterparts seem to have forgotten that access to data is not just a privilege for those able to make exclusive agreements with purveyors of lock-in technologies, the Australian National Archives have been striving to ensure that nobody is left out of the digital revolution.

Four legs good, two legs… better? Let’s prevent this subversion from happening.

 

LotD:  Mexican ‘world’s richest person’

13 August, 2006

Microsoft’s “Commitment” to Apple

In January, during Steve Jobs’ Macworld keynote speech announcing the new Intel Macintoshes, Microsoft made a "commitment" to continue to develop for and support the Apple Macintosh platform. In true Microsoft style, they conveniently didn’t explain how deeply that commitment went. Now we know.

Microsoft have decided to kill their Virtual PC product, removing a virtualisation option from Mac OS at the same time that similar functionality is being folded into Windows Vista. They are aware that virtualisation is quickly becoming a killer feature, and they’ll be damned if they allow anyone else to have it. Fortunately (and probably preferably), VMware will be made available for the Apple Intel platform. There’s also Parallels, but they still do not have any server-oriented products.

In addition, Microsoft will also be removing Visual Basic support from Office for Mac. If you can’t stop supporting something, why not cripple it instead? Many businesses are dependent upon VB scripting, or exchange files with people/organisations that make use of it, so this is a major blow indeed for Apple. Such a deficiency will be subtle: people will purchase Office for Mac expecting it to work with files created in its Windows counterpart (or vice versa), and will be sorely disappointed. This has already been occurring for a number of years, but the problem is becoming increasingly acute.

Ultimately, the best solution is to remove our dependency on proprietary formats and languages, for they are the root cause of this mess. OpenOffice.org already does what most people require, and in some cases it does it better. It even has growing support for Visual Basic for Applications. OpenOffice is truly looking like a better Office than MS Office. The OpenOffice file filtering support developers work hard to support all the MS Office formats they can find (people have counted over 20 different versions of the Word .DOC format alone), which is more than I can say about the MS Office programmers, who are notorious for breaking compatibilty with older versions. Using the OpenDocument formats (which are now an ISO standard) assures that your data will be accessible on many different platforms for many years to come.

The main stumbling block to OpenOffice adoption on Mac OS is the Windows-like interface and its reliance on X11 for display. There is work being done on a native Aqua version, but in the meanwhile there is NeoOffice.

6 August, 2006

Trustworthy/Treacherous Computing

Klepas pointed us on IRC to a brilliantly-done film explaining the concept of Trustworthy Computing. It concisely and clearly demonstrates why so many of us in the FLOSS world prefer to call it Treacherous Computing.

Unfortunately, the producers decided to make the film available as a Sorenson-encoded Quicktime file. I find it amusing that people who oppose digital restrictions are using such a highly-proprietary video format. Fortunately for us, there is a DivX/MP3 version (still not as good as Theora or even XviD, but it’ll do) available at Google Video.

Once you have finished viewing it, head on over to Against-TCPA for more information.

28 December, 2002

glibc blues

I haven’t posted any articles on PCLinuxOnline over the past three weeks because I b0rked my Gentoo system. I upgraded from glibc 2.2.5 to 2.3.1 and since then I haven’t been able to run certain apps without wrecking everything else. I’ve detailed my problem here and here. If anyone can help I’d much appreciate it.

At the moment I can run most apps, but things screw up when I load any part of KDE (including Konqueror) or Evolution. GTK+ (1 and 2) apps (apart from Evolution) work fine.

Update [2003-03-07]: The problem is with my Nvidia drivers:

Hi! I’m the guy who started this thread. I finally managed to fix things by turning off Grsecurity in my kernel. However, a very similar (but different) problem emerged a few months later. It occurred around the time I upgraded glibc to 2.3.1, so I initially thought glibc was to blame. After lots of experimenting with kernel configs, I discovered that I could have a stable system using Nvidia drivers if I turned highmem off, sacrificing just over 100MB of RAM (I have 1GB total).

I then came across cigaraficionado’s bug report and updated nvidia-kernel ebuild. I compiled a new kernel, this time turning highmem back on, and installed the new ebuild. The updated ebuild had no effect — using the Nvidia driver made my system unstable like before.

My hardware seems fine. Memtest86 detects no errors in my RAM (2x Corsair XMS 512MB DDR333 SDRAM). My GeForce 3 Ti200 card works perfectly in Windows and it worked perfectly in Gentoo until December, around the time I upgraded to glibc 2.3.1. I can’t figure out where the true problem is, but I strongly suspect it lies with nvidia-kernel.

That’s what you get for relying on binary-only kernel modules :(

Powered by GNU/Linux, Apache and WordPress