From: Robert Yang <liezhi.yang@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] sanity.bbclass: check /bin/sh is dash or bash
Date: Mon, 29 Jun 2015 11:06:38 +0800 [thread overview]
Message-ID: <5590B63E.70009@windriver.com> (raw)
In-Reply-To: <CAJTo0LbVU3u8dustr-dv6ySQmAyU6nR2c6r7=cPP-9GdRFeZsg@mail.gmail.com>
On 06/26/2015 09:10 PM, Burton, Ross wrote:
>
> On 26 June 2015 at 07:23, Robert Yang <liezhi.yang@windriver.com
> <mailto:liezhi.yang@windriver.com>> wrote:
>
> The build would fail when /bin/sh links to ksh or csh, we only test dash
> and bash AFAIK.
>
>
> csh definitely isn't a suitable candidate for /bin/sh, and I doubt ksh is too.
> Are people really doing this? They're just wrong... I seriously doubt Linux
> would boot with /bin/sh->csh and ksh would be asking for trouble.
Hi Ross,
Yes, Ubuntu would not boot well when /bin/sh -> ksh or csh, I just took
them as an example, I think that we only test on bash or dash, so I
think that this checking can reduce the potential errors, and I think
that we also need check SHELL, I will test and send another patch.
// Robert
>
> Was this a real world problem, or a hypothetical problem?
>
> Ross
next prev parent reply other threads:[~2015-06-29 3:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 6:23 [PATCH 0/1] sanity.bbclass: check /bin/sh is dash or bash Robert Yang
2015-06-26 6:23 ` [PATCH 1/1] " Robert Yang
2015-06-26 12:47 ` Christopher Larson
2015-06-26 12:56 ` Richard Purdie
2015-06-26 13:10 ` Burton, Ross
2015-06-29 3:06 ` Robert Yang [this message]
2015-06-29 8:16 ` Robert Yang
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=5590B63E.70009@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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