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

[Randy Dunlap]

On Tue, 26 Jun 2007 17:33:59 +0200 DervishD wrote:

>     Hi Jan :)
> 
>  * Jan-Benedict Glaw <jbglaw@xxxxxxxxxx> dixit:
> > On Tue, 2007-06-26 12:16:39 +0200, DervishD <lkml@xxxxxxxxxxxx> wrote:
> > >     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'.
> 
>     The "env" solution is a bit of a problem, too. Not always "env" is
> installed in /usr/bin, but in /bin, so it is available even if /usr is
> not still mounted. But /bin/sh is pretty standard (as it should be
> /bin/bash, anyway), and it's only two chars shorter than the correct
> "/bin/bash". No idea why it is not fixed.

because nobody sent a patch yet?

but I'll get around tuit.

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/