Jul 4 2007

George Orwell’s clas­sic allegory, Animal Farm, presents many per­spect­ives on human beha­viour and soci­ety. One of these is how people can be led and manip­u­lated through the con­trol of inform­a­tion. In the story, the Seven Com­mand­ments formed a de facto con­sti­tu­tion for the Anim­al­istic soci­ety. Since only a hand­ful of anim­als could read, the rest were depend­ent upon what they were told was writ­ten. Gradu­ally, the writ­ing was cun­ningly altered to the bene­fit of the pigs above all other anim­als, and the popu­lace was taught to not trust their recol­lec­tions of what was writ­ten in the past.

What made this sub­ver­sion pos­sible was the inab­il­ity of most anim­als to read. The two anim­als that could read (aside from the pigs) chose not to do any­thing about what they saw. Amongst other things, the right to access and read inform­a­tion is an import­ant corner­stone of democracy.

This is where open file formats come in. As our lives become increas­ingly defined by elec­tronic records, there needs to be a way for inde­pend­ent view­ing and audit­ing. Paper is eas­ily read, but com­puter files require soft­ware to decypher them. Ima­gine if you needed spe­cial (and expens­ive) glasses just to read the let­ter that you your­self wrote only a few years ago.

There has been a fair amount of dis­cus­sion in the press regard­ing the Open­Doc­u­ment and the so-​​called ‘Open’ XML formats. The primary focus of this report­ing thus far has been on the polit­ical and tech­nical facets. This is slowly chan­ging, as the import­ance of long-​​term data pre­ser­va­tion and free­dom of inform­a­tion become appar­ent to ordin­ary folk.

The BBC has pub­lished a report on the prob­lem, and dis­cusses how the UK National Archives are attempt­ing to deal with it. Alas, it appears that they have opted for a short-​​sighted approach, rely­ing on vir­tu­al­isa­tion of older oper­at­ing sys­tems and applic­a­tions, through a dir­ect part­ner­ship with Microsoft. With this approach, the format decoders/​viewers (not to men­tion the oper­at­ing sys­tem and soft­ware per­form­ing the vir­tu­al­isa­tion itself) remain closed in source and spe­cific­a­tion, and one must deal with a cum­ber­some vir­tual machine just to view a document.

Where is the guar­an­tee that files can be read hun­dreds of years from now, just as we can do today with paper doc­u­ments such as the his­toric Magna Carta? How does this part­ner­ship bene­fit me, an ordin­ary cit­izen who might wish to view ten– (or even two-​​) year-​​old pub­lic doc­u­ments that are only avail­able in a pro­pri­et­ary elec­tronic format?

It’s both sad and frus­trat­ing to see that his­tory is yet again repeat­ing itself. Whilst the con­tents of the Domes­day Book can still be read nearly 1000 years after com­ple­tion, the digital BBC Domes­day Pro­ject was rendered vir­tu­ally unread­able a mere 16 years later.

Thank­fully, there are efforts to cre­ate an infra­struc­ture for long-​​term pre­ser­va­tion and man­age­ment of digital doc­u­ments. To start with, there are open formats such as Open­Doc­u­ment and PDF. The Aus­tralian National Archives have long been sup­port­ers of Open­Doc­u­ment, to the extent that they are stand­ard­ising upon it. Put­ting their money where their mouths are, they are build­ing a com­pletely open source (GPL, no less) data man­ag­ment sys­tem that any­body 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 tech­no­logy, known as Xena [PDF]. Whilst their UK coun­ter­parts seem to have for­got­ten that access to data is not just a priv­ilege for those able to make exclus­ive agree­ments with pur­vey­ors of lock-​​in tech­no­lo­gies, the Aus­tralian National Archives have been striv­ing to ensure that nobody is left out of the digital revolution.

Four legs good, two legs… bet­ter? Let’s pre­vent this sub­ver­sion from happening.

 

LotD:  Mex­ican ‘world’s richest person’

Aug 13 2006

In Janu­ary, dur­ing Steve Jobs’ Mac­world key­note speech announ­cing the new Intel Macin­toshes, Microsoft made a “com­mit­ment” to con­tinue to develop for and sup­port the Apple Macin­tosh plat­form. In true Microsoft style, they con­veni­ently didn’t explain how deeply that com­mit­ment went. Now we know.

Microsoft have decided to kill their Vir­tual PC product, remov­ing a vir­tu­al­isa­tion option from Mac OS at the same time that sim­ilar func­tion­al­ity is being fol­ded into Win­dows Vista. They are aware that vir­tu­al­isa­tion is quickly becom­ing a killer fea­ture, and they’ll be damned if they allow any­one else to have it. For­tu­nately (and prob­ably prefer­ably), VMware will be made avail­able for the Apple Intel plat­form. There’s also Par­al­lels, but they still do not have any server-​​oriented products.

In addi­tion, Microsoft will also be remov­ing Visual Basic sup­port from Office for Mac. If you can’t stop sup­port­ing some­thing, why not cripple it instead? Many busi­nesses are depend­ent upon VB script­ing, or exchange files with people/​organisations that make use of it, so this is a major blow indeed for Apple. Such a defi­ciency will be subtle: people will pur­chase Office for Mac expect­ing it to work with files cre­ated in its Win­dows coun­ter­part (or vice versa), and will be sorely dis­ap­poin­ted. This has already been occur­ring for a num­ber of years, but the prob­lem is becom­ing increas­ingly acute.

Ulti­mately, the best solu­tion is to remove our depend­ency on pro­pri­et­ary formats and lan­guages, for they are the root cause of this mess. Open​Of​fice​.org already does what most people require, and in some cases it does it bet­ter. It even has grow­ing sup­port for Visual Basic for Applic­a­tions. Open­Of­fice is truly look­ing like a bet­ter Office than MS Office. The Open­Of­fice file fil­ter­ing sup­port developers work hard to sup­port all the MS Office formats they can find (people have coun­ted over 20 dif­fer­ent ver­sions of the Word .DOC format alone), which is more than I can say about the MS Office pro­gram­mers, who are notori­ous for break­ing com­pat­ib­ilty with older ver­sions. Using the Open­Doc­u­ment formats (which are now an ISO stand­ard) assures that your data will be access­ible on many dif­fer­ent plat­forms for many years to come.

The main stum­bling block to Open­Of­fice adop­tion on Mac OS is the Windows-​​like inter­face and its reli­ance on X11 for dis­play. There is work being done on a nat­ive Aqua ver­sion, but in the mean­while there is NeoOf­fice.

Aug 6 2006

Kle­pas poin­ted us on IRC to a brilliantly-​​done film explain­ing the concept of Trust­worthy Com­put­ing. It con­cisely and clearly demon­strates why so many of us in the FLOSS world prefer to call it Treach­er­ous Com­put­ing.

Unfor­tu­nately, the pro­du­cers decided to make the film avail­able as a Sorenson-​​encoded Quick­time file. I find it amus­ing that people who oppose digital restric­tions are using such a highly-​​proprietary video format. For­tu­nately for us, there is a DivX/​MP3 ver­sion (still not as good as The­ora or even XviD, but it’ll do) avail­able at Google Video.

Once you have fin­ished view­ing it, head on over to Against-​​TCPA for more information.

Dec 28 2002

I haven’t pos­ted any art­icles on PCLinuxOn­line over the past three weeks because I b0rked my Gentoo sys­tem. I upgraded from glibc 2.2.5 to 2.3.1 and since then I haven’t been able to run cer­tain apps without wreck­ing everything else. I’ve detailed my prob­lem here and here. If any­one can help I’d much appre­ci­ate it.

At the moment I can run most apps, but things screw up when I load any part of KDE (includ­ing Kon­queror) or Evol­u­tion. GTK+ (1 and 2) apps (apart from Evol­u­tion) work fine.

Update [200303-07]: The prob­lem is with my Nvidia drivers:

Hi! I’m the guy who star­ted this thread. I finally man­aged to fix things by turn­ing off Grse­cur­ity in my ker­nel. How­ever, a very sim­ilar (but dif­fer­ent) prob­lem emerged a few months later. It occurred around the time I upgraded glibc to 2.3.1, so I ini­tially thought glibc was to blame. After lots of exper­i­ment­ing with ker­nel con­figs, I dis­covered that I could have a stable sys­tem using Nvidia drivers if I turned high­mem off, sac­ri­fi­cing just over 100MB of RAM (I have 1GB total).

I then came across cigaraficionado’s bug report and updated nvidia-​​kernel ebuild. I com­piled a new ker­nel, this time turn­ing high­mem back on, and installed the new ebuild. The updated ebuild had no effect — using the Nvidia driver made my sys­tem unstable like before.

My hard­ware seems fine. Memtest86 detects no errors in my RAM (2x Cor­sair XMS 512MB DDR333 SDRAM). My GeForce 3 Ti200 card works per­fectly in Win­dows and it worked per­fectly in Gentoo until Decem­ber, around the time I upgraded to glibc 2.3.1. I can’t fig­ure out where the true prob­lem is, but I strongly sus­pect it lies with nvidia-​​kernel.

That’s what you get for rely­ing on binary-​​only ker­nel mod­ules :(

Next Entries »