From: Timur Tabi <timur@freescale.com>
To: Willy Tarreau <w@1wt.eu>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
Mark Rustad <mrustad@gmail.com>, Sam Ravnborg <sam@ravnborg.org>,
Roland Kuhn <rkuhn@e18.physik.tu-muenchen.de>,
linux-kernel@vger.kernel.org, viro@ZenIV.linux.org.uk
Subject: Re: Why use /bin/sh in kernel build system?
Date: Tue, 29 Apr 2008 17:40:01 -0500 [thread overview]
Message-ID: <4817A3C1.1020908@freescale.com> (raw)
In-Reply-To: <20080429222456.GM8474@1wt.eu>
Willy Tarreau wrote:
> Hint: not every joe user may install bash into /bin... That's why we
> see some scripts begin with "/usr/bin/env bash" as there are less
> systems without env in /usr/bin than systems without bash in /bin (or
> at all).
I agree that #!/bin/bash is a bad idea. I think the easiest, and maybe the
best, approach is to fix shell issue one-by-one. The one I found was easily
fixed by Al Viro's here-document change.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2008-04-29 22:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-28 1:34 cross-compiling on OS X, make menuconfig fails timur
2008-04-28 1:51 ` Tony Breeds
2008-04-29 15:07 ` Timur Tabi
2008-04-29 16:45 ` Sam Ravnborg
2008-04-29 17:20 ` Al Viro
2008-04-29 18:06 ` Sam Ravnborg
2008-04-30 13:54 ` Timur Tabi
2008-04-30 14:18 ` Sam Ravnborg
2008-05-03 6:55 ` SL Baur
2008-05-03 8:01 ` Sam Ravnborg
2008-05-03 8:40 ` Roland Kuhn
2008-05-03 9:34 ` SL Baur
2008-05-12 13:22 ` Arnd Hannemann
2008-04-28 18:46 ` Roland Kuhn
2008-04-29 14:51 ` Timur Tabi
2008-04-29 16:45 ` Sam Ravnborg
2008-04-29 16:48 ` Al Viro
2008-04-29 20:27 ` Why use /bin/sh in kernel build system? Mark Rustad
2008-04-29 21:41 ` Alexey Dobriyan
2008-04-29 22:24 ` Willy Tarreau
2008-04-29 22:40 ` Timur Tabi [this message]
2008-04-30 9:42 ` SL Baur
2008-04-30 11:48 ` Jan Engelhardt
2008-04-29 22:46 ` cross-compiling on OS X, make menuconfig fails Bernd Petrovitsch
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=4817A3C1.1020908@freescale.com \
--to=timur@freescale.com \
--cc=adobriyan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mrustad@gmail.com \
--cc=rkuhn@e18.physik.tu-muenchen.de \
--cc=sam@ravnborg.org \
--cc=viro@ZenIV.linux.org.uk \
--cc=w@1wt.eu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.