Bug#294123: udev: Bad parsing of regular expressions in *.rules

2005-02-14 Thread Kay Sievers
On Mon, 2005-02-14 at 09:30 -0800, Greg KH wrote: On Sun, Feb 13, 2005 at 04:14:41AM +0100, Kay Sievers wrote: On Tue, 2005-02-08 at 21:53 -0800, Greg KH wrote: On Wed, Feb 09, 2005 at 03:24:31AM +0100, Kay Sievers wrote: Can't you match against some interface attributes in sysfs, which are

Bug#294123: udev: Bad parsing of regular expressions in *.rules

2005-02-14 Thread Greg KH
On Sun, Feb 13, 2005 at 04:14:41AM +0100, Kay Sievers wrote: On Tue, 2005-02-08 at 21:53 -0800, Greg KH wrote: On Wed, Feb 09, 2005 at 03:24:31AM +0100, Kay Sievers wrote: Can't you match against some interface attributes in sysfs, which are telling you which one is the first interface of

Bug#294123: udev: Bad parsing of regular expressions in *.rules

2005-02-14 Thread Greg KH
On Mon, Feb 14, 2005 at 07:22:08PM +0100, Kay Sievers wrote: On Mon, 2005-02-14 at 09:30 -0800, Greg KH wrote: Ahh, I see. So we may follow the link to the physical device and look for the name of the _first_ serial interface of this device? Would this solve the problem? Heh, not

Bug#294123: udev: Bad parsing of regular expressions in *.rules

2005-02-13 Thread Kay Sievers
On Tue, 2005-02-08 at 21:53 -0800, Greg KH wrote: On Wed, Feb 09, 2005 at 03:24:31AM +0100, Kay Sievers wrote: Can't you match against some interface attributes in sysfs, which are telling you which one is the first interface of this device? You may compare: udevinfo -a -p

Bug#294123: Info received (was Bug#294123: udev: Bad parsing of regular expressions in *.rules)

2005-02-13 Thread Ricardo Galli
On Sunday 13 February 2005 13:55, Kay Sievers shaped the electrons to say: On Sun, 2005-02-13 at 13:04 +0100, Ricardo Galli wrote: On Sunday 13 February 2005 05:08, Kay Sievers shaped the electrons to say: Hi Ricardo, I've replied to Greg now on the hotplug list:

Bug#294123: Info received (was Bug#294123: udev: Bad parsing of regular expressions in *.rules)

2005-02-12 Thread Ricardo Galli
Sorry, I didn't see your post, so I'm asnwering a little late. Hope still helps. I have the following rule in /etc/udev/rules.d/palm.rules: BUS=usb, SYSFS{manufacturer}=Palm. Inc., KERNEL=ttyUSB[024], NAME=%k, SYMLINK=pilot What is that supposed to do? One symlink name for multiple

Bug#294123: udev: Bad parsing of regular expressions in *.rules

2005-02-11 Thread Ricardo Galli
On Tuesday 08 February 2005 17:59, Marco d'Itri shaped the electrons to shout: On Feb 08, Ricardo Galli [EMAIL PROTECTED] wrote: BUS=usb, SYSFS{manufacturer}=Palm. Inc., KERNEL=ttyUSB[024], NAME=%k, SYMLINK=pilot After further testing I realised is not always true, i.e. is not always

Bug#294123: udev: Bad parsing of regular expressions in *.rules

2005-02-08 Thread Ricardo Galli
Package: udev Version: 0.051-1 Severity: important I have the following rule in /etc/udev/rules.d/palm.rules: BUS=usb, SYSFS{manufacturer}=Palm. Inc., KERNEL=ttyUSB[024], NAME=%k, SYMLINK=pilot This rule created a symlink /dev/pilot to the first device created when the Palm is connected

Bug#294123: udev: Bad parsing of regular expressions in *.rules

2005-02-08 Thread Marco d'Itri
On Feb 08, Ricardo Galli [EMAIL PROTECTED] wrote: BUS=usb, SYSFS{manufacturer}=Palm. Inc., KERNEL=ttyUSB[024], NAME=%k, SYMLINK=pilot After further testing I realised is not always true, i.e. is not always repeatable. I'm waiting for more information on this. The other proble, perhaps

Bug#294123: udev: Bad parsing of regular expressions in *.rules

2005-02-07 Thread Ricardo Galli
Package: udev Version: 0.051-1 Severity: important I have the following rule in /etc/udev/rules.d/palm.rules: BUS=usb, SYSFS{manufacturer}=Palm. Inc., KERNEL=ttyUSB[024], NAME=%k, SYMLINK=pilot This rule created a symlink /dev/pilot to the first device created when the Palm is connected to