Customers suck, they only make problems. Doing support keeps one away from the actual work. What also makes problems are old houses with thick walls, since you can't use WLAN inside of them. WLAN at one of our customers (with such thick walls) is extremely flakey and unstable because of that, as I realized today. You do not even get a good, reliable connection 10 meters away from the access point!

Today, I did some work on dietlibc, I simplified the malloc/free routines, until I realized that, with my modifications, any program linked against the dietlibc and allocating small chunks of memory will be a memory-eating monster. Anyway, my patch still simplifies the malloc/free routines, so that they're much easier to understand. Currently, I don't know whether I will even publish this patch.

Today, I also got my answer regarding my patches for config.{guess,sub} so that these two well-known and often used scripts manage to detect dietlibc. When I compile and links programs with dietlibc, I want to have "i686-pc-linux-dietlibc" instead of "i686-pc-linux-gnulibc1", since programs linked against dietlibc are most likely _not_ GNU software.