Ich muß jetzt mal meinem Ärger über die Bundespost, ähm, die “Deutsche Post AG” meine ich natürlich, Luft machen…
Vor einigen Wochen fuhr ich samstags zur Post im Kapuzinerkarrée hier in Aachen, um zwei Pakete zu versenden. Da ich extrem selten Pakete versende, hatte ich die entsprechenden Versandformulare nicht zur Hand. Ich stellte mich also in die (extrem lange) Schlange und wartete, bis ich endlich an der Reihe war.
I had some very strange problems with Cisco’s VPN client today that almost made me go berzerk… 
It all began when I tried to use the VPN client over an establish WLAN connection. For no apparent reason, the client was unable to connect to the VPN gateway. It gave me a strange error message that didn’t help me (I forgot the exact wording). The strange thing was that I could establish a VPN connection when I was dialled in with my Vodafone Mobile Connect Card. But it wasn’t the Internet connection itself which was hampering the establishment of a VPN connection, since the VPN gateway was accessible in both cases.
I’m trying to establish an encrypted connection to my self-operated e-mail server. For this, I need to get the root certificate of the CA (CAcert) which certified my server’s public key installed on my mobile phone (a SonyEricsson V630i, remember?).
However, regardless what I try, the mobile doesn’t accept the certificate. (more…)
I just had a nightmarish experience when I upgraded Debian’s unstable WordPress package to version 2.1. When I invoked my site for the first time, WordPress prompted me to upgrade its database — which I did, of course, or rather “I tried to do.”
After I started the upgrade, I saw a dozen or so error messages rushing over my screen. When I analyzed them, I quickly recognized that the database user didn’t have sufficient permissions to perform certain table alterations. I thought, “Hey, no prob, correct the permission problems, and re-run everything.”
But “Not so!” WordPress was able to write the new WP database version no. into the database in the last step of the upgrade procedure, so the upgrade refused to run again because it thought the database was already current.
So what could I do?
