Re: NAK (bashizm in the /bin/sh script): [PATCH v3] doc/oops-tracing: add Code: decode info

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Sean
Date: Saturday, June 23, 2007 - 7:38 am

On Sat, 23 Jun 2007 15:17:27 +0200
Andi Kleen <ak@suse.de> wrote:


There's no rule that says /bin/sh is always /bin/bash.  What Novell
distributions do does not translate to all of "Linux".  If you are writing
scripts that rely on bash then "#!/bin/bash" is the appropriate way to
document that and give it the best chance of working portably.

Sean
-
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[PATCH] doc/oops-tracing: add Code: decode info, Randy Dunlap, (Thu Jun 21, 10:51 pm)
Re: [PATCH] doc/oops-tracing: add Code: decode info, Andi Kleen, (Fri Jun 22, 7:26 am)
[PATCH v2] doc/oops-tracing: add Code: decode info, Randy Dunlap, (Fri Jun 22, 9:44 am)
Re: [PATCH v2] doc/oops-tracing: add Code: decode info, Andi Kleen, (Fri Jun 22, 10:23 am)
Re: [PATCH v2] doc/oops-tracing: add Code: decode info, Randy Dunlap, (Fri Jun 22, 11:25 am)
[PATCH v3] doc/oops-tracing: add Code: decode info, Randy Dunlap, (Fri Jun 22, 1:28 pm)
Re: NAK (bashizm in the /bin/sh script): [PATCH v3] doc/oo ..., Arkadiusz Miskiewicz, (Sat Jun 23, 4:09 am)
Re: NAK (bashizm in the /bin/sh script): [PATCH v3] doc/oo ..., Arkadiusz Miskiewicz, (Sat Jun 23, 7:24 am)
Re: NAK (bashizm in the /bin/sh script): [PATCH v3] doc/oo ..., Sean, (Sat Jun 23, 7:38 am)
Re: NAK (bashizm in the /bin/sh script): [PATCH v3] doc/oo ..., Segher Boessenkool, (Sat Jun 23, 8:35 am)
Re: NAK (bashizm in the /bin/sh script): [PATCH v3] doc/oo ..., Arne Georg Gleditsch, (Tue Jun 26, 3:50 am)
Re: NAK (bashizm in the /bin/sh script): [PATCH v3] doc/oo ..., Julio M. Merino Vidal, (Tue Jun 26, 10:25 am)
Re: NAK (bashizm in the /bin/sh script): [PATCH v3] doc/oo ..., Arne Georg Gleditsch, (Thu Jun 28, 12:58 am)