ash backticks busted in 1.2.2.1

[Bennett Todd]

2006-11-01T17:24:30 David Daney:
> I suggest that you read all the comments on the list about what a bad 
> idea it is to statically link to glibc.

Thanks for the suggestion, it'll be a few days but when I get a nice
chunk of hack-at-home time I'll do that very thing.

Had a weird problem where an installer initrd was getting itself
into a wedged state where every attempt to run bunzip or cpio
segved instantly, as best strace could tell without issuing a
single syscall. Still have no clue what's the root cause but
have been experimenting with different ways of building initrd
components. Ended up having to pile on a ton of shlibs to get dns
to work but otherwise the static glibc seemed to be ok, until I
realized ash couldn't do backticks. I'll try rebuilding 1.2.2.1 on
my home uclibc-based distro (in a few days, I'm afraid), and will
send another note if I can reproduce the problem there, otherwise
we'll happily blame it on glibc. Meanwhile the mysterious segv-ing
persisted even with glibc. Persisted even when I switched to using
the Red Hat bunzip and cpio. So I'm off the theory that uclibc had
anything to do with that problem. I'm currently hoping it's skunky
hardware.

-Bennett