busybox awk and network access

[Bernhard Reutner-Fischer]

On Fri, Mar 05, 2010 at 02:07:25PM -0500, Mike Frysinger wrote:
>On Friday 05 March 2010 10:13:00 David N. Lombard wrote:

>> Is '|&' any different than "2>&1"?
>
>the former is a pipe while the latter is a redirect.  ignoring that, let's go 
>with "yes".

To expand on that (and i assume that bash's manpage goes into detail on
this) '|&' == '2>&1 |' and '2>&1' != '2>&1 |'.

Oh and while we're pipe dreaming (sorry, couldn't resist ;), it would be nice
if ash would support process substitution.
Would greatly simplify stuff like busybox's "make release". Just:
release: distclean
	git archive --prefix=busybox-xyz/ HEAD|tee >(bzip2 -9>../bb-xyz.tar.bz2) >(xz -e9>../bb-xyz.tar.xz)|gzip -9>../bb-xyz.tar.gz
	stat -c "%n %s" ../bb-xyz.tar.*
../bb-xyz.tar.bz2 2294740
../bb-xyz.tar.gz 3149586
../bb-xyz.tar.xz 1840360

And yes, there's a possible bug in bash-4.1.0 because it needs ' >()' and
doesn't grok '>()'; it should append a space to pipe command
replacements, i guess.
Let me stop here before we're completely OT..