Hi Sandip, I had a similar issue long ago. If it is actually scripts that you are executing, it is probably happening because there is no shebang line on the first line of the script. Try looking at what is actually on the first line using:
$ od -c <script-name> Try editing the script and correcting it. Also try adding a blank line on the top of the file. The difference between your KDE konsole and Ctrl+Alt+F1 might be your environment variables. Try doing: $ set > filename in both places and comparing them. Perhaps you'll get a clue as to why its happening. Thanks Manohar On Sun, Mar 28, 2010 at 12:57 PM, Sandip Tiwari <[email protected]>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? > > What is the difference between the shell we get from Alt + Ctrl + F(1-6) > and > konsole? > Is using Alt + Ctrl + F(1-6) shell and su - <username> same? > > Thanks & regards > > Sandip Tiwari > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
