The Following User Says Thank You to Char For This Useful Post: | ||
![]() |
2011-02-19
, 22:42
|
Posts: 94 |
Thanked: 3 times |
Joined on Jul 2010
|
#22
|
![]() |
2011-02-19
, 22:55
|
Posts: 94 |
Thanked: 3 times |
Joined on Jul 2010
|
#23
|
Hmmm... Well, it actually sounds like your command line isn't able to find the "nano" command for some reason - it sees the file, just doesn't see the program itself. I'm really not sure why that would be, assuming you're sure you typed everything correctly. Unless for some reason nano got uninstalled, or had it's binary renamed or deleted/moved? *Shrug* What do
andCode:ls -l /usr/bin/nano
give as output?Code:dpkg -l | grep nano
![]() |
2011-02-19
, 23:26
|
Posts: 2,225 |
Thanked: 3,822 times |
Joined on Jun 2010
@ Florida
|
#24
|
![]() |
2011-02-20
, 14:10
|
Posts: 94 |
Thanked: 3 times |
Joined on Jul 2010
|
#25
|
![]() |
2011-02-20
, 15:19
|
Posts: 94 |
Thanked: 3 times |
Joined on Jul 2010
|
#26
|
Ohhh. If you were running those commands from within the chroot, then that would make sense. I guess I assumed you would've been doing all these steps outside the chroot by default (like maybe the instructions you were following told you to first exit the chroot).
Anyway, then yeah, don't worry about it, nano should still be installed just fine.
As for typing closearch - it's at /usr/bin/closearch, right? In that case, are you use you chmod'ed it properly? ("chmod +x /usr/bin/closearch" - as root, so "sudo gainroot" first.)
![]() |
2011-02-20
, 19:53
|
Posts: 255 |
Thanked: 107 times |
Joined on Nov 2010
|
#27
|
![]() |
2011-02-20
, 23:24
|
Posts: 94 |
Thanked: 3 times |
Joined on Jul 2010
|
#28
|
![]() |
2011-02-21
, 01:52
|
Posts: 2,225 |
Thanked: 3,822 times |
Joined on Jun 2010
@ Florida
|
#29
|
so after saving that text i:
sudo gainroot
chmod a+x /usr/bin/closearch
or
sudo gainroot
cd /usr/bin
chmod a+x /usr/bin/closearch
?
The Following User Says Thank You to Mentalist Traceur For This Useful Post: | ||
![]() |
2011-02-21
, 13:10
|
Posts: 94 |
Thanked: 3 times |
Joined on Jul 2010
|
#30
|
also you can't use nano if you don't have it
sudo apt-get install nano
although I'd recommend leafpad as an alternative for you
sudo apt-get install leafpad
just replace "nano" with "leafpad" in all the commands
===
however if you DO have nano and you're seeing that it means you were inside the chroot when you tried to nano, and nano isn't inside the chroot. you'll have to exit the chroot first and THEN edit the file