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 Rich _______________________________________________ busybox mailing list busybox@busybox.net http://lists.busybox.net/mailman/listinfo/busybox
