public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Matthieu CASTET <castet.matthieu@free.fr>, linux-kernel@vger.kernel.org
Subject: Re: NAK (bashizm in the /bin/sh script): [PATCH v3] doc/oops-tracing: add Code: decode info
Date: Tue, 26 Jun 2007 12:24:15 +0200	[thread overview]
Message-ID: <20070626102414.GU27862@lug-owl.de> (raw)
In-Reply-To: <20070626101639.GB20178@DervishD>

[-- Attachment #1: Type: text/plain, Size: 915 bytes --]

On Tue, 2007-06-26 12:16:39 +0200, DervishD <lkml@dervishd.net> wrote:
>  * Matthieu CASTET <castet.matthieu@free.fr> dixit:
> > On Sat, 23 Jun 2007 10:43:03 -0700, Randy Dunlap wrote:
> > 
> > > OTOH, you also didn't supply a patch.  If you do this, I'll be glad to
> > > consider it.  If I can read it, that is.
> > 
> > "s|/bin/sh|/bin/bash" is so hard to do ?
> 
>     Given that it happens too with "ldd", it really *is* that hard. I
> don't know why still people think that /bin/sh is always /bin/bash. If
> they want/need bash, that's ok to me, I will have it installed for such
> tasks, but they should call it "#!/bin/bash".

...or "#!/usr/bin/env bash" for what it's worth...  The same for plain
`sh'.

MfG, JBG

-- 
      Jan-Benedict Glaw      jbglaw@lug-owl.de              +49-172-7608481
 Signature of:                      http://perl.plover.com/Questions.html
 the second  :

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-06-26 10:24 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-22  5:51 [PATCH] doc/oops-tracing: add Code: decode info Randy Dunlap
2007-06-22 14:26 ` Andi Kleen
2007-06-22 16:44   ` [PATCH v2] " Randy Dunlap
2007-06-22 17:23     ` Andi Kleen
2007-06-22 18:25       ` Randy Dunlap
2007-06-22 21:29         ` Andi Kleen
2007-06-22 20:28       ` [PATCH v3] " Randy Dunlap
2007-06-23  8:34         ` NAK (bashizm in the /bin/sh script): " Oleg Verych
2007-06-23 11:00           ` Andi Kleen
2007-06-23 11:09             ` Arkadiusz Miskiewicz
2007-06-23 13:17               ` Andi Kleen
2007-06-23 13:26                 ` Willy Tarreau
2007-06-23 13:51                   ` [OT]Re: " Oleg Verych
2007-06-23 13:47                 ` Björn Steinbrink
2007-06-23 14:24                 ` Arkadiusz Miskiewicz
2007-06-23 14:32                 ` Alan Cox
2007-06-23 14:34                   ` Andi Kleen
2007-06-23 14:48                     ` Alan Cox
2007-06-23 15:35                   ` Segher Boessenkool
2007-06-23 14:38                 ` Sean
2007-06-23 15:23                 ` Oleg Verych
2007-06-23 17:43           ` Randy Dunlap
2007-06-23 17:56             ` Andrew Morton
2007-06-23 20:54               ` Adrian Bunk
2007-06-23 21:04                 ` Randy Dunlap
2007-06-23 20:24             ` Matthieu CASTET
2007-06-26 10:16               ` DervishD
2007-06-26 10:24                 ` Jan-Benedict Glaw [this message]
2007-06-26 15:33                   ` DervishD
2007-06-26 16:04                     ` Randy Dunlap
2007-06-26 17:03                       ` DervishD
2007-06-26 10:50             ` Arne Georg Gleditsch
2007-06-26 15:36               ` DervishD
2007-06-26 17:19               ` Randy Dunlap
2007-06-26 17:25                 ` Julio M. Merino Vidal
2007-06-26 17:56                   ` Randy Dunlap
2007-06-28  7:58                     ` Arne Georg Gleditsch

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070626102414.GU27862@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=castet.matthieu@free.fr \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox