Buildroot busybox limited command set

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
0
down vote

favorite
1












I'm using the raspberrypi0_defconfig to create an image for the Raspberry Pi Zero-W. I'm having a number of issues, but the first one I want to address is why my Busybox shell has so little build in commands?



# help
Built-in commands:
------------------
. : [ [[ alias bg break cd chdir command continue echo eval exec
exit export false fg getopts hash help history jobs kill let
local printf pwd read readonly return set shift source test times
trap true type ulimit umask unalias unset wait


For example, at the very least I'd like to have the ls command added.
In the menuconfig I cannot find these options for Busybox, however, there is a configuration file listed, pointing to package/busybox/busybox.config.



This file has a header that suggest it's configurable somewhere (make config seems to be a text-only version of make menuconfig):



#
# Automatically generated make config: don't edit
# Busybox version: 1.27.1
# Sun Jul 30 15:27:03 2017
#


and among other things has



CONFIG_LS=y


So, the two questions are:



  • Why don't I have build-in commands that seem to be configured?

  • Where (preferably in menuconfig?) can I configure Busybox?









share|improve this question





















  • Can you not build Busybox from source?
    – Raman Sailopal
    Oct 3 '17 at 10:12










  • I think buildroot does that..
    – svenema
    Oct 3 '17 at 15:39














up vote
0
down vote

favorite
1












I'm using the raspberrypi0_defconfig to create an image for the Raspberry Pi Zero-W. I'm having a number of issues, but the first one I want to address is why my Busybox shell has so little build in commands?



# help
Built-in commands:
------------------
. : [ [[ alias bg break cd chdir command continue echo eval exec
exit export false fg getopts hash help history jobs kill let
local printf pwd read readonly return set shift source test times
trap true type ulimit umask unalias unset wait


For example, at the very least I'd like to have the ls command added.
In the menuconfig I cannot find these options for Busybox, however, there is a configuration file listed, pointing to package/busybox/busybox.config.



This file has a header that suggest it's configurable somewhere (make config seems to be a text-only version of make menuconfig):



#
# Automatically generated make config: don't edit
# Busybox version: 1.27.1
# Sun Jul 30 15:27:03 2017
#


and among other things has



CONFIG_LS=y


So, the two questions are:



  • Why don't I have build-in commands that seem to be configured?

  • Where (preferably in menuconfig?) can I configure Busybox?









share|improve this question





















  • Can you not build Busybox from source?
    – Raman Sailopal
    Oct 3 '17 at 10:12










  • I think buildroot does that..
    – svenema
    Oct 3 '17 at 15:39












up vote
0
down vote

favorite
1









up vote
0
down vote

favorite
1






1





I'm using the raspberrypi0_defconfig to create an image for the Raspberry Pi Zero-W. I'm having a number of issues, but the first one I want to address is why my Busybox shell has so little build in commands?



# help
Built-in commands:
------------------
. : [ [[ alias bg break cd chdir command continue echo eval exec
exit export false fg getopts hash help history jobs kill let
local printf pwd read readonly return set shift source test times
trap true type ulimit umask unalias unset wait


For example, at the very least I'd like to have the ls command added.
In the menuconfig I cannot find these options for Busybox, however, there is a configuration file listed, pointing to package/busybox/busybox.config.



This file has a header that suggest it's configurable somewhere (make config seems to be a text-only version of make menuconfig):



#
# Automatically generated make config: don't edit
# Busybox version: 1.27.1
# Sun Jul 30 15:27:03 2017
#


and among other things has



CONFIG_LS=y


So, the two questions are:



  • Why don't I have build-in commands that seem to be configured?

  • Where (preferably in menuconfig?) can I configure Busybox?









share|improve this question













I'm using the raspberrypi0_defconfig to create an image for the Raspberry Pi Zero-W. I'm having a number of issues, but the first one I want to address is why my Busybox shell has so little build in commands?



# help
Built-in commands:
------------------
. : [ [[ alias bg break cd chdir command continue echo eval exec
exit export false fg getopts hash help history jobs kill let
local printf pwd read readonly return set shift source test times
trap true type ulimit umask unalias unset wait


For example, at the very least I'd like to have the ls command added.
In the menuconfig I cannot find these options for Busybox, however, there is a configuration file listed, pointing to package/busybox/busybox.config.



This file has a header that suggest it's configurable somewhere (make config seems to be a text-only version of make menuconfig):



#
# Automatically generated make config: don't edit
# Busybox version: 1.27.1
# Sun Jul 30 15:27:03 2017
#


and among other things has



CONFIG_LS=y


So, the two questions are:



  • Why don't I have build-in commands that seem to be configured?

  • Where (preferably in menuconfig?) can I configure Busybox?






busybox buildroot






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Oct 3 '17 at 9:07









svenema

799




799











  • Can you not build Busybox from source?
    – Raman Sailopal
    Oct 3 '17 at 10:12










  • I think buildroot does that..
    – svenema
    Oct 3 '17 at 15:39
















  • Can you not build Busybox from source?
    – Raman Sailopal
    Oct 3 '17 at 10:12










  • I think buildroot does that..
    – svenema
    Oct 3 '17 at 15:39















Can you not build Busybox from source?
– Raman Sailopal
Oct 3 '17 at 10:12




Can you not build Busybox from source?
– Raman Sailopal
Oct 3 '17 at 10:12












I think buildroot does that..
– svenema
Oct 3 '17 at 15:39




I think buildroot does that..
– svenema
Oct 3 '17 at 15:39










1 Answer
1






active

oldest

votes

















up vote
2
down vote



accepted










BusyBox help apparently doesn't display every available command. Ls, and presumably other commands were in my case actually available.



The default consoles settings prevented keyboard input to come through correctly in some cases, resulting in an erratic shell behaviour, which caused it to seem commands were not present.



After changing the default settings TTY from "console" to "tty1" and the baudrate to "38400" everything, including the ls command worked fine.






share|improve this answer




















    Your Answer







    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "106"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    convertImagesToLinks: false,
    noModals: false,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













     

    draft saved


    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f395787%2fbuildroot-busybox-limited-command-set%23new-answer', 'question_page');

    );

    Post as a guest






























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    2
    down vote



    accepted










    BusyBox help apparently doesn't display every available command. Ls, and presumably other commands were in my case actually available.



    The default consoles settings prevented keyboard input to come through correctly in some cases, resulting in an erratic shell behaviour, which caused it to seem commands were not present.



    After changing the default settings TTY from "console" to "tty1" and the baudrate to "38400" everything, including the ls command worked fine.






    share|improve this answer
























      up vote
      2
      down vote



      accepted










      BusyBox help apparently doesn't display every available command. Ls, and presumably other commands were in my case actually available.



      The default consoles settings prevented keyboard input to come through correctly in some cases, resulting in an erratic shell behaviour, which caused it to seem commands were not present.



      After changing the default settings TTY from "console" to "tty1" and the baudrate to "38400" everything, including the ls command worked fine.






      share|improve this answer






















        up vote
        2
        down vote



        accepted







        up vote
        2
        down vote



        accepted






        BusyBox help apparently doesn't display every available command. Ls, and presumably other commands were in my case actually available.



        The default consoles settings prevented keyboard input to come through correctly in some cases, resulting in an erratic shell behaviour, which caused it to seem commands were not present.



        After changing the default settings TTY from "console" to "tty1" and the baudrate to "38400" everything, including the ls command worked fine.






        share|improve this answer












        BusyBox help apparently doesn't display every available command. Ls, and presumably other commands were in my case actually available.



        The default consoles settings prevented keyboard input to come through correctly in some cases, resulting in an erratic shell behaviour, which caused it to seem commands were not present.



        After changing the default settings TTY from "console" to "tty1" and the baudrate to "38400" everything, including the ls command worked fine.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Oct 3 '17 at 18:41









        svenema

        799




        799



























             

            draft saved


            draft discarded















































             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f395787%2fbuildroot-busybox-limited-command-set%23new-answer', 'question_page');

            );

            Post as a guest













































































            Popular posts from this blog

            How to check contact read email or not when send email to Individual?

            Displaying single band from multi-band raster using QGIS

            How many registers does an x86_64 CPU actually have?