From: md@Linux.IT (Marco d'Itri)
To: linux-hotplug@vger.kernel.org
Subject: Bug#294123: udev: Bad parsing of regular expressions in *.rules
Date: Tue, 08 Feb 2005 17:00:21 +0000 [thread overview]
Message-ID: <20050208170021.GE15004@wonderland.linux.it> (raw)
In-Reply-To: <20050208090725.GB7706@wonderland.linux.it>
[-- Attachment #1: Type: text/plain, Size: 1200 bytes --]
----- 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: help upstream
From: Ricardo Galli <gallir@uib.es>
Organization: UIB
To: 294123@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"
>
> 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
>
> By changing to KERNEL="ttyUSB[135]" it creates the right links.
After further testing I realised is not always true, i.e. is not always
repeatable.
[...]
--
ricardo galli GPG id C8114D34
http://mnm.uib.es/gallir/
We all live in a #FFFF00 submarine
----- End forwarded message -----
--
ciao,
Marco
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-02-08 17:00 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 [this message]
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
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=20050208170021.GE15004@wonderland.linux.it \
--to=md@linux.it \
--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).