From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 007 release
Date: Tue, 02 Dec 2003 17:42:04 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-107038714532457@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-106963388124982@msgid-missing>
On Tue, Dec 02, 2003 at 06:21:52PM +0100, Marco d'Itri wrote:
> On Dec 02, Kay Sievers <kay.sievers@vrfy.org> wrote:
>
> >A better pattern matching seems unavoidable.
> >Is anyone already improving namedev's strncpm_wildcard()?
> >If nobody comes up, I will do it until tomorrow night :)
> At least [] characters classes should be implemented. Taking tty* as an
> example, if you can't match on tty[0-9]+ you would have to individually
> list 16 "tty<uppercase letter>" serial device names.
>
> If a partial reimplementation of extended regexps is too much complex to
> be worth it, then a good enough substitute would be the ability to match
> on one or more numbers.
Yes, this is already working in my tree:
REPLACE, KERNEL="tty[0-9]*", NAME="vc/%n"
Dec 2 18:30:57 pim udev[10109]: build_kernel_number: kernel_number='49'
Dec 2 18:30:57 pim udev[10109]: strncmp_wildcard: fnmatch p:ttyS* s:tty49 r:1
Dec 2 18:30:57 pim udev[10109]: strncmp_wildcard: fnmatch p:tty[0-9]* s:tty49 r:0
Dec 2 18:30:57 pim udev[10109]: apply_format: substitute kernel number '49'
Dec 2 18:30:57 pim udev[10109]: udev_add_device: name='vc/49'
Dec 2 18:30:57 pim udev[10109]: create_node: mknod(/udev/vc/49, 020666, 4, 49)
It's based on libc's fnmatch(), that supports (*, ?, []).
http://developer.novell.com/ndk/doc/libc/index.html?page=/ndk/doc/libc/libc_enu/data/amsgxku.html
But I have to port it to klibc.
I will do this tomorrow if nobody comes up with a better idea :)
Kay
-------------------------------------------------------
This SF.net email is sponsored by OSDN's Audience Survey.
Help shape OSDN's sites and tell us what you think. Take this
five minute survey and you could win a $250 Gift Certificate.
http://www.wrgsurveys.com/2003/osdntech03.php?site=8
_______________________________________________
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:[~2003-12-02 17:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-24 0:29 [ANNOUNCE] udev 007 release Greg KH
2003-11-24 3:19 ` Arnd Bergmann
2003-11-24 23:40 ` Greg KH
2003-11-25 13:29 ` Marco d'Itri
2003-11-26 19:28 ` Greg KH
2003-12-01 10:51 ` Marco d'Itri
2003-12-02 0:55 ` Greg KH
2003-12-02 15:16 ` Kay Sievers
2003-12-02 16:27 ` Kay Sievers
2003-12-02 17:21 ` Marco d'Itri
2003-12-02 17:42 ` Kay Sievers [this message]
2003-12-02 17:54 ` Greg KH
2003-12-02 17:55 ` Greg KH
2003-12-02 18:04 ` 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=marc-linux-hotplug-107038714532457@msgid-missing \
--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).