udev problems

[David Zeuthen]

On Sun, 2004-09-26 at 17:58 -0700, Gary Peck wrote:
> On Sat, Sep 25, 2004 at 05:06:51PM +0200, Thomas Zehetbauer wrote:
> > On Sam, 2004-09-25 at 16:27 +0200, Thomas Zehetbauer wrote:
> > > Must have been a problem with one of my USB ports, using another port it
> > > now created the device node, but as expected not regarding console.perms
> > 
> > Even worse it resets the ownership of /dev/ttyUSB* each time I press the
> > hotsync button.
> 
> Yeah, that's because the device node gets recreated each time you
> hotsync. Moreover, console.perms refers to /dev/pilot, which used to be
> a symlink to /dev/ttyUSB1. Under udev, however, that symlink no longer
> exists and so the permissions in console.perms never get applied.
> 
> The solution is to create a /etc/udev/rules.d/10-local.rules file with
> the following in it:
> 
> # palm pilot
> KERNEL="ttyUSB1",       SYMLINK="pilot"
> 
> Maybe it would make sense to have this in the default udev config?
> Otherwise, people that had the /dev/pilot link before udev will
> experience breakage.
> 

Suggest that

 KERNEL="ttyUSB*", NAME="%k", SYMLINK="pilot%e"

is better so we can handle multiple devices (the %e modifier for
'enumerate' is rather new, see the udev man page for details).

It's not perfect though, because this will also create these symlinks
for non-PDA devices such as USB-to-serial devices. 

One thing is the fact that /dev/pilot, or /dev/pilot1 symlink appear, we
can probably live with this, another one is the console gains read/write
rights. I'm not sure this is a huge problem though, but there might be
threat scenarios?

David