http://www.opengroup.org/onlinepubs/007904975/toc.htm
> Probably of more interest is this: Prior to your tweaks, the Menuconfig
> script just reported that one was trying to run it under the wrong
> shell. What happens when one tries to run your modified version under
> those conditions? There are only two valid answers:
Remember, Keith Owens pointed out that it's really a test of
CONFIG_SHELL, not /bin/sh.
> 1. It runs successfully.
>
> 2. It reports that it can't run under that shell.
>
> You're the one proposing the patch, so you're the one who needs to
> answer that question.
Well, my understanding of the patch is that it removes all of the
bash'ism and related from the script, so that any shell which will
accept things from the above URL will work. So one of two things will
happen when /bin/sh != /bin/bash
1. The shell is complaint, and modulo bugs in the shell or script, it
will work. This should be the common case.
2. The shell is not compliant, and the system is misconfigured.
-- Tom Rini (TR1265) http://gate.crashing.org/~trini/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/