Red Hat Bugzilla – Bug 157067
Palm Pilots not accessible
Last modified: 2007-11-30 17:07:17 EST
Plug in a USB Palm, and press the hotsync button. The ttyUSB[0-1] devices aren't accessible by the console user. Right now, I use: BUS="usb", SYSFS{idVendor}="0830", SYSFS{idProduct}="0061", NAME="pilot%n" in a udev rules file, which is obviously not enough to make all the USB Palms work. Getting the list of devices using the "visor" driver from /lib/modules/<kernelver>/modules.usbmap would probably be pretty complete. Note: /etc/security/console.perms from pam would need to be modified to handle more than one Palm.
The palm reconnects itsself to the USB kernel layer after you press the hotsync button. See also http://fedora.redhat.com/docs/udev/
I know, but given that the Palm doesn't get a name different from "ttyUSBX", we can't tell whether the created device node is a USB modem, a Palm, or another serial adaptor of some kind. That's why some differentiation at the udev level is needed.
HAL?
HAL doesn't modify permissions, does it?
It doesn't do this yet, no
For a quick fix I would look for the "visor" driver in my udev rules (udev rule should create the pilot symlink and then pam-console-apply does the right thing for /dev/pilot).
We are now at the point where we can create various udev/pam_console config drop ins for hardware. I started to document this and will publish it on our fedora homepage. I will add it to the udev core. This may be a noarch.rpm with some configs.