Udev rules and Palm
 

I had my palm running fine with FC5 and then had to reinstall for a larger disk. I kept the old information for reference so I could duplicate it on the second go around. This time, I cant' get my palm to sync. I have created a 10-visor.rules file with the following:

BUS="usb" SYSFS{product}="Palm Handheld*" KERNEL="ttyUSB*" SYMLINK="pilot" MODE="0660"

When I sync it creates /dev/pilot with the correct permissions. However, the /dev/ttyUSB1 and ttyUSB0 files have the wrong owner

crw------- 1 smith uucp 188, 1 Nov 29 07:46 ttyUSB0
crw------- 1 smith uucp 188, 1 Nov 29 07:46 ttyUSB1

what do I need to do to change it so the ownership belongs to root for the USB devices? Also, aren't these devices supposed to belong in the tty users?

TIA

Goog

This is my line for my Sony Clie

BUS="usb", SYSFS{product}="Palm Handheld", NAME="ttyUSB%n", MODE="0666"

I see a couple differences but don't know if it's the answer.

You could add a GROUP="root" to your rule

I tried that. If I got it right, that would put /dev/pilot as root ownership, /dev/ttyUSB* are still given username ownership.

In 50-udev.rules it has a listing for ttyUSB[0-9] and says it should be in the uucp group and root owner, but this is not happening.

Goog

What version of udev are you using? Somewhere in the not so distant past, udev changed the syntax of rules. Essentially if you are looking for a value to match, you need to use == in the rule, where as if you are assigning a value, you use =. So for example, in your rule BUS = "usb" may not be correct. You may need to use BUS == "usb".

I guess I'm wondering if somehow your rule is being ignored and some other udev rule is being followed.

In stead of all you added to it, I just changed this line:
to this:
Works a very much the same, because the identifying doesn't need to be done with udev, as long as it works, I don't care how my system calls my PDA

Is this a change you made in the 50-udev.rules file? My understanding is that if I create a rule with a lower number (i.e. 10-visor.rules) that it will supercede any similar rules in 50-udev.rules.

The problem still remains that the character device being created cannot be read or written to by anyone other than the owner, at least so it seems.

Goog