On Sunday 20 March 2005 3:21 am, byroncoughlin@comcast.net wrote:

Sorry for not replying directly to Robert's post but I have just subscribed. Anyways here is what I have found as far as syncing with a visor. I believe you will find the same with yours. I got tired of trying to get ttyUSB1 device setup using hotplug into/dev directory. Seems to be a problem with udev_call from the general agent. So I gave up trying to hotplug to create the device. You can see this probably if you manually create ttyUSB1 manually using mknod and chmod and when you try to sync you may be able to but then you will notice ttyUSB1 gets removed after sync and you will have to create it each time you want to sync. What I did to work around this is like previously mentioned is create ttyUSB1 in another directory where hotplug will not remove it. A good place that was mentioned is /dev/usb. Then create a link in /dev to point to ttyUSB ex ln -s /dev/usb/ttyUSB1 pilot. Then in kpilot make your device setting /dev/pilot. The other thing that I prefer to do is stop hot plug at least while I am syncing so that it doesn't slow my system to a crawl while doing a hotsync. As su enter rchotplug stop. This works for me and until udev can work better and I know that ttyUSB1 will not change I am going to use this. Here is a solution: Create a rule in /etc/udev/rules.d: # Palm Handheld BUS="usb",SYSFS{serial}="PalmSN12345678",NAME="pilot"

You can either add it into 50-udev.rules or create 10-udev.rules. Then create permissions inetc/udev/permissions.d: # Palm Handheld rw pilot*:root:usb:0666 Add this to either 50-udev.permissions or 10-udev.permissions There is a good website on udev: http://www.reactivated.net/udevrules.php -- Jerry Feldman <gaf@blu.org> Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9