On 10/6/11 2:54 PM, Len Giambrone wrote:
> Bash Version: 4.1
> Patch Level: 10
> Release Status: release
>
> Description:
> The man page states:
>
>SHELLOPTS
> A colon-separated list of enabled shell options. Each word in
> the list is a valid argument for
> On Mon, Oct 10, 2011 at 11:06:16AM -0400, Len Giambrone wrote:
> > I understand that. But if you change all your scripts to use
> >
> > #!/bin/bash
> > instead of
> > #!/bin/sh
> >
> > your scripts will fail when bash isn't installed.
>
> If you use bash features in your script, then you must
On Mon, Oct 10, 2011 at 11:06:16AM -0400, Len Giambrone wrote:
> I understand that. But if you change all your scripts to use
>
> #!/bin/bash
> instead of
> #!/bin/sh
>
> your scripts will fail when bash isn't installed.
If you use bash features in your script, then you must ensure that the
scr
I understand that. But if you change all your scripts to use
#!/bin/bash
instead of
#!/bin/sh
your scripts will fail when bash isn't installed.
-Len
On Oct 10, 2011, at 8:24 AM, Greg Wooledge wrote:
On Thu, Oct 06, 2011 at 02:54:56PM -0400, Len Giambrone wrote:
Many people now use sh and b
On Thu, Oct 06, 2011 at 02:54:56PM -0400, Len Giambrone wrote:
> Many people now use sh and bash interchangeably.
That is wrong. Those people need to learn that sh and bash are NOT
interchangeable.
