In <[EMAIL PROTECTED]>, David O'Brien wrote:
> On Thu, Dec 16, 1999 at 03:40:20PM +0100, Martin Cracauer wrote:
> > You can also fool sh into running the *wrong* binary if if you have
> > two in showdowed paths:
>
> pdksh does not suffer from either this problem or the problem that
> started this thread (and does not coredump). We've shown in the past
> that pdksh is actually smaller (when linked statically) than ash.
>
> I still think we should *seriously* consider switching to pdksh.
As I said before, pdksh has other bugs.
Try this in pdksh:
#! /bin/sh
emacs -nw /tmp/bla
mv /tmp/bla /tmp/bla2
Two times:
- first run, do not hit C-g in emacs
- second run, use C-g in emacs
In the second run, the `mv` will not be executed, while in the first
it will.
This is not a bug, but a design decision in pdksh (see also my
homepage - sigint.html). It's poor man's workaround about programs
that don't exit with a proper signal status when they exit on a
signal.
Also we would loose all the PRs we received in the past. This testing
effort by our user base is a valuable resource. From the tests I ran
on all available shells, only bash2 is considerably better than the
other shells, pdksh has other bugs than our ash, not less.
Martin
--
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Martin Cracauer <[EMAIL PROTECTED]> http://www.cons.org/cracauer/
Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
