From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: [PATCH] bash: add alternative configuration for bin/sh -> /bin/bash
Date: Wed, 01 Apr 2009 19:01:55 +0200 [thread overview]
Message-ID: <gr06m3$63e$1@ger.gmane.org> (raw)
In-Reply-To: <b6ebd0a50904010952n6ce5b7b2g793f79ada1e6dcc1@mail.gmail.com>
On 01-04-09 18:52, Chris Larson wrote:
> On Wed, Apr 1, 2009 at 9:26 AM, Tim Harvey<tharvey@irobot.com> wrote:
>> Chris Larson wrote:
>>>
>>> Be very careful with this. Specifically, be sure to thoroughly test
>>> installing bash onto a system that currently has busybox, and the
>>> upgrade paths for both busybox and bash. You never want to get into a
>>> state, due to pre/post rm/install script execution order, where
>>> /bin/sh doesn't exist. If that happens, you won't be able to execute
>>> the next script to fix it :)
>>>
>>
>> in my case, I have both bash and busybox installed and I want bash to take
>> priority as the /bin/sh which it otherwise does not.
>>
>> attempting to remove the package that contains your shell is something you
>> need to be careful as anyway.
>>
>> This seems to me to be a prime example of where alternatives should be used?
>
> You missed my point, it seems. I was talking about
> update-alternatives. Depending on how update-alternatives is
> implemented, there could be issues similar to what I mentioned in the
> previous email. Consider: if it uses system(), which calls /bin/sh,
> to remove the old /bin/sh link, and then calls system() again to
> create the new, it will fail. Speculation, but again, it's something
> you always need to keep in mind if you're messing with /bin/sh in any
> way.
IIRC our default u-a is a shell script, the other version is a perl script.
Correct me if I'm wrong, it has been some years since I looked at it :)
regards,
Koen
next prev parent reply other threads:[~2009-04-01 17:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 20:50 [PATCH] bash: add alternative configuration for bin/sh -> /bin/bash Tim Harvey
2009-03-27 21:02 ` Chris Larson
2009-03-27 22:51 ` Koen Kooi
2009-04-01 16:26 ` Tim Harvey
2009-04-01 16:52 ` Chris Larson
2009-04-01 17:01 ` Koen Kooi [this message]
2009-04-01 17:12 ` Chris Larson
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='gr06m3$63e$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.org \
/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