busybox in embedded linux shows “applet not found”












5















I compiled busybox myself,and I put it in our embedded linux. But I have some questions.



Question 1:When I try to use some command such as gzip,it prints "gzip: applet not found".While I checked the menuconfig of busybox,I make sure that I've selected "gzip".



Question 2:I used to work with VIM,but busybox just provide VI.So I make a link VIM to VI,but when I typed vim and run it,it also show "vim: applet not found".



Anybody can help me with this problem that "applet not found"? Thank you very much.



PS:I'm confused with the "applet" of busybox,what it is? Like "applet" in java?










share|improve this question

























  • Looks like your shell is not finding busybox in its path. Google "busybox shell path" to find the remedy.

    – UncleO
    Sep 27 '13 at 6:48






  • 1





    First of all, try to execute gzip like "busybox gzip". If it works, then problem is in applet links (symbolic, hard or micro scripts). If not, then gzip applet is likely not compiled into busybox (although it seems that links point to busybox executable because you get "applet not found" message). Applets are commands/utilities supported by busybox.

    – sknaumov
    Sep 27 '13 at 10:37











  • @UncleO oh no,the path is ok,any other command is ok.

    – Ezio
    Sep 30 '13 at 5:20











  • @sknaumov thanks,i tried gzip and success.but when i try "ln busybox vim" and using vim ,it still show "vim: applet not found",how can i solved this?

    – Ezio
    Sep 30 '13 at 5:24






  • 5





    The way busybox work is it looks at it argv[0] parameter which is the name of the symlink; vim in your case. It then does a look-up and it has no applet named vim. You can make a script that does busybox vi and symlink that script to vim. The syntax busybox applet, is another way to select the program; but why not just type vi. An applet in busybox parlance is the emulated program. busybox has base infrastructure (command line parsing, etc) with a main driver file that is an applet emulating the normal program.

    – artless noise
    Sep 30 '13 at 15:21


















5















I compiled busybox myself,and I put it in our embedded linux. But I have some questions.



Question 1:When I try to use some command such as gzip,it prints "gzip: applet not found".While I checked the menuconfig of busybox,I make sure that I've selected "gzip".



Question 2:I used to work with VIM,but busybox just provide VI.So I make a link VIM to VI,but when I typed vim and run it,it also show "vim: applet not found".



Anybody can help me with this problem that "applet not found"? Thank you very much.



PS:I'm confused with the "applet" of busybox,what it is? Like "applet" in java?










share|improve this question

























  • Looks like your shell is not finding busybox in its path. Google "busybox shell path" to find the remedy.

    – UncleO
    Sep 27 '13 at 6:48






  • 1





    First of all, try to execute gzip like "busybox gzip". If it works, then problem is in applet links (symbolic, hard or micro scripts). If not, then gzip applet is likely not compiled into busybox (although it seems that links point to busybox executable because you get "applet not found" message). Applets are commands/utilities supported by busybox.

    – sknaumov
    Sep 27 '13 at 10:37











  • @UncleO oh no,the path is ok,any other command is ok.

    – Ezio
    Sep 30 '13 at 5:20











  • @sknaumov thanks,i tried gzip and success.but when i try "ln busybox vim" and using vim ,it still show "vim: applet not found",how can i solved this?

    – Ezio
    Sep 30 '13 at 5:24






  • 5





    The way busybox work is it looks at it argv[0] parameter which is the name of the symlink; vim in your case. It then does a look-up and it has no applet named vim. You can make a script that does busybox vi and symlink that script to vim. The syntax busybox applet, is another way to select the program; but why not just type vi. An applet in busybox parlance is the emulated program. busybox has base infrastructure (command line parsing, etc) with a main driver file that is an applet emulating the normal program.

    – artless noise
    Sep 30 '13 at 15:21
















5












5








5


3






I compiled busybox myself,and I put it in our embedded linux. But I have some questions.



Question 1:When I try to use some command such as gzip,it prints "gzip: applet not found".While I checked the menuconfig of busybox,I make sure that I've selected "gzip".



Question 2:I used to work with VIM,but busybox just provide VI.So I make a link VIM to VI,but when I typed vim and run it,it also show "vim: applet not found".



Anybody can help me with this problem that "applet not found"? Thank you very much.



PS:I'm confused with the "applet" of busybox,what it is? Like "applet" in java?










share|improve this question
















I compiled busybox myself,and I put it in our embedded linux. But I have some questions.



Question 1:When I try to use some command such as gzip,it prints "gzip: applet not found".While I checked the menuconfig of busybox,I make sure that I've selected "gzip".



Question 2:I used to work with VIM,but busybox just provide VI.So I make a link VIM to VI,but when I typed vim and run it,it also show "vim: applet not found".



Anybody can help me with this problem that "applet not found"? Thank you very much.



PS:I'm confused with the "applet" of busybox,what it is? Like "applet" in java?







linux embedded busybox ramdisk






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Sep 27 '13 at 6:17









Ingo Karkat

134k14152204




134k14152204










asked Sep 27 '13 at 6:02









EzioEzio

5582722




5582722













  • Looks like your shell is not finding busybox in its path. Google "busybox shell path" to find the remedy.

    – UncleO
    Sep 27 '13 at 6:48






  • 1





    First of all, try to execute gzip like "busybox gzip". If it works, then problem is in applet links (symbolic, hard or micro scripts). If not, then gzip applet is likely not compiled into busybox (although it seems that links point to busybox executable because you get "applet not found" message). Applets are commands/utilities supported by busybox.

    – sknaumov
    Sep 27 '13 at 10:37











  • @UncleO oh no,the path is ok,any other command is ok.

    – Ezio
    Sep 30 '13 at 5:20











  • @sknaumov thanks,i tried gzip and success.but when i try "ln busybox vim" and using vim ,it still show "vim: applet not found",how can i solved this?

    – Ezio
    Sep 30 '13 at 5:24






  • 5





    The way busybox work is it looks at it argv[0] parameter which is the name of the symlink; vim in your case. It then does a look-up and it has no applet named vim. You can make a script that does busybox vi and symlink that script to vim. The syntax busybox applet, is another way to select the program; but why not just type vi. An applet in busybox parlance is the emulated program. busybox has base infrastructure (command line parsing, etc) with a main driver file that is an applet emulating the normal program.

    – artless noise
    Sep 30 '13 at 15:21





















  • Looks like your shell is not finding busybox in its path. Google "busybox shell path" to find the remedy.

    – UncleO
    Sep 27 '13 at 6:48






  • 1





    First of all, try to execute gzip like "busybox gzip". If it works, then problem is in applet links (symbolic, hard or micro scripts). If not, then gzip applet is likely not compiled into busybox (although it seems that links point to busybox executable because you get "applet not found" message). Applets are commands/utilities supported by busybox.

    – sknaumov
    Sep 27 '13 at 10:37











  • @UncleO oh no,the path is ok,any other command is ok.

    – Ezio
    Sep 30 '13 at 5:20











  • @sknaumov thanks,i tried gzip and success.but when i try "ln busybox vim" and using vim ,it still show "vim: applet not found",how can i solved this?

    – Ezio
    Sep 30 '13 at 5:24






  • 5





    The way busybox work is it looks at it argv[0] parameter which is the name of the symlink; vim in your case. It then does a look-up and it has no applet named vim. You can make a script that does busybox vi and symlink that script to vim. The syntax busybox applet, is another way to select the program; but why not just type vi. An applet in busybox parlance is the emulated program. busybox has base infrastructure (command line parsing, etc) with a main driver file that is an applet emulating the normal program.

    – artless noise
    Sep 30 '13 at 15:21



















Looks like your shell is not finding busybox in its path. Google "busybox shell path" to find the remedy.

– UncleO
Sep 27 '13 at 6:48





Looks like your shell is not finding busybox in its path. Google "busybox shell path" to find the remedy.

– UncleO
Sep 27 '13 at 6:48




1




1





First of all, try to execute gzip like "busybox gzip". If it works, then problem is in applet links (symbolic, hard or micro scripts). If not, then gzip applet is likely not compiled into busybox (although it seems that links point to busybox executable because you get "applet not found" message). Applets are commands/utilities supported by busybox.

– sknaumov
Sep 27 '13 at 10:37





First of all, try to execute gzip like "busybox gzip". If it works, then problem is in applet links (symbolic, hard or micro scripts). If not, then gzip applet is likely not compiled into busybox (although it seems that links point to busybox executable because you get "applet not found" message). Applets are commands/utilities supported by busybox.

– sknaumov
Sep 27 '13 at 10:37













@UncleO oh no,the path is ok,any other command is ok.

– Ezio
Sep 30 '13 at 5:20





@UncleO oh no,the path is ok,any other command is ok.

– Ezio
Sep 30 '13 at 5:20













@sknaumov thanks,i tried gzip and success.but when i try "ln busybox vim" and using vim ,it still show "vim: applet not found",how can i solved this?

– Ezio
Sep 30 '13 at 5:24





@sknaumov thanks,i tried gzip and success.but when i try "ln busybox vim" and using vim ,it still show "vim: applet not found",how can i solved this?

– Ezio
Sep 30 '13 at 5:24




5




5





The way busybox work is it looks at it argv[0] parameter which is the name of the symlink; vim in your case. It then does a look-up and it has no applet named vim. You can make a script that does busybox vi and symlink that script to vim. The syntax busybox applet, is another way to select the program; but why not just type vi. An applet in busybox parlance is the emulated program. busybox has base infrastructure (command line parsing, etc) with a main driver file that is an applet emulating the normal program.

– artless noise
Sep 30 '13 at 15:21







The way busybox work is it looks at it argv[0] parameter which is the name of the symlink; vim in your case. It then does a look-up and it has no applet named vim. You can make a script that does busybox vi and symlink that script to vim. The syntax busybox applet, is another way to select the program; but why not just type vi. An applet in busybox parlance is the emulated program. busybox has base infrastructure (command line parsing, etc) with a main driver file that is an applet emulating the normal program.

– artless noise
Sep 30 '13 at 15:21














1 Answer
1






active

oldest

votes


















1














The answer to questions 1 and 2 is: you must set your PATH variable first or compile busybox with FEATURE_PREFER_APPLETS enabled. You can set the PATH variable with:



$ export PATH=/bin:/sbin:/usr/bin:/usr/sbin


A busybox applet is a small application that is usually found in the UNIX common utilities (defined in the POSIX standard). This applets are compiled into a single executable: busybox.






share|improve this answer
























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    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',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f19043700%2fbusybox-in-embedded-linux-shows-applet-not-found%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1














    The answer to questions 1 and 2 is: you must set your PATH variable first or compile busybox with FEATURE_PREFER_APPLETS enabled. You can set the PATH variable with:



    $ export PATH=/bin:/sbin:/usr/bin:/usr/sbin


    A busybox applet is a small application that is usually found in the UNIX common utilities (defined in the POSIX standard). This applets are compiled into a single executable: busybox.






    share|improve this answer




























      1














      The answer to questions 1 and 2 is: you must set your PATH variable first or compile busybox with FEATURE_PREFER_APPLETS enabled. You can set the PATH variable with:



      $ export PATH=/bin:/sbin:/usr/bin:/usr/sbin


      A busybox applet is a small application that is usually found in the UNIX common utilities (defined in the POSIX standard). This applets are compiled into a single executable: busybox.






      share|improve this answer


























        1












        1








        1







        The answer to questions 1 and 2 is: you must set your PATH variable first or compile busybox with FEATURE_PREFER_APPLETS enabled. You can set the PATH variable with:



        $ export PATH=/bin:/sbin:/usr/bin:/usr/sbin


        A busybox applet is a small application that is usually found in the UNIX common utilities (defined in the POSIX standard). This applets are compiled into a single executable: busybox.






        share|improve this answer













        The answer to questions 1 and 2 is: you must set your PATH variable first or compile busybox with FEATURE_PREFER_APPLETS enabled. You can set the PATH variable with:



        $ export PATH=/bin:/sbin:/usr/bin:/usr/sbin


        A busybox applet is a small application that is usually found in the UNIX common utilities (defined in the POSIX standard). This applets are compiled into a single executable: busybox.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jan 5 '18 at 1:57









        Luis LavaireLuis Lavaire

        88210




        88210
































            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f19043700%2fbusybox-in-embedded-linux-shows-applet-not-found%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            The Sandy Post

            Danny Elfman

            Pages that link to "Head v. Amoskeag Manufacturing Co."