From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Ian Abbott <abbotti@mev.co.uk>
Cc: ptxdist <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] /bin/sh link setting incompatibility when bash and dash installed
Date: Mon, 13 May 2024 08:29:38 +0200 [thread overview]
Message-ID: <ZkGzUufwFsW2TtnB@pengutronix.de> (raw)
In-Reply-To: <3f9ca817-92d7-4e8a-84c5-9756f3197afc@mev.co.uk>
On Wed, Apr 24, 2024 at 03:49:06PM +0100, Ian Abbott wrote:
> Hi,
>
> Currently, the Kconfig option for BASH_SH (which causes /usr/bin/sh to be
> linked to bash) is as follows:
>
> config BASH_SH
> bool
> default BUSYBOX = n || BUSYBOX_SH_IS_NONE
>
> However, if DASH_LINK_SH is enabled, that will cause /usr/bin/sh to be
> linked to dash, resulting in a conflict.
>
> I suppose the most robust fix would be to add a prompt to allow BASH_SH to
> be configured manually. I'm not sure if the default should be changed to
> `default (BUSYBOX = n || BUSYBOX_SH_IS_NONE) && DASH_LINK_SH = n`. If both
> dash and bash are installed, it is likely that dash would be used as the
> system shell and bash would be used as the interactive shell.
Imho, having both bash and dash only makes sense if /bin/sh is dash. So I
think changing the default as suggested above is the correct fix.
Michael
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2024-05-13 6:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 14:49 Ian Abbott
2024-05-13 6:29 ` Michael Olbrich [this message]
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=ZkGzUufwFsW2TtnB@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=abbotti@mev.co.uk \
--cc=ptxdist@pengutronix.de \
/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