adb devices command not working

I'm running Ubuntu 10.10 64 bit. I have ia32-libs installed along with Android Debug Bridge version 1.0.26. My problem(s): 1. `adb devices` >>> ???????????? no permissions 2. `sudo adb devices` >>>> sudo: adb: command not found 3. `adb shell` >>> error: insufficient permissions for device I guess these are all related. Here's the relevant info. $ echo $PATH /home/me/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/opt/android-sdk-linux_x86/tools:/opt/android-sdk-linux_x86/platform-tools $ which adb /opt/android-sdk-linux_x86/platform-tools/adb $ adb devices * daemon not running. starting it now on port 5037 * * daemon started successfully * List of devices attached ???????????? no permissions $ sudo adb devices sudo: adb: command not found $ adb shell error: insufficient permissions for device I get the same results with a rooted Moto Droid running CM6.1 and a rooted G-Tab running a CM7-based ROM. I have reviewed the following related posts: * http://forum.xda-developers.com/archive/index.php/t-522827.html * http://ubuntuforums.org/archive/index.php/t-1164359.html * https://stackoverflow.com/questions/2517493/adb-command-not-found-in-linux-environment I tried most (not all) of the suggestions and I have not been able to resolve my issue. The things I didn't try seemed inappropriate. I would appreciate a few more tips and I'll keep troubleshooting. One thing I didn't try was editing /etc/udev/rules.d/70-android.rules. Is that likely to be the issue? I can't see how that would cause "sudo: adb: command not found". Maybe my problems are not all related. Anyway, at this point I think I need some input from other people because I don't believe I have a path problem or the other common problems discussed in those other posts. **EDIT: SOLVED** thanks to EboMike and RivieraKid. This was actually two different problems: 1. Item #2 above (sudo: adb: command not found) was solved by making a symlink as follows: $ sudo ln -s /opt/android-sdk-linux_x86/platform-tools/adb /usr/local/sbin/adb That allowed me to then do as EboMike suggested and use [this solution](https://stackoverflow.com/questions/3127539/ubuntu-android-device-debug/3129903#3129903). Doing that was required for my Moto Droid. (Running adb as sudo was *not* required for my Viewsonic G-Tablet, however.) 2. My other two items were resolved by implementing the udev rule as RivieraKid suggested (from this [link](http://developer.android.com/guide/developing/device.html)).