Bug 157067 - Palm Pilots not accessible
Palm Pilots not accessible
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: udev (Show other bugs)
4.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Harald Hoyer
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-05-06 12:12 EDT by Bastien Nocera
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-05-11 06:15:25 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Bastien Nocera 2005-05-06 12:12:25 EDT
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.
Comment 1 Harald Hoyer 2005-05-09 08:00:22 EDT
The palm reconnects itsself to the USB kernel layer after you press the hotsync
button.
See also http://fedora.redhat.com/docs/udev/
Comment 2 Bastien Nocera 2005-05-09 08:49:03 EDT
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.
Comment 3 Harald Hoyer 2005-05-09 12:45:04 EDT
HAL?
Comment 4 Bastien Nocera 2005-05-10 17:45:07 EDT
HAL doesn't modify permissions, does it?
Comment 5 David Zeuthen 2005-05-10 17:56:54 EDT
It doesn't do this yet, no
Comment 6 David Zeuthen 2005-05-10 17:58:22 EDT
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).
Comment 7 Harald Hoyer 2005-05-11 06:15:25 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.