[Bug 480719] New: udev rules missing definition for Palm Pilot
https://bugzilla.novell.com/show_bug.cgi?id=480719 Summary: udev rules missing definition for Palm Pilot Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86 OS/Version: openSUSE 11.1 Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: ground33038@mypacks.net QAContact: qa@suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.6) Gecko/2009012700 SUSE/3.0.6-0.1.2 Firefox/3.0.6 This bug is being written to request that a udev file be created to automatically register palm pilot devices that connect via USB as /dev/pilot (or suitable equivalent). This will greatly help many people tether their palm pilots to OpenSuSE systems. This can be achieved by create a file in /etc/udev/rules.d - say 30-palmpilot.rules. Here is what I have been using successfully with a Palm Pilot TX: BUS=="usb",SYSFS{product}=="Palm Handheld*",NAME="%k",SYMLINK+="pilot",GROUP="users",MODE="0666",OPTIONS+="last_rule" (the above is my 30-palmpilot.rules and the above are all in one line). Right now, this has to be done manually and is very error prone. The great number of users affected can be done by a simple Google search where this is very common complaint. Thanks for a great (and Free) Product! Reproducible: Always Steps to Reproduce: 1. Take the default OpenSuSE 11.1 distro and connect a palm pilot via USB 2. Observe that there is no udev rule for it in /etc/udev/rules.d 3. Observe that /var/log/messages shows udev detecting it but not doing anything with the attached device. Actual Results: No /dev/pilot link! No connection with jpilot. Expected Results: I was hoping to see the link and being able to define the symbolic link /dev/pilot in jpilot for it to work. With the proposed changes, I was able to get a /dev/pilot link setup automatically (it points to /dev/ttyUSB1 but that's changeable and to be expected). Also, the link's target permissions (ie for /dev/ttyUSB1) are 0666. These permit for read/write access to the palm pilot. I confirmed with jpilot that synching works! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=480719 Cyril Hrubis <chrubis@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |kasievers@novell.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=480719 User kasievers@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=480719#c1 Kay Sievers <kasievers@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #1 from Kay Sievers <kasievers@novell.com> 2009-03-02 06:23:31 MST --- There are many types of "Pilot" devices. Most offer two interfaces. Such simple rules will try to create /dev/pilot two times which overwrite each other. The order, which one of the ports is the "real" one, differs from device to device. We dropped this rule intentionally, because it can not work correctly. Unless someone comes up with a proper database of devices, which port to use for which exact device, we can not do this. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com