mkdir command not found?












0














I think I messed up the PATH. I was installing Bioperl and tried to changed path. The correct code should be:



$ export PATH=/usr/local/ActivePerl-5.26/bin:$PATH
$ export PATH=/usr/local/ActivePerl-5.26/site/bin:$PATH
$PATH=/usr/local/ActivePerl-5.26/bin:$PATH
$PATH=/usr/local/ActivePerl-5.26/site/bin:$PATH
export PATH


--
But I did something stupid and what I typed is attached. Although Bioperl is installed, the ls or mkdir command are not working any more.enter image description here










share|improve this question









New contributor




rongrong is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















  • logout and login again. All those export commands will be forgotten
    – Stephen Harris
    1 hour ago
















0














I think I messed up the PATH. I was installing Bioperl and tried to changed path. The correct code should be:



$ export PATH=/usr/local/ActivePerl-5.26/bin:$PATH
$ export PATH=/usr/local/ActivePerl-5.26/site/bin:$PATH
$PATH=/usr/local/ActivePerl-5.26/bin:$PATH
$PATH=/usr/local/ActivePerl-5.26/site/bin:$PATH
export PATH


--
But I did something stupid and what I typed is attached. Although Bioperl is installed, the ls or mkdir command are not working any more.enter image description here










share|improve this question









New contributor




rongrong is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















  • logout and login again. All those export commands will be forgotten
    – Stephen Harris
    1 hour ago














0












0








0







I think I messed up the PATH. I was installing Bioperl and tried to changed path. The correct code should be:



$ export PATH=/usr/local/ActivePerl-5.26/bin:$PATH
$ export PATH=/usr/local/ActivePerl-5.26/site/bin:$PATH
$PATH=/usr/local/ActivePerl-5.26/bin:$PATH
$PATH=/usr/local/ActivePerl-5.26/site/bin:$PATH
export PATH


--
But I did something stupid and what I typed is attached. Although Bioperl is installed, the ls or mkdir command are not working any more.enter image description here










share|improve this question









New contributor




rongrong is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











I think I messed up the PATH. I was installing Bioperl and tried to changed path. The correct code should be:



$ export PATH=/usr/local/ActivePerl-5.26/bin:$PATH
$ export PATH=/usr/local/ActivePerl-5.26/site/bin:$PATH
$PATH=/usr/local/ActivePerl-5.26/bin:$PATH
$PATH=/usr/local/ActivePerl-5.26/site/bin:$PATH
export PATH


--
But I did something stupid and what I typed is attached. Although Bioperl is installed, the ls or mkdir command are not working any more.enter image description here







linux perl bioinformatics






share|improve this question









New contributor




rongrong is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question









New contributor




rongrong is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question








edited 51 mins ago









peterh

4,32592957




4,32592957






New contributor




rongrong is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked 1 hour ago









rongrongrongrong

1




1




New contributor




rongrong is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





rongrong is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






rongrong is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












  • logout and login again. All those export commands will be forgotten
    – Stephen Harris
    1 hour ago


















  • logout and login again. All those export commands will be forgotten
    – Stephen Harris
    1 hour ago
















logout and login again. All those export commands will be forgotten
– Stephen Harris
1 hour ago




logout and login again. All those export commands will be forgotten
– Stephen Harris
1 hour ago










1 Answer
1






active

oldest

votes


















1














The first time you ran export PATH=/usr/local/ActivePerl-5.26/ it replaced your entire previous path with that one single directory.



Subsequent attempts to "do the right thing" were now using the new path, so when you ran PATH=/usr/local/ActivePerl-5.26/bin:$PATH, what that did was update the PATH variable to contain the following string:



/usr/local/ActivePerl-5.26/bin:/usr/local/ActivePerl-5.26/


To recover from this situation, you have a few options:



1. Explicitly set the path to be what you want



Run something like the following (edit according to your requirements:



export PATH=/usr/local/ActivePerl-5.26/bin:/usr/local/bin:/usr/bin:/bin


2. Source your bashrc or bash_profile to reset the environment



You probably have your default path set in either ~/.bashrc or ~/.bash_profile. Let's assume it's in ~/.bashrc, then you can reset it like so:



. ~/.bashrc


Which is short for:



source $HOME/.bashrc


3. Start a new shell session



It might be simplest to just abandon the current session and start over. Close the terminal and open a new one; or go into a new shell inside the current terminal by running /bin/bash






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',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    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
    });


    }
    });






    rongrong is a new contributor. Be nice, and check out our Code of Conduct.










    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f493846%2fmkdir-command-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 first time you ran export PATH=/usr/local/ActivePerl-5.26/ it replaced your entire previous path with that one single directory.



    Subsequent attempts to "do the right thing" were now using the new path, so when you ran PATH=/usr/local/ActivePerl-5.26/bin:$PATH, what that did was update the PATH variable to contain the following string:



    /usr/local/ActivePerl-5.26/bin:/usr/local/ActivePerl-5.26/


    To recover from this situation, you have a few options:



    1. Explicitly set the path to be what you want



    Run something like the following (edit according to your requirements:



    export PATH=/usr/local/ActivePerl-5.26/bin:/usr/local/bin:/usr/bin:/bin


    2. Source your bashrc or bash_profile to reset the environment



    You probably have your default path set in either ~/.bashrc or ~/.bash_profile. Let's assume it's in ~/.bashrc, then you can reset it like so:



    . ~/.bashrc


    Which is short for:



    source $HOME/.bashrc


    3. Start a new shell session



    It might be simplest to just abandon the current session and start over. Close the terminal and open a new one; or go into a new shell inside the current terminal by running /bin/bash






    share|improve this answer


























      1














      The first time you ran export PATH=/usr/local/ActivePerl-5.26/ it replaced your entire previous path with that one single directory.



      Subsequent attempts to "do the right thing" were now using the new path, so when you ran PATH=/usr/local/ActivePerl-5.26/bin:$PATH, what that did was update the PATH variable to contain the following string:



      /usr/local/ActivePerl-5.26/bin:/usr/local/ActivePerl-5.26/


      To recover from this situation, you have a few options:



      1. Explicitly set the path to be what you want



      Run something like the following (edit according to your requirements:



      export PATH=/usr/local/ActivePerl-5.26/bin:/usr/local/bin:/usr/bin:/bin


      2. Source your bashrc or bash_profile to reset the environment



      You probably have your default path set in either ~/.bashrc or ~/.bash_profile. Let's assume it's in ~/.bashrc, then you can reset it like so:



      . ~/.bashrc


      Which is short for:



      source $HOME/.bashrc


      3. Start a new shell session



      It might be simplest to just abandon the current session and start over. Close the terminal and open a new one; or go into a new shell inside the current terminal by running /bin/bash






      share|improve this answer
























        1












        1








        1






        The first time you ran export PATH=/usr/local/ActivePerl-5.26/ it replaced your entire previous path with that one single directory.



        Subsequent attempts to "do the right thing" were now using the new path, so when you ran PATH=/usr/local/ActivePerl-5.26/bin:$PATH, what that did was update the PATH variable to contain the following string:



        /usr/local/ActivePerl-5.26/bin:/usr/local/ActivePerl-5.26/


        To recover from this situation, you have a few options:



        1. Explicitly set the path to be what you want



        Run something like the following (edit according to your requirements:



        export PATH=/usr/local/ActivePerl-5.26/bin:/usr/local/bin:/usr/bin:/bin


        2. Source your bashrc or bash_profile to reset the environment



        You probably have your default path set in either ~/.bashrc or ~/.bash_profile. Let's assume it's in ~/.bashrc, then you can reset it like so:



        . ~/.bashrc


        Which is short for:



        source $HOME/.bashrc


        3. Start a new shell session



        It might be simplest to just abandon the current session and start over. Close the terminal and open a new one; or go into a new shell inside the current terminal by running /bin/bash






        share|improve this answer












        The first time you ran export PATH=/usr/local/ActivePerl-5.26/ it replaced your entire previous path with that one single directory.



        Subsequent attempts to "do the right thing" were now using the new path, so when you ran PATH=/usr/local/ActivePerl-5.26/bin:$PATH, what that did was update the PATH variable to contain the following string:



        /usr/local/ActivePerl-5.26/bin:/usr/local/ActivePerl-5.26/


        To recover from this situation, you have a few options:



        1. Explicitly set the path to be what you want



        Run something like the following (edit according to your requirements:



        export PATH=/usr/local/ActivePerl-5.26/bin:/usr/local/bin:/usr/bin:/bin


        2. Source your bashrc or bash_profile to reset the environment



        You probably have your default path set in either ~/.bashrc or ~/.bash_profile. Let's assume it's in ~/.bashrc, then you can reset it like so:



        . ~/.bashrc


        Which is short for:



        source $HOME/.bashrc


        3. Start a new shell session



        It might be simplest to just abandon the current session and start over. Close the terminal and open a new one; or go into a new shell inside the current terminal by running /bin/bash







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered 58 mins ago









        cryptarchcryptarch

        63810




        63810






















            rongrong is a new contributor. Be nice, and check out our Code of Conduct.










            draft saved

            draft discarded


















            rongrong is a new contributor. Be nice, and check out our Code of Conduct.













            rongrong is a new contributor. Be nice, and check out our Code of Conduct.












            rongrong is a new contributor. Be nice, and check out our Code of Conduct.
















            Thanks for contributing an answer to Unix & Linux Stack Exchange!


            • 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%2funix.stackexchange.com%2fquestions%2f493846%2fmkdir-command-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

            Entries order in /etc/network/interfaces

            Grub takes very long (several minutes) to open Menu (in Multi-Boot-System)

            新発田市