I’m a bit fascinated about KI lately. What finally made me interested was a report about George Hotz using machine learning to build a self driving car. And a deeply respected Friend of mine, Flavio Trolese, working on an “Cloud Power for Image KI” startup.

The ide is that working as a coder, I really appreciate how source code is managed by git nowadays. It’s a bit of a learning curve, but then it gets intuitive and very productive in managing simultanously changing code.

One of the core concepts of git is to “merge” the codes for two features into a new code base that contains both features. When changes not interfere they can be merged automatically. But when both changes touch the same lines of code, manual interventions is needed.

Most of these interventions are booring. The way the “conflicts” are presented is not intuitive for most of mankind. There’s tools, but anyway, solving such issues take developer time.

I think we should be able to build tools, using state-of-the-art open source technologies, automating most of the conflicts.

I try to blog about my progess into this. Maybe I succeed:-)

Some links for today:


A framework I’m currently giving a try. It includes some nice tutorials, like MNIST, the “hello world” of computer vision.

Awesome Deep Learning

One of many awesome lists. Lost of links to tools, tutorials, special areas…

Gmail Blog: Computer Respond to this Email

Similar use case: learn from millions of (merges|mail threads), and figure out an appropriate (resolution|reply).

Building Program Vector Representations for Deep Learning

A Chinese Paper I’ll give a try reading:-)


Debian unstable regains Xen Dom0 support

Good news everyone!

After a long time with no “modern” Linux Kernel available in Debian or Ubuntu for usage as Xen Dom0, the “Big Bang” release has been uploaded to Debian unstable. This actually means all the hardware support etc. from Kernel 2.6.32 AND Xen a simple ‘apt-get install’ away. Maybe we can even get Ubuntu Karmic DomUs running…

There’s some other goodies in it too, see Ben Hutchings Blog.

Voyage on ALIX Setup Notes

Can’t login using SSH

When you can’t login using SSH after installing Voyage Linux on a CF Card, this might come from extracting the voyage-XXX.tar.bz2 not as root. This results in some /dev/ nodes not being created.

Simplest solution: re-extract as root and run installation again.

cpio failes to update

If you’re getting the following error after apt-get update/upgrade from Debian Etch:

Unpacking replacement cpio …
Replaced by files in installed package tar …
dpkg: error processing /var/cache/apt/archives/cpio_2.6-18.1+etch1_i386.deb (–unpack):
unable to create `./usr/share/locale/da/LC_MESSAGES/’: No such file or directory
dpkg-deb: subprocess paste killed by signal (Broken pipe)

Then run these commands:

mkdir -p /usr/share/locale/da/LC_MESSAGES
mkdir -p /usr/share/locale/gl/LC_MESSAGES
mkdir -p /usr/share/locale/ko/LC_MESSAGES
mkdir -p /usr/share/locale/nl/LC_MESSAGES
mkdir -p /usr/share/locale/ru/LC_MESSAGES
mkdir -p /usr/share/locale/sv/LC_MESSAGES
mkdir -p /usr/share/locale/tr/LC_MESSAGES
mkdir -p /usr/share/locale/zh_CN/LC_MESSAGES

Now you the update should work…

How to fix broken NX user authentication after OpenSSL fix

It looks like OpenSSH Keys generated on Debian derived distros (Ubuntu/Voyage etc.) are REALLY bad. I’m currently rolling out OpenSSL key updates as adviced on

One casualty of this update was my NX server using freenx. It just tells me that I can’t be authenticated. In the log /var/log/freenx.log it shows the following:

— NX SERVER START: -c /usr/lib/nx/nxserver – ORIG_COMMAND=
HELLO NXSERVER – Version 2.1.0-71 OS (GPL)
NX> 105 hello NXCLIENT – Version 2.1.0
NX> 134 Accepted protocol: 2.1.0
NX> 105 login
NX> 101 User: shuerlimann
NX> 102 Password:
NX> 404 ERROR: wrong password or login
NX> 999 Bye

This post talks about the NoMachine NX Server, but gave me the necessary clues:

The magic command for freenx from
on Ubuntu is

sudo rm /var/lib/nxserver/home/.ssh/known_hosts

This is necessary, as the SSH host key has been updated… Well, a more informative error message would’ve been nice, but I’m thankfull to the guys who produce freenx, anyway;-)

Take part of the KDE relicensing effort

KDE needs a relicensing! While I’m not happy that the release of the GPL3 made such an effort necessary… But now it’s important to handle it fast and correct. Please give your feedback to techbase or use SVN:

svn co svn+ssh://$
vi scripts/ & add your name to all the four lists (that is if you agree to all four options)
svn ci scripts -m “I agree to a relicense”

As Tom Albers says:
“Really, it’s not more than a minute of work for you.”

Using KDE4 daily

I’m running KDE4 RC1 as my main desktop for 2 days now. Only few crashes, so productivity is good. But there are many small bugs. And it’s not very fast/responsive. But this is at least partially to blame on all the debug code.

Quite happy so far! It’s shaping up! Please test!!!

Packages from Kubuntu: HOWTO
KDE Four Live: openSUSE based Live CD
KDE4Daily: full virtual machine image with efficient update mechanism to SVN head

Please report any possibilities to try out KDE4 the easy way in the comments section:-)