No such file or directory

KaliBob · 11-14-2013, 03:56 PM

Hi, all!

This is my first post to the boards here, so I can't yet make attachments to my posts else I'd post a screenshot of my problem.

I'm attempting to run a script (run.sh), but it will not find a file (adb) no matter what I do. This program is not one I made myself, it is the program tether-linux, which I untarred and installed myself.

I have used this program on BackTrack5r3 and Ubuntu 12.04LTS without issue, but since upgrading to Kali Linux from BT5r3, it for some reason will not work. I checked the file structure against Ubuntu 12.04 and everything is the same. I installed it the way I always do: (moving the tar file to /usr/local/src first)

Code:

tar xzvf tether-linux.tgz

cd into the new directory /Tether/linux/node and run

Code:

./configure
make
make install

and receive no errors.

Here is what my terminal looks like when trying to start the tether service:

Code:

root@kali:~# cd /usr/local/src/Tether/linux
root@kali:/usr/local/src/Tether/linux# ls
adb  run.sh
root@kali:/usr/local/src/Tether/linux# ./run.sh
/usr/local/src/Tether/linux
Starting Tether...
./run.sh: line 38: ../linux/adb: No such file or directory
Opening tun device.
Opening tun device: /dev/net/tun
Forking worker.
Tun/tap device IP: 10.0.0.1
Reading tun/tap device... 
Opening tun device.
adb binary path: "/usr/local/src/Tether/linux/adb"
Checking phone status...
tun worker initialized.
{ [Error: Command failed: /bin/sh: 1: /usr/local/src/Tether/linux/adb: not found
] 
killed: false, code: 127, signal: null }
Listening on tether port...
root@kali:/usr/local/src/Tether/linux# ls
adb  run.sh
root@kali:/usr/local/src/Tether/linux# cd\
> 
root@kali:~# /usr/local/src/Tether/linux/adb
bash: /usr/local/src/Tether/linux/adb: No such file or directory
root@kali:~# cd /usr/local/src/Tether/linux
root@kali:/usr/local/src/Tether/linux# ls
adb  run.sh
root@kali:/usr/local/src/Tether/linux# HELP!!!

As we can see, adb is clearly there and it's where the installer put it, which is the same place as the Ubuntu install, which works fine. I've also done:

Code:

rm -r Tether

, rebooted, and installed the entire thing over again and get the same error.

Any help in getting this shell script to recognize that adb is there would be greatly appreciated! I need to tether since Kali doesn't come with the wicd network manager and thus I need to download it.

Hopefully as I post around the boards I'll be granted permission to post attachments, a screenshot would have been much easier for you to read.

Thanks.

PS - Unless I'm mistaken, Kali is always in root, but just to make sure I tried running the ./run.sh script in a sudo shell and got the same error. sudo command did not prompt for password either, so I think I'm already root. I also tried exec ./run.sh to no avail.

KaliBob · 11-14-2013, 04:04 PM

Also, I forgot to mention that in my terminal, root is the username I used during the OS install last night, it does not necessitate that I am in the system root. I'm probably going to have to change that to alleviate confusion.

Here is an external link to the screenshot of my issue if this makes it easier to read, since I can not yet attach them here directly.

http://i7.photobucket.com/albums/y26...psbc4401aa.png

yancek · 11-14-2013, 06:20 PM

You didn't post the script so we have no way of knowing what the contents are. What does line 38 look like, where the error is reported?

Beryllos · 11-14-2013, 09:43 PM

Quote:

Originally Posted by KaliBob

Code:

root@kali:~# /usr/local/src/Tether/linux/adb
bash: /usr/local/src/Tether/linux/adb: No such file or directory

You must have a filename containing a space or an unprintable character.

I made a directory with four files that look the same:

Code:

$ mkdir erase-me
$ cd erase-me
$ ls
$ touch "adb"
$ touch "  adb "
$ touch " adb  "
$ touch "adb "
$ ls
adb    adb    adb    adb
$ ls -1b    # 1=one entry per line, b=backslash before any nongraphic character
adb
\ \ adb\
\ adb\ \
adb\
$ ls -1Q    # 1=one entry per line, Q=double quotes around each entry
"adb"
"  adb "
" adb  "
"adb "
$ ls | hexdump -C    # hexdump tells all
00000000  61 64 62 0a 20 20 61 64  62 20 0a 20 61 64 62 20  |adb.  adb . adb |
00000010  20 0a 61 64 62 20 0a                              | .adb .|
00000017
$

Try these three ls commands to see what your filename really is.