shell parsing bug with &>

Rich Felker dalias at aerifal.cx
Sun Sep 2 21:21:36 UTC 2012


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


More information about the busybox mailing list