From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Bug#294123: udev: Bad parsing of regular expressions in *.rules
Date: Sun, 13 Feb 2005 03:14:41 +0000 [thread overview]
Message-ID: <1108264481.5674.34.camel@localhost.localdomain> (raw)
In-Reply-To: <20050208090725.GB7706@wonderland.linux.it>
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 /class/tty/ttyUSB0
>> udevinfo -a -p /class/tty/ttyUSB1
>>
>> if you find a difference between both interfaces to match against, that
>> is not dependent on the kernel device name.
>
>This is a real tough one to try to match on, as these both point to the
>same exact physical device. Same USB interface even. It's a pain,
>stupid palm devices...
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?
Kay
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2005-02-13 3:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-08 9:07 Bug#294123: udev: Bad parsing of regular expressions in *.rules Marco d'Itri
2005-02-08 17:00 ` Marco d'Itri
2005-02-09 2:24 ` Kay Sievers
2005-02-09 5:53 ` Greg KH
2005-02-12 12:28 ` Marco d'Itri
2005-02-13 3:14 ` Kay Sievers [this message]
2005-02-14 17:30 ` Greg KH
2005-02-14 18:22 ` Kay Sievers
2005-02-14 18:31 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1108264481.5674.34.camel@localhost.localdomain \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.