Hi all,
I've finally figured out what was going wrong with the udev stuff on
Fedora Core 6
setting up the USB device for adb. The advice for Ubuntu may be correct, but it
doesn't work out of the box with Fedora Core 6 and probably higher. The reason
is because Fedora Core 6 has a rule in /etc/udev/rules.d/50-udev.rules
for all new
USB devices which sets modes, etc. The advice for Ubuntu is to make a
file called
50-android.rules and place it in the rules directory. Note that just
like init(1), udev
scans the rules directory in sorted order which means that 50-android
is executed
*before* 50-udev.
The net effect here is that 50-udev sets the permissions on the new device back
to 0644 which is to say, no write permission for userland adb and the subsequent
non-love (running adb's server as root ought to work). Here's the simple fix:
1) create a file to 51-android.rules in rules.d
2) put this incantation in it:
SUBSYSTEM=="usb_device",SYSFS{idVendor}=="0bb4",SYMLINK+="android_adb",MODE="0666"
3) as root after you've created the file, kick udev with: udevcontrol
reload_rules
4) plug in the device and enjoy!
It would be *really* nice if this or something like it found its way
back into the
documentation ::wink wink:: In fact, the advice for Ubuntu Dapper is the
exact same rule as Fedora, so most likely just changing the docs to create
51-android will work for both Fedora and Ubuntu Dapper.
Mike
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
