Archive for September, 2010

OSX – Broken NX/X11 after a recent upgrade

Tuesday, September 14th, 2010

After a recent OSX (Leopard) security update, my NX client failed to start (with a cryptic “session timed out” error). There were no other error messages of any kind, which was a bit puzzling. After a bit of investigation, I found out that X11 failed to start as well… we’re onto something.

$ /Applications/Utilities/X11.app/Contents/MacOS/X11.bin
Library not loaded: /usr/X11/lib/libX11.6.dylib Referenced from: /Applications/Utilities/X11.app/Contents/MacOS/X11.bin Reason: Incompatible library version: X11.bin requires version 10.0.0 or later, but libX11.6.dylib provides version 9.0.0

Aha, is seems like this error (weird, the bug looks rather old). Anyways, I reinstalled X11 and…. voila… things are happy again. Or, are they?

It turned out that xmonad stopped responding to my mod1 key (did I mention that I use xmonad and NX to work on a remote Linux station?). Again a bit of googling and I found the magic checkbox to uncheck (I must have set it long time ago an the setting got flushed when I reinstalled X11).

T.

Gratuliere Bergführer Nielsen & Nielsen!

Tuesday, September 7th, 2010

Thanks to Ulf & Lars for organizing this fantastic tour last weekend.

WordPress replacement?

Friday, September 3rd, 2010

Being frustrated with soooo many security vulnerabilities of my current blogging engine, I decided to find a replacement. Here’s a list of requirements I came up with:

  1. Not written in PHP
  2. No known security vulnerabilities.
  3. Supports customization – I would like to have a Tadek’s theme on it.
  4. Can import my current blog content.
  5. Supports markdown (or a similar syntax. The only thing I hate more than writing html, are bad UIs for generating it).

Since I already have a server, I didn’t want to go for a hosted solution (though I may change my mind on this one, as I did with my e-mail). I quickly discovered that excluding PHP, there’s little out there. Also, I didn’t want to jump to a full-bodied CMS for my puny website.

The more I thought about it, the more I realized I wanted have something very much like WordPress (willing to compromise on some bells and whistles like WYSIWYG editor I personally hate) that is not-Wordpress. Knowing what I to look for, I quickly came across Zine, which is exactly what I was looking for:

  1. It’s written in Python. Yay!
  2. It’s seems pretty nicely written and haven’t seen any mentions of security vulnerabilities (given, it’s a niche product).
  3. It’s really nice – I ported Tadek’s theme in no time. I also really liked the templating language.
  4. I managed to import my blog content in 2 min (I spent another 100 trying to identify two records-of-death).
  5. It has a markdown plugin. Yay!

While playing with Zine, I realized that PHP, with all its drawbacks and issues, has one big advantage: most programs are simple drag-n-drop and modules are very well supported on Debian I run. Having gone through a mixture of obsolete Python modules and easy_install, I started to appreciate simplicity. Ah, did I mention that my swigged psql module would crash apache workers with SEGV at random times?

It sounded like a challenge and, after two evenings, I actually do have a running Zine-powered WordPress replica in Python (I even started implementing some missing functions like adding counts to post categories and search function). The admin UI is awesome and I really like it. With a few days of evening hacking, I would have a really awesome blog in Python. It was only that when I realized that… the Zine and Python are slow. Not just slow, but it’s excruciatingly slow. My server is not the most powerful machine and having to wait almost 10s for the initial page load was way more than I could handle (to give justice, you can enable mamcache/file based caching). This is when I decided to grind my teeth, upgrade the WordPress blog one more time and give another try.

As of now, I am still not writing Zine off, but WordPress is to stay for now (well, at least till I get really annoyed).

T.

PS. I still cannot comprehend why getting WordPress behind SSL (under a different path) is sooooo hard. There used to be a plugin that did this but it since stopped working. But then WordPress’s security track record shows that maybe there’s more to worry about than somebody sniffing your password – just don’t reuse it ;-)

PPS. WordPress Android app is awesome and just works. I can share photos I took with just a few clicks.