From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Clarification on /etc/udev/rules.d processing
Date: Wed, 21 Apr 2004 10:09:20 +0000 [thread overview]
Message-ID: <20040421100920.GA23501@vrfy.org> (raw)
In-Reply-To: <4085F187.2070003@backtobasicsmgmt.com>
On Tue, Apr 20, 2004 at 08:59:03PM -0700, Kevin P. Fleming wrote:
> I've just started using udev, and I've decided I'd much rather have
> individual config files for various purposes in /etc/udev/rules.d rather
> than one combined file.
>
> From my reading of the code, it appears that udev always reads all the
> files in that directory (which is good), and they are read in readdir()
> order which should mean I can control the order by using alphanumeric
> sorting of the names (also good).
>
> What I'm not clear on is how udev will handle multiple rules that match
> for a given device: if more than one rule wants to provide a device
> name, I presume udev will stop looking for device name rules as soon as
> any rules matches, right?
Yes.
> In spite of that, rules that add symlinks to a
> device seem to always be processed even if they appear in the file after
> the rule that supplied the device name.
No, if NAME is set by a rule, the processing is stopped. No later
"symlink only" rule will be applied.
thanks,
Kay
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&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:[~2004-04-21 10:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-21 3:59 Clarification on /etc/udev/rules.d processing Kevin P. Fleming
2004-04-21 10:09 ` Kay Sievers [this message]
2004-04-21 14:20 ` Kevin P. Fleming
2004-04-21 16:08 ` Marco d'Itri
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=20040421100920.GA23501@vrfy.org \
--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.