2014-11-19 Today, I installed a Debian packaging bug. [0] In /usr/lib/php5/sessionclean, which is executed by cron, `sed -z' was used. It failed because sed does not have a -z option. To my shock, people told, that future GNU sed will have such an option. I hope people won't use it. It's not portable -- someone really said ``but unfortunatelly we missed the fact that wheezy's sed doesn't have -z'', i.e. implying the reason this script is buggy is because the sed currently in Debian does not support `-z', and thus implying that, if the sed in Debian will support this op- tion, it wouldn't be a bug. This is quite naive, IMO. (Btw: sed equals gsed in Debian; it is not abstracted like awk.) -- and apart from that, the practice of using NUL characters as separa- tors in all pipelines is a pain. Let's add this feature to *all* tools that read anything from stdin or write anything to stdout ... yay! How ridiculous! We should rather forbid newline charac- ters in file names to solve this issue. (It's insane to use new- lines in file names anyway.) [0] http://bugs.debian.org/770105 http://marmaro.de/lue/ markus schnalke