2011-05-03 I'm writing few about the stuff I do currently, though I could write a lot. Again a summary of the last days. I have worked on masqmail quite a bit, but right now this work is stopped as university demands lots of programming now. For the system-level programming lecture, I needed to write a program to crack passwords using brute force. This wasn't diffi- cult and neither the version that forks for better performance. But covering the last corner-cases of the forking version (off- by-one and the like) required a lot of time. The 80:20 ratio proved right. When the exercise descriptions already propose bad approaches to the problem it will become more difficult to solve. A good ap- proach makes everything else easier. Proposed approaches to solve excercises should always be regarded with suspect. If they seem to be bulky, go your own way. Otherwise your solution will be bulky too. Two impressions from being tutor for script languages: In order to understand what regular expressions match, you need the right view on them: Play finite state machine! Be exact. EX- ACT! I can't recall who had said that SQL is one of the language in which you spend much more time thinking than writing, however, he is right. First: Think! Did some programming in PostScript. I like the language. It's pretty consistent, which is something I appreciate. Some command names could consist of less chars, though. ;-) Inne pointed me to the problems of EXIF data in JPEGs. If you want to remove them use: mogrify -strip *.jpg Why do I use ksh? I would need too many words to answer, thus I don't. Only that much: ksh isn't perfect, but neither is it worst. Some day I might reconsider. Frequently using different keyboard layouts is a mayor decrease in input efficiency. http://marmaro.de/lue/ markus schnalke