On Tue, Nov 13, 2018 at 05:29:42PM +0100, Service wrote: > Repeat-By: > Under Windows 10, WSL.
Then why did you send this to a debian.org address? > Start "bash", terminal with shell pops up. > 2. This does not work: > > # Put the above commands into a script, say check.sh > # Run with: /bin/sh < check.sh > # Or : /bin/sh ./check.sh In both of these cases, you're explicitly calling /bin/sh rather than bash. So you are not using bash's builtin [. You are using WSL's sh's builtin [ command. You might start by identifying which shell WSL uses as its sh. > # Or : /usr/bin/env ./check.sh In this case, it would use the shebang line of check.sh to decide which shell to run. However, I suspect you did not include a shebang line at all. In that case, /usr/bin/env will decide how to handle the exec format error. It might decide to spawn sh for you, in which case this would explain why the result matches the first two results.
