>I was told the latest ash can be found sun-lamp.cs.berkeley.edu in the
>directory /pub/NetBSD-current/src/bin/sh. I have picked up a copy and
>have managed to compile it. It seems to handle the `configure' scripts that
>come with most GNU packages without problems; which is about the most I will
>ever need, since I am very unlikely to write a shell script myself that will
>really test the capability of a shell. For example, ksh had trouble with
>the configure scripts of gzip and shellutils-1.8 (it produced spurious
>quotes in the makefile for gzip and completely hung during running the
>configure script of the shellutils package). But ash had no problem at
>all. The executable is about 64k, which is smaller than ksh. Hope this
well under Linux after using Sunando's new Makefile (the original Makefile
was absolutely unusable under Linux).
It runs indeed configure scripts very well except it cannot do `cd .' :-)
It has however some serious bug (I think): many shell scripts from INN and
smail use commands in backquotes (`date`). When running these scripts from
the command line, they work fine, but when run from crond they hang at the
first `...` command, consuming 100% CPU time. This is also the case for
/etc/rc scripts. I started using debugging traces but haven't been able
yet to find the problem.
When this bug has been fixed, ash will be a good (and small: 66K) /bin/sh
substitute for Linux.
I'm at home now but tomorrow I'll try the find out who the current
maintainers of NetBSD's ash are so I can report the bug.