Re: bash vs sh in scripts

2005-12-07 Thread Eric Blake
> > /bin/sh should exist and be a hard-link to /bin/bash. If this is not > the case you have an installation problem. The bash postinstall script > should ensure this. Actually, it should be a copy rather than a hard link, since hard links can't be broken to be upgraded while the postinstall sc

Re: bash vs sh in scripts

2005-12-07 Thread Brian Dessent
David Arnstein wrote: > Some cygwin packages install shell scripts that begin with the line > #!/bin/sh > The latest example is the smartd script that smartmontools installs in > /etc/rc.d/init.d. But there are many others. This seems to be standard > Linux usage. > > On some of my PCs, t

bash vs sh in scripts

2005-12-07 Thread David Arnstein
Some cygwin packages install shell scripts that begin with the line #!/bin/sh The latest example is the smartd script that smartmontools installs in /etc/rc.d/init.d. But there are many others. This seems to be standard Linux usage. On some of my PCs, this causes the shell script to fail.