From: Oleg Verych <olecom@flower.upol.cz>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Andi Kleen <ak@suse.de>, lkml <linux-kernel@vger.kernel.org>,
<akpm@linux-foundation.org>
Subject: NAK (bashizm in the /bin/sh script): [PATCH v3] doc/oops-tracing: add Code: decode info
Date: Sat, 23 Jun 2007 10:34:59 +0200 [thread overview]
Message-ID: <E1I2159-0005AH-DS@flower> (raw)
In-Reply-To: <20070622132810.3c758590.randy.dunlap@oracle.com>
* From: Randy Dunlap
* Newsgroups: linux.kernel
* Date: Fri, 22 Jun 2007 13:28:10 -0700
* Organization: Oracle Linux Eng.
[]
> --- /dev/null
> +++ linux-2.6.22-rc5/scripts/decodecode
> @@ -0,0 +1,47 @@
> +#!/bin/sh
> +# Disassemble the Code: line in Linux oopses
> +# usage: decodecode < oops.file
|-*- sh = dash -*-
flower:-$ <kernelOops.txt sh decodecode
Jun 18 22:05:11 localhost kernel: Code: 00 00 00 eb 1b 6b 4e 38 05 89 ca 03 53 \
1c 4a 89 d0 31 d2 f7 f1 89 da 89 c1 89 f0 e8 83 ed ff ff e8 26 af 12 00 8b 76 6\
4 83 ee 64 <8b> 46 64 0f 18 00 90 81 fe 14 5c 37 c0 0f 85 70 ff ff ff b8 84
decodecode: 31: Syntax error: Bad substitution
flower:-$
|-*-
Or you are writing for "#!/bin/bash", or i can help optimize and make
this script "sh" compatible.
NAK.
--
frenzy
-o--=O`C
#oo'L O
<___=E M
next prev parent reply other threads:[~2007-06-23 8:22 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 ` Oleg Verych [this message]
2007-06-23 11:00 ` NAK (bashizm in the /bin/sh script): " 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
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=E1I2159-0005AH-DS@flower \
--to=olecom@flower.upol.cz \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
/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