[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070623152313.GP19904@flower.upol.cz>
Date: Sat, 23 Jun 2007 17:23:13 +0200
From: Oleg Verych <olecom@...wer.upol.cz>
To: Andi Kleen <ak@...e.de>
Cc: Arkadiusz Miskiewicz <arekm@...en.pl>,
Randy Dunlap <randy.dunlap@...cle.com>,
lkml <linux-kernel@...r.kernel.org>, akpm@...ux-foundation.org
Subject: Re: NAK (bashizm in the /bin/sh script): [PATCH v3] doc/oops-tracing: add Code: decode info
On Sat, Jun 23, 2007 at 03:17:27PM +0200, Andi Kleen wrote:
> On Saturday 23 June 2007 13:09, Arkadiusz Miskiewicz wrote:
> > On Saturday 23 of June 2007, Andi Kleen wrote:
> > > Here's a nickel. Get yourself a real shell.
> >
> > POSIX compilant shell isn't real shell?
>
> In this case it's not good enough. We're not writing POSIX portable software
> here, but Linux software where /bin/sh is /bin/bash. Similar to the Linux
> kernel which is not written in portable ISO C.
Technical reply about my disagreement.
It's a problem more like "it's broken, but somebody use this in the
source tree". Good example is if "someone uses page_mapping on a slab
page" and have oops with SLUB:
Message-ID: <Pine.LNX.4.64.0706221531520.19704@...roedinger.engr.sgi.com>
Archived-At: <http://permalink.gmane.org/gmane.linux.kernel/546758>
Thus, if one doesn't know what `#!/bin/sh' really is, don't
"syntax error" with possible another sh[ell]. In the Linux build system
$(CONFIG_SHELL) currently is bash, but that's only in the kbuild *now*.
Hope that clarifies.
____
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists