On Mar 28, 2010, at 4:27 PM, Sandip Tiwari wrote:

Hi,

A)
1. I booted up with BackTrack 3 Live CD.
2. Opened up konsole.
3. Tried to run rfcomm bind /dev/rfcomm0 <Bluetooth MAC>
4. It gave me an error: rfcomm : cannot execute binary file

5. I tried other commands like aircrack-ng, airodump-ng, hcitools, etc but I
kept getting the same error.

B)
1. Then I rebooted and didn't login into KDE instead used Alt + Ctrl + F1 and
logged in as root. And tried those commands and it worked.

2. Just to try things out, I logged into KDE and tried runnng those commands
in konsole. I got the same error again.
3.Then I switched to Alt + Ctrl + F1. And even there I started getting that
error.

Can anyone explain why it happened like this?


Can you give more information? Like under which user you are getting these errors? It could be the case that execute flag is set for these files only so that they can be executed by root. I don't have a Linux system handy to confirm this, but this is probably the reason.

One more thing you could check is the current shell - echo $0 - gives you current shell. Just check if the same shell is being used in both the cases.

What is the difference between the shell we get from Alt + Ctrl + F(1-6) and
konsole?

AFAIK, nothing. However, I am not entirely sure if konsole starts a login shell or is it a normal shell. But that should not affect your command execution, other than the fact that some directories may not be in the path.

Is using Alt + Ctrl + F(1-6) shell and su - <username> same?


AFAIK, if you are using su <username> [not root], then the logging in console or using su should be same. Only difference is that if you login using console shell, it will process all the login profile scripts, because its a login shell. However, su does not do that.

http://www.gnu.org/software/coreutils/manual/html_node/su-invocation.html

Thanks & regards

Sandip Tiwari

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


Reply via email to