[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070623135119.GO19904@flower.upol.cz>
Date: Sat, 23 Jun 2007 15:51:19 +0200
From: Oleg Verych <olecom@...wer.upol.cz>
To: Willy Tarreau <w@....eu>
Cc: Andi Kleen <ak@...e.de>, Arkadiusz Miskiewicz <arekm@...en.pl>,
Randy Dunlap <randy.dunlap@...cle.com>,
lkml <linux-kernel@...r.kernel.org>, akpm@...ux-foundation.org
Subject: [OT]Re: NAK (bashizm in the /bin/sh script): [PATCH v3] doc/oops-tracing: add Code: decode info
On Sat, Jun 23, 2007 at 03:26:26PM +0200, Willy Tarreau wrote:
> 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.
I disagree.
> Well, it can also be zsh or pdksh, but I suspect that the code is valid on
> them too.
Not for the latter:
|-*- pdksh -*-
flower:-$ <kernelOops.txt>/dev/null pdksh decodecode
decodecode[40]: : bad substitution
flower:-$
|-*-
I don't want to go further with this OT, just last thing.
It's GNU BaSH *BUG* (addition to being big and slow), if it can't switch
off it's expressly undocumented extentions while run as `/bin/sh'.
____
-
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