Red Hat Bugzilla – Bug 133790
udev breaks console.perms for pilot
Last modified: 2007-11-30 17:10:50 EST
udev causes /dev/ttyUSB* to be recreated every time one presses the
hotsync button and the Palm appears on the USB.
This means not only that /etc/security/console.perms cannot be applied
to the /dev/pilot symlink on login because /dev/ttyUSB* has been
removed on shutdown but also causes ownership and permissions to be
reset every time someone presses the hotsync button.
udev needs to be handling the console.perms stuff on device creation,
not just login.
That's not the problem, Bill...
The problem is, that the device seems to reconnect to the USB bus,
causing one REMOVE and one ADD hotplug event.
Which module is this?
The device is a Palm Zire 71, the driver is CONFIG_USB_SERIAL_VISOR.
do you really have the problem with the permissions, btw?
if yes, which version of udev?
It breaks the way this used to work: have a symlink from /dev/pilot to
/dev/ttyUSB1 and /dev/pilot listed in /etc/security/console.perms
It works now that I have created a /etc/udev/rules.d/10-local.rules
The alternative would be to change /etc/console.perms to list
/dev/ttyUSB1 instead of /dev/pilot
Yes, the hardware causes that device to disconnect and reconnect every
time, you can't do anything about that, unfortunatly :(
And, as I just pointed out on linux-hotplug-devel, /dev/pilot
shouldn't always point to /dev/ttyUSB1, it all depends on the type of
you currently have (some Sony Clie devices use /dev/ttyUSB0 to sync
This is why it is (was) recommended practice to use a symlink.
# ln -s ttyUSB1 /etc/udev/devices/pilot
as of >= udev-032-5 this should get copied to the real dev on every reboot