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: Wed, 09 Feb 2005 02:24:31 +0000 [thread overview]
Message-ID: <1107915872.23291.67.camel@localhost.localdomain> (raw)
In-Reply-To: <20050208090725.GB7706@wonderland.linux.it>
On Tue, 2005-02-08 at 10:07 +0100, Marco d'Itri wrote:
> ----- Forwarded message from Ricardo Galli <gallir@uib.es> -----
>
> Subject: Bug#294123: udev: Bad parsing of regular expressions in *.rules
> Reply-To: Ricardo Galli <gallir@uib.es>, 294123@bugs.debian.org
> X-Debian-PR-Message: report 294123
> X-Debian-PR-Package: udev
> X-Debian-PR-Keywords:
> From: Ricardo Galli <gallir@uib.es>
> To: Debian Bug Tracking System <submit@bugs.debian.org>
>
> 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"
What is that supposed to do? One symlink name for multiple devices?
Every second Palm interface should overwrite this symlink?
> This rule created a symlink /dev/pilot to the first device created when
> the Palm is connected to USB.
>
> Up to version 0.50 it worked fine, but in last version udevs creates the
> symlink to /dev/ttyUSB1 instead of /dev/ttyUSB0
What does:
udevinfo -q all -p /class/tty/ttyUSB0
print in the failure case?
> By changing to KERNEL="ttyUSB[135]" it creates the right links.
Hmm, we didn't change anything in the matching logic and it worked for a
long time without any known problems. I expect something different as
the problem.
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.
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-09 2:24 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 [this message]
2005-02-09 5:53 ` Greg KH
2005-02-12 12:28 ` Marco d'Itri
2005-02-13 3:14 ` Kay Sievers
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=1107915872.23291.67.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).