Actually /bin/sh depends on the distro / implementation. On most it is a link to the intended dominant shell. On Ubuntu -> dash on debian ->bash on fedora/redhat/centos -> bash. It is always best to use the interpreter designator to directly invoke the intended interpreter for your script.
#!/bin/bash #!/bin/dash #!/bin/tcsh #!/bin/ksh #!/usr/bin/perl etc depending upon the script On Thu, Feb 10, 2011 at 8:09 PM, Jeremy <[email protected]> wrote: > On 11-02-10 05:27 PM, Jerome Oufella wrote: >>> >>> On 11-02-10 04:01 PM, Jimmy wrote: >>>> >>>> make sure you have bash installed >>>> and that bin/bash is not a symlink to something else... >> >> You need to choose what language you are scripting in. >> >> /bin/sh implements the posix bourne shell, while /bin/bash actually gives >> you all the rest but the kitchen sink. >> >> Posix gives you portability and consistency across platforms and system >> releases. Bash, however, has different features in each new versions. >> >> /bin/dash implements (and documents) a strict posix shell, so if you stick >> to what it provides, you will be safe whatever implementation you use >> (dash >> or bash). >> >> Good luck :-) > > Important info on which I was not totally clear. Thank you for the > explanation. > > Jeremy > _______________________________________________ > mlug mailing list > [email protected] > https://listes.koumbit.net/cgi-bin/mailman/listinfo/mlug-listserv.mlug.ca > -- ___..___........__.......__ ...|....|__/....|...|......|...|__| ...|....|.....\...|...|__..|...|....| "You must be the change you wish to see in the world." Mohandas K Gandhi _______________________________________________ mlug mailing list [email protected] https://listes.koumbit.net/cgi-bin/mailman/listinfo/mlug-listserv.mlug.ca
