mkdir command not found?
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.
linux perl bioinformatics
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.
add a comment |
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.
linux perl bioinformatics
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 thoseexportcommands will be forgotten
– Stephen Harris
1 hour ago
add a comment |
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.
linux perl bioinformatics
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.
linux perl bioinformatics
linux perl bioinformatics
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.
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 thoseexportcommands will be forgotten
– Stephen Harris
1 hour ago
add a comment |
logout and login again. All thoseexportcommands 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
add a comment |
1 Answer
1
active
oldest
votes
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
add a comment |
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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
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
add a comment |
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
add a comment |
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
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
answered 58 mins ago
cryptarchcryptarch
63810
63810
add a comment |
add a comment |
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.
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
logout and login again. All those
exportcommands will be forgotten– Stephen Harris
1 hour ago