From: ChenQi <Qi.Chen@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: nfs-utils does NOT rdepend on bash
Date: Tue, 22 Apr 2014 14:02:34 +0800 [thread overview]
Message-ID: <535605FA.6080905@windriver.com> (raw)
In-Reply-To: <5352B5E0.3080509@topic.nl>
On 04/20/2014 01:44 AM, Mike Looijmans wrote:
> To my surprise, a megabyte sized package "bash" was installed on
> target when I installed nfs-utils to start the NFS server.
>
> Commit 664ae3dc52fd7fc8c6f64e6cf5e70f97dedd332d claims the package
> needs bash.
>
> It's simply not true. It does not require bash at all, it runs just
> fine with busybox's ash shell for example.
>
How about the start-statd script?
It begins with '#!/bin/bash -p'.
If you de-bash it, I think we can remove the dependency.
//Chen Qi
> I don't understand the reasoning behind that commit. There's nothing
> in nfs-utils that really needs bash, it runs fine without it.
>
>
>
> Also, there is an error in the startup script, I can submit a patch
> for that if you like. The script is needlessly complex too.
>
>
next prev parent reply other threads:[~2014-04-22 6:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-19 17:44 nfs-utils does NOT rdepend on bash Mike Looijmans
2014-04-22 6:02 ` ChenQi [this message]
2014-04-22 6:10 ` Mike Looijmans
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=535605FA.6080905@windriver.com \
--to=qi.chen@windriver.com \
--cc=openembedded-core@lists.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