Hi, Botao 

You're right, if we use busybox as our default shell and command line tool, it will be better. But there may exist a standard for any Android system in my opinion. Currently, the third party components are playing an "optional" role, not default. I'm not sure change this status whether breaks some policies in AOSP or any other communities.

what about to do like this:

1. make a directory /system/busybox

2. create sub command link files in that directory

    # the busybox command itself can also be installed in /system/bin directory.

3. if we want to use the commands of busybox, then we can change the path in our shell like:

    export PATH="/data/busybox:${PATH}"

4. if we don't like use the commands of busybox, we can do as now.

this will not change the "optional" role i think.

Thanks,

Yongqin Liu

I will discuss this topic with some guys in future, but we still use Android's own "unfriendly" command line tools by default at present.

Thank you!


BR
Botao Sun

On Thursday, September 22, 2011 11:25 AM, yong qin wrote:

Hi, botao

I have just use the attachment file to take a try with images of linaro-android-leb-panda build#252.

the busybox and some it's sub commands works well.

But in my opinion it's better to create link for each sub command at installation.

Then we just need to add the link files' parent path to the environment PATH, and can simply use the sub command.

Not as now should use the busybox command at the front.

Now if we want use the grep command, we need specify as "busybox grep" but not only  "grep".

Especially, when I write a shell including if sentence(as sentence in the attachment file), we need to write like this:

if /system/bin/busybox [ $# -lt 1 ]; then

It's a little not convenient I think.

Thanks,

Yongqin Liu

On 21 September 2011 17:40, Botao Sun <botao.sun@linaro.org> wrote:

Hi Yongqin,

Just test it can be run or not. Run some basic commands, such like busybox top, busybox vi, busybox ps | busybox grep XXX..., something like that.

I don't have test cases at my side. And this is the first time I integrated the entire busybox source code to our Android platform. I would like to be ensure it works on every board first.

Thanks.

On Wed, Sep 21, 2011 at 5:33 PM, Fathi Boudra <fathi.boudra@linaro.org> wrote:

Foward to Botao as Yongqin replied to me only.

---------- Forwarded message ----------
From: yong qin <yongqin.liu@linaro.org>
Date: 21 September 2011 12:29
Subject: Re: Hi guys, could you help me to test busybox on your board?
To: Fathi Boudra <fathi.boudra@linaro.org>


Hi, Botao
What test would you like to do?
Or do you have any test cases or test programs?
Thanks
Yongqin Liu

On 21 September 2011 16:44, Fathi Boudra <fathi.boudra@linaro.org> wrote:
>
> ---------- Forwarded message ----------
> From: Botao Sun <botao.sun@linaro.org>
> Date: 21 September 2011 11:42
> Subject: Hi guys, could you help me to test busybox on your board?
>
> Hi,
>
> The busybox source code has been integrated to Linaro Android platform
> for all boards, so I'd like to ask help from you to test it. I have
> tested it on my Origen board, and it works well.
>
> Thank you!
>
>
> BR
> Botao Sun
>
> _______________________________________________
> linaro-dev mailing list
> linaro-dev@lists.linaro.org
> http://lists.linaro.org/mailman/listinfo/linaro-dev

--
Fathi Boudra
Linaro Release Manager | Validation Project Manager
Linaro.org | Open source software for ARM SoCs