From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev: rules ignore whitespace but not case
Date: Mon, 15 Nov 2004 20:51:06 +0000 [thread overview]
Message-ID: <1100551866.7323.7.camel@localhost.localdomain> (raw)
In-Reply-To: <20041115204046.GA5306@localhost>
On Mon, 2004-11-15 at 15:40 -0500, Eric C. Cooper wrote:
> I use a rule like this
> BUS="scsi", SYSFS{model}="iPod", KERNEL="sd[a-z]2", SYMLINK="ipod"
> and it works even though the model field is actually
> "iPod "
>
> But a rule like this
> BUS="scsi", SYSFS{vendor}="KINGSTON", KERNEL="sd[a-z]1", SYMLINK="flash"
> fails with my flash disk because the vendor field is actually "Kingston".
>
> I think that if the pattern matching is going to trim whitespace, it
> should also ignore case. That would be more consistent and more
> resilient to errors.
That's on purpose. The whitespace is ignored only if your key value does
not end with whitespace. So it's still possible to distinguish fields
with differences only in the whitespace.
Thanks,
Kay
-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
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:[~2004-11-15 20:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 20:40 udev: rules ignore whitespace but not case Eric C. Cooper
2004-11-15 20:51 ` Kay Sievers [this message]
2004-11-15 21:12 ` 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=1100551866.7323.7.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).