On Sun, Sep 2, 2012 at 11:21 PM, Rich Felker <dalias at aerifal.cx> wrote: > It seems busybox ash is misinterpreting "&>" as having some special > meaning rather than being a "&" token followed by a ">" token. I've > filed a bug report: > > https://bugs.busybox.net/show_bug.cgi?id=5498 Set CONFIG_ASH_BASH_COMPAT to "no" and it will stop doing that.