If you want to debug postinst scripts, you can easily do this on the machine where you (half) installed the package. Normally you can execute /var/lib/dpkg/info/foo.postinst like this:

sh -x /var/lib/dpkg/info/foo.postinst configure


However, if you use debconf, the output will be like this:
+ . /usr/share/debconf/confmodule
+ [ ! ]
+ PERL_DL_NONLAZY=1
+ export PERL_DL_NONLAZY
+ [ ]
+ exec /usr/share/debconf/frontend /var/lib/dpkg/info/foo.postinst


Which is not helpful either. However, you can add “set -x” in /var/lib/dpkg/info/foo.postinst and then just execute it, it will give you the full output.


sh /var/lib/dpkg/info/foo.postinst configure


Now the debugging process can begin!

When only one package is made, this is easy: just install the files in debian/tmp as you would when installing on the system. For multiple packages, each package has its own directory: debian/<package-name>. How does dh_builddeb figure out which directory to use?

Apparently, the default behaviour is to let the first package use the debian/tmp dir, and the other packages use the debian/<package-name> directory.

I would rather have them all using the debian/<package-name> directory, but I could not find an option to do this.

Update:
It seems that setting the compatibility level to 7 fixes this behaviour (echo “7″ > debian/compat), see man debhelper (section “Compatibility levels” for more info.

client 192.168.1.1#37242: view internal: query: www.apple.com IN A +

I changed the regexp and I archive it here in case anyone else (or future-me) wants to use this:

--- bind9.orig	2009-11-01 15:06:16.000000000 +0100
+++ bind9.new	2009-11-01 15:06:07.000000000 +0100
@@ -73,9 +73,9 @@
     open(Q,"< $QUERYLOG") or die "$!";
     while (<Q>) {
 	chomp;
-	if (/client \d+\.\d+.\d+.\d+\#\d+: query\: \S+ (\w+) (\w+)/) {
-	    if ($1 eq 'IN' and $2 !~ /^TYPE/) {
-		$IN{$2}++;
+	if (/client \d+\.\d+.\d+.\d+\#\d+: (view \w+: )?query\: \S+ (\w+) (\w+)/) {
+	    if ($2 eq 'IN' and $3 !~ /^TYPE/) {
+		$IN{$3}++;
 	    } else {
 		$OTHER++;
 	    }

By the way, I also found out that there is a program called 'munin-run' which can be used to run the plugin as munin would, this saves a lot of hassle with sudo and environment settings!

Oct  8 03:32:08 hoshi kernel: [145430.434977]kjoradsatn. omtitra  eod

edit: Oct 9
Today, I got this one, this is getting scary:

Oct  9 03:32:08 hoshi kernel: >99873]koradsatn. omtitra  eod

The only link I could find was this one: http://forums.gentoo.org/viewtopic-t-245137-start-0.html But it does not help me a lot.

When comparing the output of dmesg to the one in /var/log/kern.log (which is the source of the garbled messages), the only thing that is missing in the kern.log is this:

[236989.877537] kjournald starting.  Commit interval 5 seconds

It looks like this is the source from the garbled message: If you start from ‘k’ and take only every other character, you’ll see. So apparently, this is not a kernel problem (because the message appears ungarbled in dmesg) but rather a problem with syslogd.

Now things get really strange, as I have an rsyslogd daemon running, but I could not find the binary on the disk. It seems that I accidentally started a syslog daemon in a chroot (I did play around with that certain chroot, because I was fixing a computer that was booting via nfs-root from this machine).

The funny thing is that the rsyslogd that was running, was actually a 32-bit executable (the nfsroot is a 32-bits install), while the host is a 64-bit system. So I’ve been running a 32-bit syslogd on a 64-bit for two days :)

I’ll see if I get another garbled message tomorrow, but I think the problem is solved now :)

Scrambled character set

A friend of mine had a problem with his terminal today. Most people will encounter this one day or another. He asked me how to fix it. I told him to do ‘cat /bin/bash’ and press ^C at one point and repeat this until it worked. He was surprised that worked and asked me why. I told him I didn’t know exactly, but that it had to do with control characters that are often found in binary files but I was curious myself to so I did some research.

Apparently there is an ANSI escape sequence to select character sets. To select one of these character sets, the ANSI code ‘ESC(0′ is used. Because terminals will catch the escape character, we have to do some extra to get a literal ESC: type ^V ESC. The character will be displayed as: ‘^[‘. Typing this will result in a terminal that looks like the image above:


bash$ echo '^[(0'


You can get the correct character set back by typing ‘ESC(B’, but maybe a better idea is to reset the terminal (the program ‘reset’ will not always reset the character set) with the following ANSI code: ‘ESCc’. For this command we don’t have to use single quotes to avoid the parenthesis from being interpreted, so this easier to remember:


bash$ echo ^[c


So whenever you get this problem, remember to press these 4 keys (ok, I count a control character as one key): ^V ESC c ENTER

Connecting with Eduroam can be done by following the instructions on this site, and for RuG-FN2, there is also this website, but the latter profile will always ask for a password and this is tedious to type in everytime, especially if people can see what you type.

Therefore I made my own profile, which can be downloaded here. Just surf to that page on your iPhone/iPod touch and accept the configuration. Fill in your username and password and you’re good to go. Of course, you need internet access to do that, so you can do this in advance (for example at home).

update: the network changed, find your new profile here

If you have no idea what I’m talking about, this post is not for you :)

Apparently, you can disable it in the preferences of MobileMe, but only when you have signed up for an account (if you search in System Preferences, the option shows up, but if you select it, you get a dialog that says you have to sign up first).

After some searching, I found this thread: http://discussions.apple.com/thread.jspa?threadID=1633095&tstart=0, that explains that you can ALSO disable it through preferences of the program iSync (I don’t know if it’s pre-installed, but it was on my computer).

A third option was to remove it by CMD+dragging it out of the menu bar, but it seems that is only temporary.

Yeah, more space in my menu bar for things that I actually use :)

From before I remembered a program that could restrict commands, but I forgot the name, so fo r future reference I write this post. The program is called ‘authprogs’ and can be found here.

I like this program, because you can specify (with a config file) which hosts are able to do which commands, and it logs (and outputs to the user) commands that are rejected, so you can try your command and copy-paste it into the configuration.