Talked with Vincent today and he told me that his webserver got traffic from a weird .ee website and that is was requesting a certain image very often. Apparently the website contains a reference (in their CSS) to a picture on his website. This is absurd and dispicable, so his decided to replace the requested image with a totally Not Suitable For Work image. Just in case the site admin ‘fixes’ his error, I took the liberty of making a screenshot. Enjoy!
If you use the Zarafa webaccess (6.40, but apparently also 6.30) on Ubuntu 9.10, apache2 will nicely segfault and you will not be able to access your webmail. Upside: the mobile server will keep functioning. Even Fedora has this problem and it was tracked down to an error in PHP. I do not want to compile my own software to work around this issue, since I am lazy and I use a package manager for a reason! I quickly found the least nasty workaround for this issue in this post on the Zarafa forums.I replace /usr/lib/apache2/modules/libphp5.so (from karmic’s 5.2.10) with the libphp5.so from the 5.2.6 libapache2-mod-php5 package. At least the file will still be managed by dpkg and thus updated/upgraded if neccessary. As Ubuntu 10.04 is just around the corner, I will suggest the owner to does not update libapache2-mod-php5 until he upgrades to 10.04.
Just when you think you have seen it all, you experience something new. This happened when SSH’ing to a server which authenticates against an LDAP server:
The source of the problem was a configuration error in libnss-ldap.conf
Last week (during a LPI 101 course) one of my students gave me a bottle of sudocrem (by Boots healthcare). Yes, it contains a sudo component 
He gave it to me, since I explained vigorously why sudo is a good security mechanism, as long as you use it correctly.
Apparently this creme is used by many parents in the Netherlands for skincare of their young(er) children. Below you can find the obligatory picture:
