bind9 runs in a chroot environment on lenny. The service can be started as usual: # /etc/init.d/bind9 start Starting domain name service...: bind9. Let’s check bind9 status: ` /etc/init.d/bind9 status bind9 is not running failed! ` Well, the first thing I did was to check the log file, in which I found no error related to named. So I tried another way to check the status: # rndc status version: 9.6-ESV-R3 CPUs found: 1 worker threads: 1 number of zones: 17 debug level: 0 xfers running: 0 xfers deferred: 0 soa queries in progress: 0 query logging is OFF recursive clients: 0/0/1000 tcp clients: 0/100 server is up and running I was convinced that the DNS service was running. So what went wrong? It must be something in the /etc/init.d/bind9 script that incorrectly reports bind9 status. Opened up this file, I found: ...

3 is my mobile carrier. It offers an online service which allows its customers to check the current usage from their phones by accessing this URL: three.net.au/my3/gethome.do. Usually it works quite well, but not today (and probably some more days to come), it gave me a HTTP ERROR 404. I thought I should just visit http://three.net.au and find out w-t-h is wrong. Unexpectedly it took me to another site — “callenden group policy wording”. It’s very weird so with some spare time, I decided to do a little investigation. ...

This is a self-note. $ banshee --disable-dbus

On Ubuntu 10.10, if you get an error message as the following when trying to create audio CD from mp3: “Unable to handle the following files due to an unsupported format: You may manually convert these audio files to wave using another application supporting the audio format and then add the wave files to the K3b project.” Check if you have libk3b6-extracodecs installed, if not just; $ sudo apt-get install libk3b6-extracodecs ...

On Debian: # apt-get install libnet-ldap-perl