the builtin printf in sh(1) behaves differently than /usr/bin/printf, specifically: Fix: I'm working around by specifying /usr/bin/printf for strings that require '0' padding. How-To-Repeat: (ttyp0@jake)$ /bin/sh (ttyp0@jake)$ printf "%04d\n" 12 12 (ttyp0@jake)$ /usr/bin/printf "%04d\n" 12 0012
Responsible Changed From-To: freebsd-bugs->joerg I'm goinmg to deal with sh(1) bugs some day.
State Changed From-To: open->closed Fixed after 4.4Lite2 sh code merge