Rich, All,
On Sunday 02 September 2012 23:21:36 Rich Felker wrote:
> It seems busybox ash is misinterpreting "&>" as having some special
> meaning rather than being a "&" token followed by a ">" token.
The &> operator is not defined in POSIX. However, reading the bash manpage
gives:
[--SNIP--]
Redirecting Standard Output and Standard Error
This construct allows both the standard output (file descriptor 1) and
the standard error output (file descriptor 2) to be redirected to the
file whose name is the expansion of word.
There are two formats for redirecting standard output and standard
error:
&>word
and
>&word
Of the two forms, the first is preferred. This is semantically
equivalent to
>word 2>&1
[--SNIP--]
ash can "include" some bash extensions if configured to. Not sure &> is
part of the supported extnesions, though. Maybe you can check this in your
busybox configuration.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
busybox mailing list
[email protected]
http://lists.busybox.net/mailman/listinfo/busybox
