-bash: /usr/bin/nano: No such file or directory

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











up vote
1
down vote

favorite












I have this problem on fresh install of Debian 8 (after doing apt upgrade).



nano is installed but when I try to use it to open a file :



nano myfile.txt



I get:



-bash: /usr/bin/nano: No such file or directory


I removed and reinstalled nano I get:



Setting up nano (2.7.4-1) ...
update-alternatives: using /bin/nano to provide /usr/bin/editor (editor) in auto mode
update-alternatives: using /bin/nano to provide /usr/bin/pico (pico) in auto mode


And using /usr/bin/editor myfile.txt I can open the file.



Why does this happen? How can I fix it?




debian upgrade nano




share|improve this question













migrated from serverfault.com May 3 at 9:08


This question came from our site for system and network administrators.














  • ls -l /usr/bin/nano ls: cannot access '/usr/bin/nano': No such file or directory
    – Karlom
    May 3 at 9:22







  • 1




    What does type nano give you? Presumably Bash has hashed it under the wrong path. Have you tried logging on anew to see if this is limited to your shell instance?
    – 0xC0000022L
    May 3 at 9:47






  • 1




    Guys, for no obvious reason, nano command works now. As for type nano I get nano is hashed (/bin/nano). Really strange! I never had such issue before.
    – Karlom
    May 3 at 9:50











  • @StephenKitt Could you explain what is cause of the problem , please.
    – GAD3R
    May 3 at 10:03






  • 5




    @GAD3R nano used to include both /bin/nano and /usr/bin/nano (the latter as a symlink to the former). Going from Debian 8 to 9, nano dropped the symlink; upgrading the package would then result in the error in the question, until a new shell is started or hash -r is run.
    – Stephen Kitt
    May 3 at 11:06














up vote
1
down vote

favorite












I have this problem on fresh install of Debian 8 (after doing apt upgrade).



nano is installed but when I try to use it to open a file :



nano myfile.txt



I get:



-bash: /usr/bin/nano: No such file or directory


I removed and reinstalled nano I get:



Setting up nano (2.7.4-1) ...
update-alternatives: using /bin/nano to provide /usr/bin/editor (editor) in auto mode
update-alternatives: using /bin/nano to provide /usr/bin/pico (pico) in auto mode


And using /usr/bin/editor myfile.txt I can open the file.



Why does this happen? How can I fix it?




debian upgrade nano




share|improve this question













migrated from serverfault.com May 3 at 9:08


This question came from our site for system and network administrators.














  • ls -l /usr/bin/nano ls: cannot access '/usr/bin/nano': No such file or directory
    – Karlom
    May 3 at 9:22







  • 1




    What does type nano give you? Presumably Bash has hashed it under the wrong path. Have you tried logging on anew to see if this is limited to your shell instance?
    – 0xC0000022L
    May 3 at 9:47






  • 1




    Guys, for no obvious reason, nano command works now. As for type nano I get nano is hashed (/bin/nano). Really strange! I never had such issue before.
    – Karlom
    May 3 at 9:50











  • @StephenKitt Could you explain what is cause of the problem , please.
    – GAD3R
    May 3 at 10:03






  • 5




    @GAD3R nano used to include both /bin/nano and /usr/bin/nano (the latter as a symlink to the former). Going from Debian 8 to 9, nano dropped the symlink; upgrading the package would then result in the error in the question, until a new shell is started or hash -r is run.
    – Stephen Kitt
    May 3 at 11:06












up vote
1
down vote

favorite









up vote
1
down vote

favorite











I have this problem on fresh install of Debian 8 (after doing apt upgrade).



nano is installed but when I try to use it to open a file :



nano myfile.txt



I get:



-bash: /usr/bin/nano: No such file or directory


I removed and reinstalled nano I get:



Setting up nano (2.7.4-1) ...
update-alternatives: using /bin/nano to provide /usr/bin/editor (editor) in auto mode
update-alternatives: using /bin/nano to provide /usr/bin/pico (pico) in auto mode


And using /usr/bin/editor myfile.txt I can open the file.



Why does this happen? How can I fix it?




debian upgrade nano




share|improve this question













I have this problem on fresh install of Debian 8 (after doing apt upgrade).



nano is installed but when I try to use it to open a file :



nano myfile.txt



I get:



-bash: /usr/bin/nano: No such file or directory


I removed and reinstalled nano I get:



Setting up nano (2.7.4-1) ...
update-alternatives: using /bin/nano to provide /usr/bin/editor (editor) in auto mode
update-alternatives: using /bin/nano to provide /usr/bin/pico (pico) in auto mode


And using /usr/bin/editor myfile.txt I can open the file.



Why does this happen? How can I fix it?





debian upgrade nano





share|improve this question












share|improve this question




share|improve this question








edited May 3 at 12:57









Stephen Kitt

140k22302363




140k22302363









asked May 3 at 8:52









Karlom

1083




1083




migrated from serverfault.com May 3 at 9:08


This question came from our site for system and network administrators.






migrated from serverfault.com May 3 at 9:08


This question came from our site for system and network administrators.













  • ls -l /usr/bin/nano ls: cannot access '/usr/bin/nano': No such file or directory
    – Karlom
    May 3 at 9:22







  • 1




    What does type nano give you? Presumably Bash has hashed it under the wrong path. Have you tried logging on anew to see if this is limited to your shell instance?
    – 0xC0000022L
    May 3 at 9:47






  • 1




    Guys, for no obvious reason, nano command works now. As for type nano I get nano is hashed (/bin/nano). Really strange! I never had such issue before.
    – Karlom
    May 3 at 9:50











  • @StephenKitt Could you explain what is cause of the problem , please.
    – GAD3R
    May 3 at 10:03






  • 5




    @GAD3R nano used to include both /bin/nano and /usr/bin/nano (the latter as a symlink to the former). Going from Debian 8 to 9, nano dropped the symlink; upgrading the package would then result in the error in the question, until a new shell is started or hash -r is run.
    – Stephen Kitt
    May 3 at 11:06
















  • ls -l /usr/bin/nano ls: cannot access '/usr/bin/nano': No such file or directory
    – Karlom
    May 3 at 9:22







  • 1




    What does type nano give you? Presumably Bash has hashed it under the wrong path. Have you tried logging on anew to see if this is limited to your shell instance?
    – 0xC0000022L
    May 3 at 9:47






  • 1




    Guys, for no obvious reason, nano command works now. As for type nano I get nano is hashed (/bin/nano). Really strange! I never had such issue before.
    – Karlom
    May 3 at 9:50











  • @StephenKitt Could you explain what is cause of the problem , please.
    – GAD3R
    May 3 at 10:03






  • 5




    @GAD3R nano used to include both /bin/nano and /usr/bin/nano (the latter as a symlink to the former). Going from Debian 8 to 9, nano dropped the symlink; upgrading the package would then result in the error in the question, until a new shell is started or hash -r is run.
    – Stephen Kitt
    May 3 at 11:06















ls -l /usr/bin/nano ls: cannot access '/usr/bin/nano': No such file or directory
– Karlom
May 3 at 9:22





ls -l /usr/bin/nano ls: cannot access '/usr/bin/nano': No such file or directory
– Karlom
May 3 at 9:22





1




1




What does type nano give you? Presumably Bash has hashed it under the wrong path. Have you tried logging on anew to see if this is limited to your shell instance?
– 0xC0000022L
May 3 at 9:47




What does type nano give you? Presumably Bash has hashed it under the wrong path. Have you tried logging on anew to see if this is limited to your shell instance?
– 0xC0000022L
May 3 at 9:47




1




1




Guys, for no obvious reason, nano command works now. As for type nano I get nano is hashed (/bin/nano). Really strange! I never had such issue before.
– Karlom
May 3 at 9:50





Guys, for no obvious reason, nano command works now. As for type nano I get nano is hashed (/bin/nano). Really strange! I never had such issue before.
– Karlom
May 3 at 9:50













@StephenKitt Could you explain what is cause of the problem , please.
– GAD3R
May 3 at 10:03




@StephenKitt Could you explain what is cause of the problem , please.
– GAD3R
May 3 at 10:03




5




5




@GAD3R nano used to include both /bin/nano and /usr/bin/nano (the latter as a symlink to the former). Going from Debian 8 to 9, nano dropped the symlink; upgrading the package would then result in the error in the question, until a new shell is started or hash -r is run.
– Stephen Kitt
May 3 at 11:06




@GAD3R nano used to include both /bin/nano and /usr/bin/nano (the latter as a symlink to the former). Going from Debian 8 to 9, nano dropped the symlink; upgrading the package would then result in the error in the question, until a new shell is started or hash -r is run.
– Stephen Kitt
May 3 at 11:06










1 Answer
1






active

oldest

votes

















up vote
6
down vote













In Debian 8, nano includes both /bin/nano and /usr/bin/nano (the latter is a symlink to the former). In Debian 9, /usr/bin/nano is no longer included (see #767929 for details).



Presumably you upgraded from Debian 8 to a version of the package including the fix above. Your shell had remembered that nano was in /usr/bin/nano, but after the upgrade that was no longer the case. Running hash -r in your shell would fix that, as would starting a new shell.






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%2f441493%2fbash-usr-bin-nano-no-such-file-or-directory%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
    6
    down vote













    In Debian 8, nano includes both /bin/nano and /usr/bin/nano (the latter is a symlink to the former). In Debian 9, /usr/bin/nano is no longer included (see #767929 for details).



    Presumably you upgraded from Debian 8 to a version of the package including the fix above. Your shell had remembered that nano was in /usr/bin/nano, but after the upgrade that was no longer the case. Running hash -r in your shell would fix that, as would starting a new shell.






    share|improve this answer

























      up vote
      6
      down vote













      In Debian 8, nano includes both /bin/nano and /usr/bin/nano (the latter is a symlink to the former). In Debian 9, /usr/bin/nano is no longer included (see #767929 for details).



      Presumably you upgraded from Debian 8 to a version of the package including the fix above. Your shell had remembered that nano was in /usr/bin/nano, but after the upgrade that was no longer the case. Running hash -r in your shell would fix that, as would starting a new shell.






      share|improve this answer























        up vote
        6
        down vote










        up vote
        6
        down vote









        In Debian 8, nano includes both /bin/nano and /usr/bin/nano (the latter is a symlink to the former). In Debian 9, /usr/bin/nano is no longer included (see #767929 for details).



        Presumably you upgraded from Debian 8 to a version of the package including the fix above. Your shell had remembered that nano was in /usr/bin/nano, but after the upgrade that was no longer the case. Running hash -r in your shell would fix that, as would starting a new shell.






        share|improve this answer













        In Debian 8, nano includes both /bin/nano and /usr/bin/nano (the latter is a symlink to the former). In Debian 9, /usr/bin/nano is no longer included (see #767929 for details).



        Presumably you upgraded from Debian 8 to a version of the package including the fix above. Your shell had remembered that nano was in /usr/bin/nano, but after the upgrade that was no longer the case. Running hash -r in your shell would fix that, as would starting a new shell.







        share|improve this answer













        share|improve this answer



        share|improve this answer











        answered May 3 at 12:56









        Stephen Kitt

        140k22302363




        140k22302363






















             

            draft saved


            draft discarded


























             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f441493%2fbash-usr-bin-nano-no-such-file-or-directory%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?

            Image
            Clash Royale CLAN TAG #URR8PPP up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this question asked Sep 26 at 0:12 ToanLuong 49 9 add a comment  |  up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this questi...
            Read more

            Displaying single band from multi-band raster using QGIS

            Image
            Clash Royale CLAN TAG #URR8PPP 1 How can I extract a single band from multi-band raster in QGIS? I have an remote sensed image which has 6 bands (including NDVI band), I want to display each band separately, but have no idea how to do. I have seen some questions similar here but none worked for me. The original image (has 6 bands) is: I want to display the band 6 which should be like this: But I tried gdal_translate, and couldn't get the correct result. What I have got is: qgis raster multi-band share | improve this question edited Mar 5 at 0:53 Summer asked Mar 4 at 6:42 Summer Summer 23 6 Is this any help gis.stackexchange.com/questions/220658/… ? if not gis.stackexchange.com/questions/62133/… might help. – Michael Stimson Mar 4 at 6:46 Thanks for answering but when I used gdal_translate, qgis showed that 'Error 4: Kayena.tif: No such file or directory". Would you know how to fi...
            Read more

            How many registers does an x86_64 CPU actually have?

            Image
            Clash Royale CLAN TAG #URR8PPP up vote 2 down vote favorite I am currently learning reverse engineering and am studying the flags register. I had in my mind that rflags was just another name for one of the 16 general purpose registers, for example rax or rbx . But it looks like rflags is actually an additional register. So that makes 17 registers in total... how many more could there be? I have spent at least an hour on this and found numerous different answers. The best answer so far is this, which says that there are 40 registers in total. 16 General Purpose Registers 2 Status Registers 6 Code Segment Registers 16 SSE Registers 8 FPU/MMX Registers But if I add that up, I get 48. Could anybody provide an official answer on how many registers an x86_64 CPU has (e.g. an Intel i7). Additionally, I have seen references to 'hardware' and 'architectural' registers. What are those registers and how many are there? register x86-64 share | improve this...
            Read more