The path of the shell is the only substantial difference I can see between sh
and bash
- if you look carefully at /bin/sh on OS X, it's really bash (perhaps compiled with a flag to make it know it's filling in for sh since the binaries are slightly different).
mac me$ md5 /bin/sh /bin/bash
MD5 (/bin/sh) = 2cc3c26641112c1bd0173f396b7d7662
MD5 (/bin/bash) = 5d7583d80e5314ac844eedc6d68c6cd7
mac me $ ls -l /bin/sh /bin/bash
-r-xr-xr-x 1 root wheel 628496 Aug 28 02:02 /bin/bash
-r-xr-xr-x 1 root wheel 632672 Aug 28 02:02 /bin/sh
mac me $ sh --version
GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin15)
Copyright (C) 2007 Free Software Foundation, Inc.
manoa mac me $ bash --version
GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin15)
Copyright (C) 2007 Free Software Foundation, Inc.
So, if somehow iTerm is barfing on /bin/sh even though it's already bash, you could change shells. I'd say running things from your user with sudo -H
is always better than enabling root, but that's a discussion for another thread:
If you want to test the change:
sudo bash
. – David Anderson Oct 10 '15 at 14:53sudo -s
(which uses the value of$SHELL
to spawn a root shell) – nohillside Oct 10 '15 at 14:57sh
(because you currently get aYour shell, /bin/sh, is not supported yet. Only tcsh, zsh, bash, and fish are supported. Sorry!
error when following the instructions on the iTerm site), please ask a new question for this (or consider analyzing the code of the curl'ed scripts and adapting it forsh
the entry exam for running root shells :-)). – nohillside Oct 10 '15 at 15:27